Magento to Shopify Migration 2026: A Playbook from 40 Builds

I've lost count of the number of times a client has told me their last Magento migration "mostly worked." That word -- mostly -- is where the trouble lives. Mostly means orphaned customer records. Mostly means 14% of images 404ing. Mostly means a configurable product that collapsed into a single variant and a Google ranking that quietly tanked three weeks after launch.

After roughly 40 Magento (and Adobe Commerce) to Shopify migrations, I can tell you the platform swap itself is the easy part. The hard part is everything Magento modeled differently: configurable products, category trees, URL structures, checkout logic, and the mountain of custom modules nobody remembers installing. This is the playbook we actually use -- not the sanitized eleven-step version, but the one with the caveats written in.

Why 2026 is the year teams are finally moving

There's a genuine cluster of deadlines forcing hands this year, and they're not marketing fluff.

Adobe Commerce 2.4.4's extended security support ended in April 2026. For 2.4.5, extended support ends August 2026. Once you're past those dates you're carrying real PCI compliance risk -- unpatched commerce software handling card data is exactly what auditors flag. Roughly 14% of Magento stores are still on Magento 1, which has been end-of-life since June 2020. Those merchants have been living on borrowed time for six years.

Then there's the licensing squeeze. Through 2026 Adobe has steadily pushed Magento Open Source users toward paid Adobe Commerce Cloud licensing. If you originally picked Magento because it was free, that math has changed. The self-hosting bill -- Cloudflare, a managed hosting provider, a DevOps contractor on retainer -- adds up fast when the "free" platform starts nudging you to a license.

And if you're on Shopify Plus already but eyeing a fuller migration: Shopify Scripts hit full end-of-life on June 30, 2026. Any custom checkout logic now lives in Shopify Functions. That rebuild is standard scope in every 2026 migration we quote.

Pre-migration audit: what to keep, what to bin

Every migration we've regretted skipped this step. The temptation is to move everything -- every product, every order back to 2014, every customer who bought once and never returned. Don't.

Here's the audit we run before touching a single export:

• Product catalog. How many active products? How many disabled? We migrate active SKUs only unless there's a legal reason to keep the rest. Disabled products bloat the import and confuse smart collections.
• Configurable products. Count them separately. A 3-color × 4-size configurable becomes 12 variants in Shopify. If you've got products exceeding 100 variants, Shopify's hard cap (100 variants, or 2,000 on some plans via variant expansion) becomes a real design constraint.
• Custom attributes. Magento's EAV model lets you attach arbitrary attributes to anything. Shopify uses metafields. Map every attribute you actually display or filter on; ignore the rest.
• Orders. We usually migrate 12-24 months of order history for customer-facing account pages, and archive the rest to a CSV in cold storage. Full order history rarely justifies the import time.
• Customers. Clean the list. Bounced emails and duplicate accounts don't need to come along.

Back everything up before you start. A full database dump plus a media folder tarball. I've never needed the backup on a well-run migration -- and I've always been glad it existed on the messy ones.

Choosing your migration tool

There are really three viable paths, and the right one depends on how weird your catalog is.

Tool	Best for	Cost (2026)	Handles configurables well?
Shopify Store Importer	Small, clean catalogs	Free	Poorly -- flattens options
Cart2Cart	Mid-size, standard data	~$99-$1,500 by volume	Decent, with review
Matrixify	Large / complex catalogs	$20-$200/mo	Excellent with mapping
Custom ETL script	Enterprise, unusual data models	Dev time	Fully controllable

For most mid-market stores we reach for Matrixify. You convert your Magento product CSV into their Excel template -- which documents every single Shopify field -- then run a dry-run import that shows exactly what will be created or updated without writing anything. That dry-run has saved us from botched migrations more than once.

Cart2Cart is the click-and-go option. You install their Store Migration app, drop a Connection Bridge PHP file on your Magento server, point it at your admin URL, and pick entities. Always run the free demo migration first -- it moves ~10 products so you can spot-check before paying.

For anything genuinely complex -- multi-source inventory, deeply custom attribute logic, ERP-driven data -- we write a custom ETL against the Magento REST API and Shopify's Admin GraphQL API. It's more work, but you get total control over transformations. If your build is at that level of complexity, our headless CMS and commerce work is usually part of the same conversation.

Step-by-step data migration

Products and variants

Magento configurable products are the single biggest source of migration bugs. In Magento, a configurable is a parent shell pointing to simple product children. Shopify has one product with up to three option dimensions producing variants. The mapping isn't automatic.

Your verification checklist after import:

• Product count matches Magento's active count (minus anything you intentionally left behind).
• Variant count. That 3×4 configurable should show 12 variants -- spot check a few.
• Image count. Spot-check 20 products. Missing images are almost always a media-URL mismatch between Magento's pub/media path and what your CSV references.
• Categories → collections. Build smart collections matching your Magento category tree before going live.
• Inventory totals. Sum the variant quantities. The total should equal your Magento total exactly.

The awkward product types

Magento has product types Shopify doesn't. Here's how they translate:

Magento bundle       → Shopify Bundles app (rebuild manually, ~5-10 min each)
Magento virtual      → Standard product, Requires Shipping = FALSE
Magento downloadable  → Digital Downloads app (re-upload each file)
Magento grouped      → Rebuild as separate products or a collection

None of the bundle definitions or download file links migrate. Budget real time for rebuilding these by hand. On a store with 200 bundles, that's a full day of nobody's favorite work.

Customers, orders, gift cards

Customers migrate cleanly via Cart2Cart or Store Importer, with two caveats. First, passwords never migrate -- you can't; they're hashed differently. Every customer gets a password-reset prompt at first login, so plan a comms email. Second, customer account email must be unique in Shopify; Magento allowed edge cases that don't map.

Gift cards are their own headache. Outstanding gift card balances need manual re-issuance in Shopify unless you're on a plan and tool combination that supports the transfer. Reconcile the balances to the cent before launch -- customers notice missing store credit faster than anything else.

Rebuilding checkout logic after Shopify Scripts

This is the 2026 scope item nobody budgets for. If your Magento store had any custom cart or checkout logic -- tiered discounts, "buy X get Y," bundled shipping rules, customer-group pricing -- none of it ports. And with Shopify Scripts gone as of June 30, 2026, the old Ruby escape hatch is closed too.

Everything now lives in Shopify Functions, which run on WebAssembly and are written in Rust or JavaScript. A basic discount function looks like this:

export function run(input) {
  const discounts = input.cart.lines
    .filter(line => line.quantity >= 3)
    .map(line => ({
      targets: [{ cartLine: { id: line.id } }],
      value: { percentage: { value: "10.0" } }
    }));
  return { discounts, discountApplicationStrategy: "FIRST" };
}

Functions are more capable than Scripts ever were, and they run server-side at checkout without the performance hit. But they're a proper development task, not a config toggle. On a store with genuinely complex promotion rules, we've seen this consume 30-40% of the total migration budget. Scope it explicitly. If you're building at this level, our Next.js and headless commerce work often pairs with a Hydrogen storefront.

SEO and 301 redirects: the part that pays the bills

Here's where the "mostly worked" migrations bleed revenue. Magento and Shopify structure URLs completely differently:

Magento:  /catalog/product/view/id/1234/s/blue-widget/
          /blue-widget.html
Shopify:  /products/blue-widget
          /collections/widgets/products/blue-widget

Every indexed Magento URL needs a 301 redirect to its Shopify equivalent. Miss this and you lose ranking equity that took years to build. We export the full URL list from Google Search Console plus the Magento URL rewrite table, dedupe, and build a redirect map.

Stage the redirects before you point the domain -- never after. Import them, test a sample against the live-but-unpointed Shopify store, and have them ready to fire. Shopify's built-in URL redirect tool handles the map; for large sets, import them via Matrixify's Redirects sheet.

A few more SEO essentials that get forgotten:

• Migrate meta titles and descriptions as metafields, not just the auto-generated ones.
• Keep canonical tags pointing to the primary product URL, not the collection-scoped variant.
• Rebuild the XML sitemap and resubmit in Search Console the moment DNS flips.
• Watch Search Console coverage reports daily for the first two weeks. A spike in 404s means a redirect gap.

Launch day runbook

The switch is a domain change, and it's best done during your quietest traffic window. Check analytics for it.

24-48 hours before:

• Lower your DNS TTL to 300 seconds. This controls how long DNS records stay cached worldwide; a low TTL means the cutover propagates fast, shrinking the window where some visitors see the old site and others the new.
• Confirm all 301 redirects are staged and tested.
• Freeze the Magento catalog -- no more product or price edits.

Cutover:

• Point the domain at Shopify.
• Confirm SSL provisioning. Shopify's free SSL takes a few minutes to activate after the domain connects; plan for it so the site isn't briefly flagged insecure.
• Fire the redirect map.
• Smoke-test: place a real test order, reset a customer password, check three product pages, verify a collection.

Post-launch:

• Resubmit the sitemap.
• Monitor Search Console and error logs daily for two weeks.
• Keep the Magento instance running (read-only) for 30 days as a fallback reference.

If you run physical retail on Shopify POS, don't switch every location at once. Run both systems in parallel and cut over store by store. Continuity beats a clean launch date.

Cost breakdown

Rough 2026 numbers for a mid-market migration, based on what we actually quote:

Line item	Typical range
Migration tooling (Matrixify/Cart2Cart)	$200-$1,500
Theme build / customization	$8,000-$30,000
Checkout logic in Functions	$5,000-$25,000
Data migration + QA	$4,000-$15,000
SEO / redirect mapping	$2,000-$8,000
Shopify Plus (if needed)	~$2,300/mo

The honest truth: catalog complexity and checkout logic drive 70% of the cost variance. A clean 500-product store with standard promotions is a very different project from a 40,000-SKU catalog with customer-group pricing. If you want a scoped estimate for your specific build, our pricing page lays out how we structure engagements, or just get in touch with your catalog size and current pain points.

FAQ

How long does a Magento to Shopify migration take?

For a clean mid-size catalog, plan 6-10 weeks end to end. Complex builds with heavy checkout logic, thousands of configurables, or ERP integrations run 3-6 months. The data transfer itself is days; everything around it -- theme, Functions, QA, redirects -- is where the calendar goes.

Will I lose my Google rankings when I migrate?

Only if you skip the redirect work. A complete 301 redirect map from every indexed Magento URL to its Shopify equivalent preserves ranking equity. Expect a small temporary dip in the first two to three weeks as Google recrawls, then recovery. Stores that botch redirects can lose 20-40% of organic traffic and never fully recover.

Do customer passwords transfer to Shopify?

No. Passwords are hashed and can't be moved between platforms. Every migrated customer gets a password-reset prompt on first login. Send a heads-up email explaining the change so it doesn't read as a phishing attempt.

What happens to my custom Magento checkout logic?

It has to be rebuilt in Shopify Functions. Shopify Scripts reached full end-of-life on June 30, 2026, so there's no legacy path. Tiered discounts, buy-X-get-Y, bundled shipping, and customer-group pricing all become Functions written in Rust or JavaScript. Budget for it as real development work.

Can I migrate configurable products without breaking variants?

Yes, but not with the free Store Importer, which tends to flatten options. Use Matrixify with careful field mapping or Cart2Cart with a manual review pass. Always verify variant counts post-import -- a 3-color × 4-size configurable must show exactly 12 variants in Shopify.

Should I use Shopify or Shopify Plus?

If you need Functions for complex checkout logic, high API limits, more than a handful of staff accounts, or B2B features, Plus (around $2,300/month in 2026) is usually the right call for former Magento merchants. Smaller catalogs with standard promotions run fine on the Advanced plan.

What data should I not migrate?

Disabled products, bounced or duplicate customer records, and order history older than 12-24 months (archive it to CSV instead). Moving dead data slows the import, inflates your Shopify catalog, and creates noise in your reports. Migrate lean.

Is a headless Shopify build worth it during migration?

If performance and a custom frontend matter, migrating is the natural moment to go headless with Hydrogen or a framework like Next.js or Astro. You're rebuilding the storefront anyway. It adds scope but avoids a second replatform later -- worth discussing if your Magento theme was heavily customized.