Skip to content
M1 EOL since June 2020

Migrate Magento 1 → 2 without losing customers, orders, or SEO

Magento 1 reached end of life in June 2020: no security patches, no PCI cover. I handle the Magento 1 to Magento 2 migration myself and move your store to Magento 2.4.9 with all customers, orders, products and content carried across. I crawl the old and new store and check every URL so your rankings carry over. You get a fixed written quote with scope, price and timeline.

  • Row counts compared before go-live
  • A 301 map for every crawled legacy URL
  • Cutover and rollback plan agreed in writing
Fixed written quote Adobe Certified since 2021
Migrate Magento 1 → 2 without losing customers, orders, or SEO
  • 2020 M1 EOL date

    Magento 1 stopped getting security patches in June 2020. Every extra month on it leaves known CVEs open.

  • Row counts Checked before go-live

    Customers, orders, products, reviews and CMS pages are migrated, and I compare row counts before go-live.

  • 301 map From a crawl of the old store

    I crawl the old store and the new one and compare the URLs. Each crawled legacy URL gets a 301. Schema, hreflang and canonicals move across too.

  • M1 Moves to Magento 2

    I’ve already hit most M1 extension conflicts, so few of them surprise me now.

What you get

Six pillars of a clean M1 → M2 migration

Every migration I do covers all six. Anything outside this scope is quoted up front in the written quote, never billed silently.

  • Full data migration

    Customers, orders, products (simple, configurable, bundle), categories, reviews, CMS, URL rewrites, customer addresses, gift cards and store credit.

  • URL & SEO continuity

    Every legacy URL gets a 301. I run Screaming Frog crawls before and after to check nothing drops out of the index. Hreflang, canonicals and structured data carry over.

  • Theme rebuild

    I rebuild your M1 theme on Magento 2, or on Hyvä if you want a faster frontend. It matches the old design by default, or you can use the move to redesign.

  • Extension equivalents

    For every M1 extension you rely on, I find a Magento 2 version: from the vendor, from the community, or rebuilt by me. The written quote lists all of them before work starts.

  • Payment & gateway migration

    Stripe, PayPal, Authorize.net, Braintree, Razorpay and Klarna re-integrated and tested. Subscriptions and stored cards are kept where the gateway allows it.

  • Admin team retraining

    A Magento 2 admin walkthrough for your team: catalog, orders and marketing tools. You get a written guide and a 1-hour live session with me.

How it works

Five steps from brief to live

You can review staging daily from week two. I do three test data runs before the live cutover, and you approve the cutover before I touch production.

  1. 01

    Brief

    Send a short brief on WhatsApp: your Magento 1 version, extensions, custom code, payment gateways, integrations, traffic and SEO. I reply with scope, price and timeline, with the risks listed.

    Days 1-2
  2. 02

    Data + scope plan

    A fixed-price quote in phases: the data map, the theme decision (Magento 2 rebuild or Hyvä), the extension list and the redirect plan. Once you sign, I book the slot.

    Days 3-4
  3. 03

    Build Magento 2

    A fresh Magento 2.4.9 install. I port the theme, add extension equivalents, re-integrate payment gateways and rebuild ERP, OMS or PIM connectors. You can review staging every day.

    Weeks 2-8
  4. 04

    Migrate data

    Adobe’s Data Migration Tool plus my own scripts for non-standard tables. Three test runs on staging, then a final delta during the cutover window. I check order, customer and product counts before go-live.

    Weeks 8-10
  5. 05

    Cutover

    DNS or load-balancer switch. The cutover time and the rollback plan are agreed with you in writing before launch. 14-day bug-fix warranty on production deployments covers regressions in delivered scope.

    Launch

Your quote

Get a fixed quote for your project

Send your store URL and describe what you want to change. We can review the requirements and agree a written scope, quote and timeline before work starts.

  • Written scope, price and timeline
  • You approve every change
What clients say

Stores already migrated from M1 to M2

Client feedback is public on my Upwork profile.

Magento work and feedback View Upwork profile

  • Illustration of Magento 2 development work for a sports footwear and hockey shop
    Sports footwear and hockey shop, Netherlands
  • Illustration of Magento 2 development work for a photo printing supplies wholesaler
    Photo printing supplies wholesaler, Netherlands
  • Illustration of Magento 2 development work for an educational toys and books shop
    Educational toys and books shop
  • Kishan has done an excellent job in a timely manner. He is very knowledgeable, has a very positive attitude, easy to communicate.

    Z. K.Magento 2 client
  • He is technically strong, approaches problems thoughtfully, and focuses on stable, long-term solutions.

    E. H.Magento 2 client
  • Kishan was a pleasure to work with! He is highly skilled, professional, and delivered outstanding results on time.

    M.Magento 2 client
FAQ

Honest answers to the M1 → M2 questions everyone asks

Why do I need to migrate from Magento 1 to Magento 2?

Magento 1 hit End of Life on June 30, 2020. Adobe stopped releasing security patches, bug fixes, and PCI compliance updates from that date. Every day a store stays on M1, it accumulates unpatched CVEs, and most card processors (Stripe, Braintree, Authorize.net) now flag M1 stores as non-compliant during PCI audits. Beyond security: Magento 2 is faster (PHP 8, Varnish, full-page cache native), has a modern admin, ships with B2B and PWA-ready features, and runs on actively-maintained extensions. Migration isn’t optional anymore, it’s the only safe path forward for serious commerce.

How long does an M1 to M2 migration take?

The timeline depends on store complexity:

  • Small store (< 10k SKUs, < 10 extensions, light customisation): mostly data migration and a theme rebuild
  • Standard store (up to 50k SKUs, up to 20 extensions, custom theme): adds extension replacements and a custom theme port
  • Enterprise (B2B, multi-store, ERP/POS/PIM integrations, 100k+ SKUs): integrations and data volume set the pace

Staging review, the final delta-data migration and the production cutover window are part of every plan. We give a fixed timeline in the written quote and won’t move the goalposts mid-project.

How much does it cost to migrate from Magento 1 to Magento 2?

Contact me on WhatsApp for a quote. I reply with scope, price and timeline.

Typical scopes:

  • Standard Migration: up to 50k products, up to 20 extensions, full data + SEO carry-over. The 14-day bug-fix warranty on production deployments covers regressions in delivered scope.
  • Enterprise: custom quote, B2B, multi-store, ERP/POS integrations, 100k+ SKUs, dedicated PM

Hosting, SSL, payment gateway re-application fees, and any third-party extension licences (e.g. Amasty, Mageplaza) are pass-through with no markup. You always see the line items before signing.

Will my customers, orders, and product data carry over?

Yes, 100% of standard data migrates: customers (with addresses, groups, store credit, gift cards, password hashes where compatible), orders (open + completed + invoices + shipments + credit memos), products (simple, configurable, bundled, virtual, downloadable), categories, reviews, ratings, CMS pages, CMS blocks, URL rewrites, and store config. We use Adobe’s Data Migration Tool as the foundation, plus custom scripts for any non-standard tables (custom modules, third-party schemas). Three test runs on staging confirm row counts match before the live delta-migration during cutover. Audited reports show before/after counts on every table, nothing slips through silently.

Will my SEO rankings be affected?

Done right, zero ranking loss, and usually a small lift from M2’s better Core Web Vitals. Our SEO continuity protocol: (1) Pre-migration Screaming Frog crawl captures every indexed URL + status code + title + meta + canonical + hreflang. (2) Every legacy URL gets a 301 redirect to its M2 equivalent (auto-mapped where slugs match, manual where they don’t). (3) Schema.org JSON-LD, hreflang, canonicals, meta robots, and XML sitemaps all carried over. (4) Post-launch crawl compares against pre-launch, any 4xx/5xx flagged and fixed. (5) Search Console resubmission of new sitemap. Most stores see ranking improve within 60 days from speed alone.

Can my Magento 1 extensions work on Magento 2?

No, M1 and M2 have completely different architectures. Every M1 extension needs an M2 equivalent. Three paths:

  • Vendor M2 version, Mageplaza, Amasty, Magefan, Aheadworks, Webkul all rebuilt for M2. Often free upgrade with proof of M1 licence.
  • Community / Marketplace alternative, if the original vendor disappeared, there’s usually a competitor with feature-parity.
  • Custom rebuild, for niche / proprietary extensions, we rebuild on M2’s API + UI components.

The project starts with an audit that catalogues every extension on your M1 store and maps each to one of the three paths, with cost & risk, before any migration work starts.

Should I migrate to Magento 2 or move to Shopify / WooCommerce?

Depends on your store:

  • Stay on Magento (migrate to M2): if you have B2B flows, multi-store, custom checkout, ERP/POS integrations, 10k+ SKUs, or international tax requirements. Magento 2 is the cheaper path long-term and you keep the data + URL history.
  • Move to Shopify: if you have < 5k SKUs, simple B2C, no custom checkout, and value low operational overhead more than control. Shopify Plus starts at $2,300/month vs Magento OS being free + hosting.
  • Move to WooCommerce: rarely makes sense from M1, you lose the commerce-grade catalog model.

Send a short brief on WhatsApp and the written quote includes a platform-fit assessment: I’ll tell you honestly if M2 isn’t the right answer.

Can I redesign during migration or should it be like-for-like?

Both options work, we recommend based on store maturity:

  • Like-for-like rebuild (default): pixel-perfect M2 theme matching the M1 design. Lowest risk for SEO + UX continuity. No A/B variable to confuse migration metrics. Choose this if your M1 design still converts well.
  • Migrate + redesign: combine the migration with a fresh design (or move to Hyvä for the perf bonus). Only ~20% more time and cost than like-for-like, and you get a 2-for-1 project. Choose this if your M1 design is dated, mobile-weak, or pre-Core-Web-Vitals.

Pre-migration A/B testing on staging proves the new design converts at least as well before cutover, we won’t ship a redesign that hurts revenue.

How do you handle URL redirects?

Every legacy M1 URL gets a 301 redirect to its M2 equivalent. Three layers:

  • (1) Slug-match auto-mapping, Magento’s URL rewrite migration handles 80-90% of product, category, and CMS URLs automatically (slugs unchanged).
  • (2) Manual mapping, for URLs that changed (e.g. M1 .html suffix dropped, custom routes restructured), we generate a CSV of old→new and load it into M2’s url_rewrite table.
  • (3) Web-server fallback, nginx / Apache rules catch anything missed at the URL-rewrite level (e.g. legacy .php paths).

Pre/post Screaming Frog crawls compare every URL, any 404s on legacy URLs get patched after cutover.

What about my custom checkout and payment integration?

M2 has a completely different checkout (KnockoutJS-based, multi-step or 1-page via Hyvä Checkout) so a custom M1 checkout flow needs to be rebuilt. Process:

  • Document the M1 flow, every step, validation rule, payment gateway, business rule.
  • Map to M2 checkout architecture, vanilla M2, Hyvä Checkout, or custom UI components. Hyvä is usually cheaper and faster.
  • Gateway re-integration, Stripe, Adyen, Braintree, PayPal, Authorize.net, Razorpay, Klarna, Mollie all have native M2 modules. Stored payment tokens carry over where the gateway supports it (most do).

Recurring subscriptions, gift-card balances, and store credit all preserved. Three test transactions per gateway in staging before cutover.

What’s the rollback plan if something goes wrong?

Two safety nets, both built in:

  • (1) Agreed cutover: the old store stays available until you approve the cutover, with a rollback plan agreed before launch.
  • (2) Bug-fix warranty: the 14-day bug-fix warranty on production deployments covers regressions in delivered scope. After that, optional monthly retainer for continued cover.

We also keep the final M1 database snapshot for 90 days, if a customer reports a missing 2017 order on day 60, we can reconstruct it from the snapshot.

When’s the right time to migrate?

Yesterday. Magento 1 has been EOL since June 2020, every additional day is a CVE exposure and a PCI-compliance risk. Practical timing:

  • If your last PCI audit failed or is upcoming: start now. Most processors (Stripe, Braintree, Adyen) flag M1 as non-compliant in 2026.
  • If you’re re-platforming anyway: M2 + Hyvä is the cheapest combined upgrade path.
  • If you’re > 6 months from Black Friday: you have time for a comfortable migration with two months of post-launch stabilisation.
  • If you’re < 3 months from a peak season: book the audit now, schedule the migration for January.

The longer you wait, the more your M1 stack drifts from anything modern. Send a short brief on WhatsApp and I’ll tell you honestly when to start.

Reserve your migration slot

Send me a short brief on WhatsApp. I reply with a fixed written quote with scope, price and timeline.

Message me on WhatsApp

No form to fill. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Message me on WhatsApp

No form to fill. Send me a quick message. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Helpful to mention

  • Magento 1 store URL
  • Magento 1 version
  • Product count
  • Monthly orders
  • Target version
  • B2B requirement

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

Kishan Savaliya Online 10 AM to 7 PM IST Chat on WhatsApp