Magento → Shopify Migration, 2026 edition.

Why Magento exits stall

Five things I clean up after when teams DIY a Magento exit or hire a generic migration shop: no 1:1 redirect map, which is the one that actually costs you money; configurable products mapped wrong, giving you duplicated variant SKUs and desynced inventory; customer accounts handled the old way, with a mass password reset at launch that locks out repeat buyers in your first week; B2B agreed-rate pricing erased; and schema and meta tags wiped. Each is recoverable on a redo, but expensive in lost months.

Modeling the catalog

Magento has a flexible product model — simple, configurable, bundle, grouped, virtual, downloadable. Shopify has products with up to 3 options and 100 variants per product. Translating between the two requires per-case judgment: configurables map cleanly to variants, bundles are best modeled as Shopify "kits" via an inventory app or as a parent product with line-item discounting, grouped products usually become collections, virtual/downloadable map to Shopify's digital-product flow.

Customer + order migration

Customer export from Magento covers names, emails, addresses, custom attributes, and order history. Passwords do not transfer, because Magento hashes are not Shopify hashes and nobody can read them back. The old answer to this was a mass forced reset at launch, which locks people out in your first week and quietly costs you repeat orders. Shopify's passwordless customer accounts remove the problem: the customer enters their email, receives a six-digit code, and is in, with order history attached by email match. Launch on those and there is no reset wave at all. Order history itself can be imported as draft orders (full record) or as metafield archives (lighter, support lookup only). Pick based on what your support team actually needs.

The 1:1 redirect map

The single highest-leverage SEO discipline in a migration. Generate a CSV mapping every Magento URL (category, subcategory, product, CMS page) to its Shopify equivalent. Audit manually for top traffic pages. Deploy as 301 redirects in Shopify's "URL Redirects" admin or via the bulk-redirects API. Resubmit sitemap to Search Console. Monitor Search Console crawl errors daily for the first 30 days.

B2B agreed-rate pricing

Magento's B2B module supports rich per-customer and per-company pricing with NET-30 terms. Shopify rebuilds this with companies, catalogs, volume pricing and payment terms, plus Functions where the price logic is genuinely custom. The important 2026 change: this is no longer Plus-only. The standard paid plans now carry B2B, with a cap on the number of catalogs. Plus still wins for unlimited catalogs and the more advanced B2B checkout work. So the honest scope is to check whether your wholesale operation actually needs Plus, rather than assuming it does, because that assumption costs about $2,000 a month.

Payment + fulfillment rewire

Authorize.Net / Braintree / Stripe / Shopify Payments configuration. Gift cards migrated (Shopify's API supports importing existing gift-card codes + balances). Subscriptions (if any) need a parallel migration to ReCharge or Bold or Shopify's native subscriptions. Fulfillment routing — ShipStation, ShipBob, third-party warehouses — all reconnected. Apps + integrations (ERP, WMS, Klaviyo, GA4, Meta CAPI) reconnected before cutover.

SEO preservation discipline

Beyond the redirect map: meta titles + descriptions migrated 1:1 (don't let the new theme overwrite them with defaults), alt text preserved, canonical tags rebuilt, schema markup rebuilt to match (product, organization, breadcrumbs, FAQ), sitemap regenerated, robots.txt rebuilt to match Magento's allow/disallow rules. Search Console + Bing Webmaster Tools resubmission on launch day.

Cutover plan

A written cutover plan with rollback procedure: pre-cutover checklist (DNS TTLs lowered, comms drafted, backups verified), cutover window (low-traffic, typically 2-6am client local), DNS swap, verification (top URLs return 200, redirects work, cart/checkout work end-to-end), post-cutover sweep (sitemap submission, broken-link check, real-customer test orders). Rollback path documented and tested before the cutover.

30/60/90-day monitoring

Search Console crawl-error monitoring daily for 30 days. Organic-traffic delta tracked in GA4 / Plausible / your analytics. Conversion-rate monitoring vs. pre-launch baseline. Customer-support ticket sweep for migration-related issues (forgotten passwords, lost loyalty points, missing order history). Written report at day 30 and day 60 with recovery trajectory and any remaining tail items to fix.

When to migrate to Shopify (not Plus)

This advice changed in 2026 and most of what you will read online has not caught up. B2B is no longer Plus-only: companies, catalogs, volume pricing and payment terms now work on the standard paid plans, with a cap on how many catalogs you get. So "we do wholesale, therefore we need Plus" is no longer true, and it is an expensive assumption to inherit. Standard Shopify (Advanced) is fine when B2B is modest, you need no custom checkout logic, you are single-store and single-currency, and you are below roughly $1M a month. Plus earns its money for B2B at real scale, custom checkout via Checkout Extensibility, multi-store and multi-region, advanced cart logic in Functions, and dedicated launch support. Check before you commit. Plus is roughly $24K a year more than Advanced. Also note Shopify Scripts are gone; they stopped executing on 30 June 2026 and that logic now lives in Functions.

When to consider WordPress + WooCommerce instead

For B2B catalogs that are mostly content + light commerce (RFQ-driven, manual quotes, NET terms), WooCommerce on a custom theme is sometimes the right answer instead of Shopify. The post on /magento-to-wordpress-b2b-migration-romsons/ walks through a real case where it was. Cost is comparable; ongoing TCO is lower; flexibility is higher; the trade-off is more dev work to maintain Woo + plugins vs. Shopify's managed platform.