Magento → Shopify Plus Replatform
Magento to Shopify Plus Migration
Replatform from Magento / Adobe Commerce to Shopify Plus — resolving the variant-ceiling constraint on Magento's configurable matrices, projecting EAV attributes into metafields and metaobjects, re-architecting checkout on Checkout Extensibility and Shopify Functions, and converting the .html + layered-navigation URL surface into prefixed /products/ handle 301s. 200+ migrations completed on a documented no-data-loss cutover playbook with rollback paths.
Trusted by 400+ Brands · Certified Partners
Years in eCommerce
Of results, scale, and quality at the enterprise level.
Expert Team
Specialists across SEO, AI SEO, PPC, design, dev, and strategy.
US Core + Global Talent
US core team for clear communication; vetted global specialists for international client work.
Reputation Score
Rated 4.9/5 across 941+ verified client reviews.
Reviewed by the 1Digital® Migration TeamLast updated:
TL;DR
1Digital® migrates merchants off Magento 1, Magento 2, Adobe Commerce, and Adobe Commerce Cloud onto Shopify Plus — Online Store 2.0, Hydrogen on Oxygen, Checkout Extensibility, Shopify Functions, and native B2B on Shopify. Configurable variant matrices are resolved against Shopify's variant model, EAV attributes become metafields/metaobjects, sales rules become Functions, and the .html + layered-navigation URLs are converted into prefixed /products/ handle 301s with a rebuilt schema graph.
Related: All platform migrations · Magento → BigCommerce · Shopify Plus Agency · Shopify Plus Developer · Magento Developer · Data Migration
Why Replatform
Specific Magento Pain → Shopify Plus Gain
Variant ceiling: the 100/3 constraint
Shopify products historically capped at 100 variants and 3 options per product (the newer expanded limits still differ sharply from Magento's unbounded configurable matrices). A Magento configurable with size × color × material × length routinely exceeds that. We resolve it with split products, metaobject-backed option references, or a variant-rationalization plan agreed before the build — this is the defining scoping question of a Magento → Shopify Plus project.
EAV attributes become metafields & metaobjects
Magento's EAV attribute sets do not have a direct Shopify column. Descriptive attributes become product metafields; relational attributes Magento stored in EAV (fitment, spec sheets, ingredient panels) become Shopify metaobjects referenced from products and surfaced through the Storefront API and Liquid.
Shop Pay is the conversion argument
Shop Pay's one-tap accelerated checkout and network-effect login across Shopify's buyer graph is the strongest single conversion lever moving off a Magento checkout. Combined with Checkout Extensibility, you customize checkout through extensions instead of forking checkout.liquid or owning the checkout codebase.
Shopify Functions replace sales rules
Magento cart-price/sales rules and promotion logic re-express as Shopify Functions — discount, shipping, payment, cart, and delivery customizations that run on Shopify's infrastructure at millisecond latency, with no Magento promotion-engine or queue workers behind them.
B2B on Shopify, not the Wholesale Channel
Adobe Commerce B2B Suite maps to native B2B on Shopify (Companies, Locations, Buyer Roles, Catalogs, quantity rules, percentage/fixed price-list overrides, Net terms, draft-order quoting) — no longer the legacy Plus Wholesale Channel.
Hydrogen + Oxygen vs PWA Studio
Hydrogen (React + Remix) on Oxygen is Shopify's first-party headless stack — a maintained alternative to Magento PWA Studio / Venia, with the Storefront API and Oxygen edge hosting instead of a self-run Node tier.
What We Migrate
The Records Your Migration Has To Carry
Field-level mapping with referential integrity — the EAV catalog, configurable matrices, Customer Groups, tier prices, and B2B workflows all carry across, with variant strategy agreed before data moves.
Catalog & variant matrices
Simple, configurable, grouped, bundle, virtual, downloadable types → Shopify products + variants. Configurable matrices that exceed Shopify's variant/option limits are split or moved to metaobject-backed option references per an agreed rationalization plan.
EAV → metafields/metaobjects
Descriptive EAV attributes → product metafields; relational EAV data (fitment, specs, ingredients) → Shopify metaobjects referenced from products and surfaced via Storefront API + Liquid.
Customers & segments
Customer accounts, addresses, Customer Groups, wishlists → Shopify customers + segments + B2B Companies where applicable. Passwords reset-on-first-login (Shopify requirement).
Orders & store credit
Full orders, line items, fulfillments, refunds, native store credit, and gift cards preserved for revenue reporting, LTV, and support continuity.
Tier prices → B2B Catalogs
Catalog rules, tier prices, customer-group prices → B2B on Shopify Catalogs with quantity rules and percentage/fixed price-list overrides. Negotiable quotes → draft-order quoting or a B2B app (BSS, Sparklayer).
MSI → Locations
Multi-Source Inventory sources → Shopify Locations with stock levels and reservation behavior preserved where the model maps cleanly.
CMS → Pages/metaobjects
CMS pages, blocks, Page Builder content → Shopify Pages + Online Store 2.0 sections + metaobjects. Blog posts → Shopify Blog. Slugs preserved or 301'd to Shopify's prefixed paths.
Reviews & UGC
Yotpo, Okendo, Judge.me, Loox, Bazaarvoice preserved with star ratings, verified-buyer flags, and AggregateRating schema continuity for AI-engine citations.
How We Migrate
Six-Phase Migration Framework
Magento audit & variant-ceiling scoping
Inventory modules (composer.json + app/code), custom code, B2B Suite workflows, ERP/PIM integrations, sales rules, and — critically — every configurable-product option matrix that may exceed Shopify's variant/option limits. The variant-rationalization decision is made here, before quote.
EAV data audit & URL inventory
Catalog count, EAV attribute density, configurable fan-out, customer/order volume, media library, CMS pages, and the full layered-navigation canonical URL set. Produces data-parity targets and a URL-mapping spreadsheet that respects Shopify's mandatory path prefixes.
URL & schema mapping
Magento /<category>/<product>.html and layered-nav facet URLs → Shopify /products/<handle>, /collections/, /pages/, /blogs/ with 301 rules, canonical strategy, and a rebuilt schema graph (Product, BreadcrumbList, FAQPage, Organization) with consistent @id references, hreflang re-anchored to Markets.
OS 2.0 / Hydrogen build & EAV projection
Online Store 2.0 theme or Hydrogen storefront. Iterative loads with parity reports: EAV → metafields/metaobjects, Customer Groups → B2B companies, tier prices → Catalogs, orders, reviews. Apps, Functions, and Checkout UI Extensions configured against staging.
Cutover & DNS
Freeze Magento writes, sync the final delta (orders, customers, inventory), flip DNS at low TTL, and validate checkout, Shop Pay, Functions, Markets, GA4, Consent Mode v2, and pixels live. Cutover window typically under 60 minutes.
Post-launch QA & monitoring
30+ days of crawl-error triage, Search Console change-of-address, ranking and AI-citation monitoring, Core Web Vitals tracking, B2B workflow validation, Shop Pay uplift validation, and an edge-case fix sprint.
Extension Mapping
Magento Extension → Shopify Plus Equivalent
The third-party stack you depend on rarely needs to change — only the connectors and the host platform. Custom Magento modules and sales rules are the line items that rebuild as Functions and extensions.
| Magento / Adobe Commerce | Shopify Plus Equivalent |
|---|---|
| Adobe Sensei Live Search / Product Recs | Shopify Search & Discovery (native), Searchspring, Algolia, Klevu, Nosto, Rebuy |
| Magento Klaviyo extension | Klaviyo for Shopify (native, deepest integration of any platform) |
| Yotpo / Bazaarvoice / Okendo / Judge.me | Same vendors with native Shopify connectors |
| Avalara AvaTax for Magento | Shopify Tax (built-in) or Avalara AvaTax for Shopify |
| ShipperHQ / ShipStation / Temando | Shopify Shipping, ShipperHQ, ShipStation (native) |
| Magento Subscriptions / Aheadworks recurring | Shopify Subscriptions, Recharge, Bold, or Awtomic |
| Stripe / Braintree / PayPal Magento modules | Shopify Payments + Shop Pay + Apple Pay + Google Pay + PayPal + Affirm + Klarna |
| Adobe Commerce B2B Suite | B2B on Shopify (Companies, Locations, Buyer Roles, Catalogs, Net Terms — native) |
| PWA Studio / Venia / Hyvä | Hydrogen (React + Remix) on Oxygen, or Online Store 2.0 themes |
| Custom Magento modules / sales rules | Shopify apps, Shopify Functions, Checkout UI Extensions, Hydrogen components |
| NetSuite / SAP / Dynamics connectors | Celigo, Boomi, MuleSoft, or custom Shopify Admin GraphQL middleware |
The Technical Reality
What Actually Makes Magento → Shopify Plus Hard
Shopify's variant ceiling is the project-defining constraint
Magento configurable products have no practical option ceiling — a product can carry size × color × material × finish × length with thousands of resolvable simples behind it. Shopify's product model is fundamentally different: historically 100 variants and 3 options per product, and even with Shopify's expanded variant limits the model does not match an unbounded Magento configurable matrix one-for-one. This is not a data-volume problem; it is a data-model problem, and it is the first thing we scope.
Resolution paths are: split a single Magento configurable into multiple Shopify products grouped by a shared metaobject; move non-purchasable selectors (a spec the buyer filters on but does not buy a variant of) into product metafields/metaobjects instead of variant options; or rationalize the matrix where Magento carried option permutations that never actually sold. We model your real order history against each configurable to recommend the path, and you approve the variant strategy before the build starts — discovering it at data-load is the classic Magento → Shopify Plus failure mode.
Magento URLs → Shopify's mandatory prefixed handles
Magento product URLs are /<url_key>.html (optionally category-pathed), with a url_rewrite history table and crawlable layered-navigation facet URLs (?price=, ?color=, multi-select). Shopify enforces non-negotiable resource prefixes: products live at /products/<handle>, categories become /collections/<handle>, content at /pages/, the blog at /blogs/. There is no .html, no arbitrary nesting, and the handle is derived from the title. Every Magento URL changes, and the prefix structure is not configurable.
We export the complete Magento URL set including the url_rewrite table and the indexed facet URLs, then build a per-pattern 301 map: /<category>/<product>.html → /products/<handle>, category → /collections/<handle>, CMS → /pages/<handle>, with facet URLs decided individually (301 to a Shopify Search & Discovery filtered collection, redirect to the parent collection, or canonicalize away). Shopify URL redirects are applied at the platform level and verified post-launch with crawl tooling and Search Console. The facet-URL decisions are where most of the SEO risk on this route concentrates.
Checkout Extensibility, Functions, and B2B re-architecture
Magento merchants who customized checkout via layout XML, controller overrides, or a forked checkout commonly assume that flexibility ports. On Shopify Plus you do not own the checkout codebase — Checkout Extensibility replaces the legacy checkout.liquid model with checkout UI extensions and Shopify Functions. Custom Magento cart-price rules, multi-step approval flows, and gift/promotion logic are re-implemented as Functions and extensions, which is a rebuild, not a lift-and-shift, and is scoped explicitly.
Adobe Commerce B2B Suite (Company accounts, Shared Catalogs, Requisition Lists, Negotiable Quotes) maps to native B2B on Shopify (Companies, Locations, Buyer Roles, Catalogs with quantity rules and price-list overrides, Net terms, draft-order quoting). Negotiable-quote and punchout flows with custom approval chains usually need a light rebuild via Shopify's quote APIs or a B2B app (BSS B2B, Sparklayer). ERP-linked pricing flows through the Shopify Admin GraphQL API. Every module from composer.json and app/code is cataloged at discovery so the Functions/extensions rebuild list is on the quote.
SEO Equity Protection
Keep the Rankings, Citations, and Traffic You've Earned
Migrations that lose SEO equity lose months of revenue. On this route the variant-ceiling decisions and the facet-URL 301s are the highest-risk surfaces — both are release-blockers, not afterthoughts.
- Full Magento URL export including the url_rewrite table and indexed layered-navigation facet URLs.
- Page-level 301 map respecting Shopify's mandatory prefixes — Magento /<category>/<product>.html → /products/<handle>, category → /collections/<handle>, CMS → /pages/, blog → /blogs/, facet URLs decided per pattern.
- Per-URL title, meta description, canonical, hreflang, and Open Graph carryover; Markets hreflang handled at the Shopify Markets layer.
- Schema graph rebuilt with consistent @id references (Organization, Product, BreadcrumbList, FAQPage, AggregateRating) so ChatGPT, Perplexity, Gemini, and AI Overviews keep citing the brand.
- XML sitemap regeneration, llms.txt continuity, robots.txt parity, and a formal Search Console change-of-address.
- Core Web Vitals targets baked into the Online Store 2.0 theme or Hydrogen build — LCP under 2.5s, INP under 200ms, CLS under 0.1. Shopify's CDN + Oxygen edge typically lifts a self-hosted Magento LCP materially.
- 30+ days of post-launch monitoring: crawl errors, Search Console coverage, ranking deltas, AI-citation share, and conversion-rate parity (Shop Pay uplift baseline).
Timeline & Engagement
Typical Engagement Bands
8–10 weeks
Standard B2C
Mid-size catalog within Shopify's variant model, standard checkout, common app stack (Klaviyo, Yotpo, ShipStation), 2 payment gateways, single store, Online Store 2.0 theme.
12–16 weeks
B2B / Mid-complexity
B2B on Shopify (Companies, Catalogs, Net terms), tier prices → Catalogs, ERP/NetSuite, Avalara, configurable matrices needing rationalization, Checkout UI Extensions.
18–24+ weeks
Hydrogen / Headless / Enterprise
Hydrogen on Oxygen, complex Shopify Functions logic, Markets multi-region, custom Magento modules with no clean equivalent, large catalog (50K+ SKUs), heavy variant-matrix re-modeling.
Engagements start at $185/hour. Fixed-fee proposal after discovery, sized to your catalog, configurable-matrix complexity, integrations, B2B requirements, and target architecture.
Request a Proposal
Tell us about your Magento store
Share your Magento version (M1, M2, Adobe Commerce, Adobe Commerce Cloud), configurable-product option complexity, checkout customizations, B2B Suite usage, ERP/OMS, and non-negotiables. A senior strategist responds within one business day with a pricing band and a draft migration roadmap.
FAQ
Magento → Shopify Plus FAQs
How long does a Magento to Shopify Plus migration take?
What happens to Magento configurable products with huge variant matrices?
How do Magento's EAV attributes map to Shopify?
Can we keep our customized Magento checkout on Shopify Plus?
How does Magento B2B move to B2B on Shopify?
Will there be downtime at cutover?
Replatform from Magento to Shopify Plus — without losing what you've built.
Free migration audit. Fixed-fee proposal. Variant strategy approved before data moves. 200+ migrations run on a documented no-data-loss cutover playbook.