Magento migration

Magento to Shopify Plus migration

OUXP moves Magento 1 and 2 stores to Shopify Plus for teams tired of paying for patches, upgrades and hosting – with products, customers and order history intact. The catalog is restructured for Shopify’s product model, checkout and B2B are rebuilt natively, and a 301 map covering every URL pattern is live at launch to protect your search rankings.

Reviewed by the OUXP engineering teamUpdated

Best for
Magento 1 and 2 stores, including heavily customized and multi-store builds
Magento 1
Migrated directly – no Magento 2 upgrade first
Timeline bands
8–12 weeks standard · 12–18 B2B · 18–24+ enterprise
Pricing
From $50,000, fixed before work starts
Downtime
Minimal, with a rehearsed cutover
SEO preservation
Included in every migration
Integrations
ERP, CRM, PIM, OMS and WMS reconnected
After launch
Retainer support, first response within 30–⁠60 minutes in business hours

Why teams move off Magento

Magento can run a serious store. What wears teams down is the work of keeping it running – patches, upgrades, hosting and extension conflicts – which takes budget and attention away from selling.

  • 01

    Magento 1 runs unpatched

    Magento 1 reached end of life on June 30, 2020. A store still on it runs without official security fixes, and PCI compliance gets harder to defend every year.

  • 02

    Upgrades turn into projects

    A new Magento 2 version means updating extensions, custom modules and the theme together – often a project the size of a small rebuild.

  • 03

    Every patch needs regression testing

    Each security patch has to be tested against every extension and custom module before it goes live, and conflicts are common.

  • 04

    Hosting is your job

    Servers, Elasticsearch or OpenSearch, Redis and Varnish need tuning, patching and scaling for peak days – by your team or a managed host.

  • 05

    Speed depends on tuning

    Storefront and admin performance depend on hosting, caching and indexers, so every slowdown is yours to diagnose.

  • 06

    Budget goes to upkeep

    Specialist Magento development is expensive, and much of it pays for keeping the platform current rather than for new features.

On Adobe Commerce, the licensed edition of Magento? Adobe Commerce to Shopify Plus migration

Magento vs Shopify Plus: what changes for your team

The operational differences in one table. The full guide adds total cost of ownership, security and developer experience.

Magento vs Shopify Plus at a glance
CriteriaMagentoShopify Plus
Hosting and serversYou run it
AWS, Azure, GCP or a managed host – or Adobe’s cloud on Adobe Commerce
Included
Managed by Shopify
Security patches and core updatesManual
Tested against every extension
Automatic
Version upgradesA project each timeNone needed
The platform updates continuously
Performance and traffic peaksYou tune and scale it
Speed depends on hosting, caching and indexers; servers are scaled up for peak days
Managed by Shopify
Infrastructure scales automatically for flash sales and peak traffic
PCI complianceYours or shared
Yours on Open Source; shared with Adobe on its cloud
Included
Shopify is a PCI DSS Level 1 platform
Checkout customizationFull code accessExtensible
Checkout Extensibility and Shopify Functions
Extensions and appsVia extension
Installed into your codebase
Via app
Updated by each app’s vendor
Platform feeOpen Source: no license fee. Adobe Commerce: typically $22,000–$125,000+ a year (estimate)From $2,300/month on a three-year term, or $2,500/month on a one-year term; high-volume stores move to a revenue-based variable fee

Broad comparison; details vary by project. Shopify pricing and platform facts as of October 2026; the Adobe Commerce license range is an industry estimate.

When staying on Magento is the right call

Stay when deeply custom checkout or catalog logic is core to how you sell, you run a dedicated engineering team, or you need full control of your infrastructure. If that describes your store, the free migration assessment says so.

What moves to Shopify Plus – and what gets rebuilt

Data moves with its history. Extensions and custom code can’t transfer between platforms, so they are replaced or rebuilt. Discovery inventories every data type, extension and integration, and you sign off the list before the build starts.

Migrated

  • Products and variants
  • Categories as collections
  • Product attributes
  • Images
  • Inventory
  • Customers and addresses
  • Order history
  • Reviews and ratings
  • Gift card balances
  • Active subscriptions
  • Blog posts
  • CMS pages
  • SEO metadata
  • URLs as 301 redirects

Internal IDs don’t carry over between platforms; the relationships do – each order with its customer and products, each product with its variants and images. Old order and customer numbers that support, finance or connected systems rely on are kept for reference.

Rebuilt or reconnected

  • Extensions, as Shopify apps
  • Custom modules
  • Cart price rules and promotions
  • Checkout customizations
  • B2B accounts and pricing
  • ERP
  • CRM
  • PIM
  • OMS and WMS
  • Payment and shipping providers
  • Analytics and tracking

Passwords can’t move – Shopify can’t read Magento’s password hashes – so returning customers sign in with a one-time code sent by email. The stored payment details behind subscriptions and data held in third-party apps – loyalty points, wishlists – are investigated in discovery, never assumed.

What actually makes a Magento migration hard

Moving data is the easy part. These five problems decide whether a Magento migration lands on time, so we scope each one before quoting – not halfway through the build.

  1. Configurable products can outgrow Shopify’s three options

    How we solve it

    Shopify allows up to 2,048 variants per product, but still only three options – size, color and material, say. Magento configurables with more options, or very large option matrices, need a new product model: we split them into separate products shown together as one listing, move choices that filter rather than sell into metafields, or rationalize combinations against your real order history. You approve the variant strategy before anything is built.

  2. Magento attributes have no Shopify column

    How we solve it

    Magento’s EAV attribute sets give each product type its own fields; Shopify’s product schema is fixed. Descriptive attributes become metafields, and structured data – fitment tables, spec sheets, ingredient panels – becomes metaobjects your theme displays and your filters use. You approve the attribute-to-metafield map before any data moves.

  3. Every URL changes – by Shopify’s design

    How we solve it

    Magento URLs such as /category/product.html and layered-navigation filter URLs can’t exist on Shopify, which uses fixed /products/, /collections/ and /pages/ paths. We export your full URL set with its rewrite history, build a per-pattern 301 map, carry over titles, meta descriptions and canonicals, rebuild structured data and monitor rankings through cutover. Filter URLs are where Magento SEO risk concentrates, so we decide them pattern by pattern – never with a blanket redirect.

  4. Your custom checkout doesn’t port – it’s re-architected

    How we solve it

    On Shopify Plus you don’t own the checkout code: checkout.liquid is retired, and Shopify Scripts stopped running on June 30, 2026. Cart price rules, promotion logic and checkout customizations are rebuilt with Checkout Extensibility – checkout UI extensions, Shopify Functions, branding and web pixels. We itemize that rebuild at discovery from your modules and sales rules, so it is never a surprise mid-project.

  5. B2B moves to Shopify’s native B2B

    How we solve it

    Company accounts, shared catalogs, tier pricing and net terms map to Shopify’s native B2B: companies, catalogs with price lists, payment terms and draft orders for quoting. Core B2B has run on every paid Shopify plan since April 2, 2026; Plus adds deposits, more than three catalogs and catalogs assigned to specific companies. Quote and approval workflows with custom approval chains need a light rebuild, scoped up front.

What replaces your Magento extensions?

Every extension is replaced by an app, rebuilt as custom code or retired – because Shopify covers it natively or you no longer need it. These are the most common mappings; your full list is itemized during discovery.

Extension mapping: what replaces what
On MagentoOn Shopify Plus
Klaviyo Magento extensionKlaviyo for Shopify
Review extensions such as Yotpo or BazaarvoiceThe same vendors’ Shopify apps, or Okendo or Judge.me, with ratings and review history imported
Subscription modulesRecharge, Skio or Shopify Subscriptions, with active subscribers migrated
Avalara AvaTaxShopify Tax, or Avalara Tax Compliance for Shopify
ShipperHQ or ShipStationThe same vendors’ Shopify integrations
Search and merchandising modulesShopify Search & Discovery, Algolia, Klevu or Rebuy
Payment modulesShopify Payments with Shop Pay, Apple Pay and Google Pay, plus PayPal, Affirm or Klarna
B2B modules, or the Adobe Commerce B2B suiteNative Shopify B2B: companies, catalogs, payment terms
ERP connectors (NetSuite, SAP, Dynamics)Celigo, Boomi or custom Admin API middleware – see commerce integrations
Custom modules and sales rulesShopify Functions, checkout UI extensions and custom apps, itemized at discovery

Common mappings, not a fixed list. Apps and Shopify features as of October 2026; app subscriptions are billed by their vendors and are not part of the migration price.

How long does a Magento migration take?

8–⁠24+ weeks. Timeline tracks complexity more than catalog size, and most Magento migrations fall into one of three bands.

  1. Standard

    8–12 weeks

    Magento 1 or 2, a catalog that fits Shopify’s product model, a common app stack, one store.

  2. B2B or mid-complexity

    12–18 weeks

    B2B accounts and tier pricing, ERP integration, option matrices to restructure, checkout customization.

  3. Enterprise

    18–24+ weeks

    Multi-store, heavy custom modules, large catalogs and complex Shopify Functions logic.

What does a Magento migration cost?

Typically $50,000–⁠$180,000, starting at $50,000 for a standard project – with a fixed price agreed before work starts.

  • Not in the migration price: the Shopify Plus subscription (from $2,300/month on a three-year term, as of October 2026) and app subscriptions, billed by Shopify and each app’s vendor.
  • What moves the price most: option matrices, custom checkout logic, B2B requirements, integrations and design scope.
  • SEO preservation – URL map, 301s, metadata, structured data and post-launch monitoring – is always included.
  • A hosting contract or license renewal coming up? Plan the cutover before it so you don’t pay for two platforms – enterprise builds should start 6–9 months ahead.

How a Magento migration runs

Seven steps, each with an output you check before the next one starts. Your team’s time goes mainly into approving the maps, reviewing the build and signing off QA and the launch rehearsal.

  1. 1

    Discovery

    Inventory data, extensions, integrations, URLs and the behaviors your business relies on.

    Output: written inventory and plan

  2. 2

    Mapping

    Decide where everything goes: variant strategy, attribute-to-metafield map, extension map and 301 map.

    Output: maps you approve

  3. 3

    Build

    Theme, apps, Shopify Functions, checkout extensions and integrations, in a separate development store.

    Output: a working store to review

  4. 4

    Pilot and reconcile

    Import a representative sample, compare counts, totals, keys and links with Magento, then fix and repeat.

    Output: reconciliation report

  5. 5

    QA and launch rehearsal

    Test functionality, checkout, integrations, SEO and page speed, take your team’s sign-off, then run the cutover end to end, including redirects, payments, B2B checkout and order flow.

    Output: QA sign-off, tested cutover and rollback plan

  6. 6

    Launch

    Freeze changes, import the final delta of orders and customers, switch the domain and verify checkout.

    Output: live store, verified

  7. 7

    Monitor and optimize

    Watch orders, errors, rankings, support requests and Core Web Vitals, tune speed and conversion, then hand over to your team or to an OUXP retainer and maintenance plan.

    Output: handover

Why Magento teams choose OUXP

  • Commerce engineers since 2011

    We built on Magento and Adobe Commerce before Shopify Plus, so we know where a Magento store keeps its business logic: modules, sales rules and attribute sets.

    15+ years · 300+ projects delivered

  • The projects others turned down

    “…We have had some complex needs on our site, where other developers have said it could not be done. ‘Outstanding Experience’ has been able to get it done every time.”

    Wall Snobs, via Shopify Partner Directory (external site)

  • A fixed price you can plan around

    Variant strategy, checkout rebuild and integrations are scoped before we quote, so the fixed price and timeline reflect what your store actually needs.

    Fixed before work starts

  • AI-accelerated engineering

    AI tools take the repetitive parts of a migration, so engineer hours go to the decisions – and a senior engineer reviews every change before it ships.

    Used for data mapping, test suites, code review and QA

  • Performance first

    Page speed is part of how we build the new store, and performance optimization – typically a 2–⁠4 week project – is there after launch, as your catalog and app stack grow.

    Core Web Vitals checked before and after launch

  • Support after launch

    Retainers from $2,500 a month cover fixes, optimization and ongoing Shopify Plus development after launch – or add a dedicated engineer to your team. 24/7 emergency coverage is an add-on, included on the Dedicated tier.

    First response within 30–⁠60 minutes in business hours

Catalog, B2B and migration work

Two Shopify builds that carry the catalog depth and B2B pricing a Magento store usually brings, and a store migration in the client’s own words, quoted from the Shopify Partner Directory.

  • CleanFlow

    Industrial supply · Canada

    Thousands of SKUs, wholesale pricing and CAD/USD selling in one storefront

    We built a deep mega-menu taxonomy, a wholesale account portal and Canada and US markets, keeping navigation fast across the full catalog.

  • Wall Snobs

    Luxury wallcoverings · USA

    A trade-only channel with gated pricing, sample orders and custom requests

    We built trade applications with approval, logged-in-only pricing, a sample order flow and a custom-request pipeline straight to the print studio.

  • Rated 5 out of 5

    “OUXP was highly communicative and quick to respond. Store migration is successfully done by a top-notch team on Shopify. They met the requirements and provided high-quality work, just as requested.”

    Lordstown Motorsvia Shopify Partner Directory (external site)Store migration

Which timeline band and cost range fit your store? Get a free written answer in 2 business days – no store access needed.

Magento migration questions

Something else on your mind? Ask an engineer – first response within 30–⁠60 minutes in business hours.

We’re still on Magento 1 – can we migrate straight to Shopify Plus?

Yes, and you don’t need to upgrade to Magento 2 first. Moving Magento 1 directly to Shopify Plus is usually faster and cheaper than an M1-to-M2 upgrade, and it ends your security-patch exposure for good – Magento 1 has had no official patches since June 30, 2020. Products, customers, order history and URLs move the same way they do from Magento 2.

Is upgrading Magento cheaper than migrating to Shopify Plus?

Not over time. A major Magento upgrade often costs nearly as much as a migration, and afterwards you still pay for the same hosting, patching and extension maintenance. Upgrading still makes sense if your business depends on deep backend customization and you have an engineering team to maintain it. Our free assessment shows which way the numbers point for your store, and the Magento vs Shopify Plus guide compares both in detail.

How long does a Magento to Shopify Plus migration take?

8–⁠24+ weeks, depending on complexity. Standard Magento 1 or 2 stores with a catalog that fits Shopify’s product model take 8–12 weeks. B2B stores with ERP integration, option matrices to restructure or checkout customization take 12–18 weeks. Multi-store builds with heavy custom modules take 18–24+ weeks. The free migration assessment places your store in a band, and a fixed timeline with milestones is agreed before work starts.

How much does a Magento to Shopify Plus migration cost?

Most Magento migrations cost $50,000–⁠$180,000, starting at $50,000 for a standard project. Complexity moves the price more than catalog size: option matrices, custom checkout logic, B2B requirements, integrations and design scope. A free assessment gives you a cost band, and the price is fixed before work starts, with SEO preservation always included. Shopify Plus itself starts at $2,300 a month on a three-year term, as of October 2026.

Will we lose search rankings when we leave Magento?

Not when the migration is planned for it, though nobody can honestly promise rankings won’t move at all. Every Magento URL changes – .html product and category paths, store-view URLs and layered-navigation filter URLs – so we export the full URL set with its URL rewrite history, build a per-pattern 301 map and decide filter URLs pattern by pattern rather than sending them all to one page, carry over titles, meta descriptions and canonicals, rebuild structured data and monitor rankings and crawl errors after launch. SEO preservation is part of every migration, never an add-on.

Can customer passwords be migrated from Magento?

No – Shopify can’t use Magento’s password hashes, so passwords themselves don’t transfer. Customer accounts, addresses and order history do. With Shopify’s customer accounts, customers sign in with a one-time code sent by email, so no password is needed. We plan the launch emails so returning customers know what to expect the first time they sign in.

Will our store design carry over, or do we get a new one?

Magento themes can’t run on Shopify, so the storefront is always rebuilt as a Shopify theme. You choose how far that goes: recreate your current design closely, refresh it during the rebuild, or start a full redesign. Design scope is one of the biggest price drivers, so we agree it with you during scoping and fix it in the quote before work starts.

Will the store be down during the migration?

Your Magento store keeps trading while we build and test Shopify Plus in a separate store. At cutover we freeze changes, import the final delta of orders and customers, switch the domain and verify checkout – a sequence we rehearse end to end beforehand. Downtime is minimal, and we time the switch with you, away from peak trading hours.

Ready to leave Magento?

Send your store URL and current setup. Within 2 business days an engineer sends a free written assessment: platform verdict, timeline band, cost band and the risks specific to your store – yours to keep whether or not you hire us.