Migration
Magento and Adobe Commerce
to Shopify Plus
Adobe Commerce 2.4.4 extended support ended on 14 April 2026 and 2.4.5 on 11 August 2026, while Adobe pushes Open Source users toward paid Cloud licensing.
The case for moving is usually cost: a total cost of ownership several times the managed alternative, and a stack that needs a developer on call to stay upright.
What the deadline means
On a self-hosted store, nothing switches off. It takes orders the morning after end of support exactly as it did the night before. Adobe Commerce Cloud is different: from 1 June 2027 Adobe suspends traffic to Cloud environments still running an unsupported version, and the storefront goes offline.
What stops first is ordinary maintenance from Adobe. 2.4.4 and 2.4.5 are in a one-time security-only period until 31 May 2027: limited, isolated security fixes and no quality fixes. After that, every newly disclosed vulnerability in the platform is yours to fix, back-port or carry. Extension vendors drop the version at their own pace. And a store handling card data is expected, under PCI DSS, to run software that still receives vendor security updates, so the compliance position weakens as the fixes run out.
On a self-hosted store the risk rises steadily. On Cloud it ends on a set date. Either way it puts a clock on the decision: every store on these versions faces the same 31 May 2027 date, so the partners able to deliver the work get busier as it approaches.
Adobe Commerce 2.4.4 extended support ended on 14 April 2026 and 2.4.5 on 11 August 2026. Security-only fixes for both end on 31 May 2027. All three are Adobe's own published lifecycle dates.
Catalogue size changes what the project is
"Migration" covers three different pieces of work, and a quote should say which one it's pricing.
Around 5,000 SKUs
The data moves cleanly and most of the work is elsewhere: theme, checkout, integrations, redirects. The catalogue is small enough to check by hand at the end.
Around 40,000 SKUs
Attribute mapping becomes the project. Magento's attribute sets and configurable products don't map one-to-one onto Shopify's option model, and the reconciliation is where the time goes. Sampling replaces inspection, so the sampling method has to be agreed up front.
200,000 SKUs and up
At this size it's a data-engineering job with a storefront attached. Import limits, variant ceilings and the source of truth for the catalogue all become design decisions, and the catalogue's real home is often the ERP rather than either platform.
At that size the real question is often a systems decision, with the migration standing in for it.
URLs and the redirect map
The redirect map costs money when it's left late. It belongs to nobody by default and can't be finished until the new URL structure is settled, so we start it in the first week.
Shopify's URL structure is fixed in ways Magento's isn't: products live under /products/, collections under /collections/, and a Magento store with category-nested product paths won't reproduce its old URLs. Every one needs a redirect, and the ones that matter most carry the most inbound links. That's a different list from the most-visited pages, and it comes from backlink data rather than analytics.
The failure mode
Rarely a missing redirect. Usually a chain of them.
An old URL pointing at a URL that itself redirects, two or three deep, each hop shedding a little authority and a little speed. The map is built and verified before cutover, then verified again against the live site afterwards, because a redirect that behaved on staging can be intercepted by a platform rule in production.
Extensions and custom logic
A mature Magento store can carry dozens of extensions, plus whatever was written into the codebase over the years. The first audit asks which of them are load-bearing, and that list is shorter than what's installed.
Native on Plus
Checkout customisation, multi-currency, staff permissions, wholesale pricing. Things Magento needed an extension for that Plus does in the platform. This column is where the cost-of-ownership saving comes from.
App equivalent
Reviews, subscriptions, loyalty, advanced search, feed management. Real equivalents exist; the work is choosing them and accepting that a subscription line replaces a licence line. Both belong in the cost model.
Has to be rebuilt
Bespoke pricing rules, unusual tax or shipping logic, anything reaching into an ERP or a warehouse system. This column is the real cost of the project, and it's sized by reading the code rather than asking what the store does.
It's also the only column that can't be estimated from a feature list, which is why quotes built from one go wrong.
B2B, customer groups and tier pricing
Magento's customer groups are a general-purpose mechanism: a group is a label any rule can hang off, and a store that has run for years will have built up rules against it. Shopify covers the same ground through company profiles, catalogues and price lists: a more structured model, built for wholesale, and a different shape.
Since April 2026 every Shopify plan supports B2B, and Plus lifts the limit of three catalogues. The migration question is whether your existing pricing logic survives translation into that model. Bespoke rules written against customer groups over a decade sometimes don't, and cutover is the expensive place to find out.
If you run retail and trade off one catalogue, this is often the reason the project is worth doing, and the reason it needs scoping before a price is quoted.
Payment terms
Every Shopify plan
Catalogues with their own pricing
Three on every plan, unlimited on Plus
Volume discounts and quantity rules
Every Shopify plan
Deposits and partial payments
Plus only
As Shopify states it, announced April 2026.
The other routes onto Plus
The work has the same shape wherever it starts: audit what's load-bearing, map the URLs early, rehearse the data, plan the rollback. What changes is where the difficulty sits.
Routes delivered
Magento, WooCommerce, Wix and EKM. Four routes onto Shopify, run end to end. EKM was the hardest: its export was non-standard, so we built the extraction from scratch.
Other source platforms
Shopware, PrestaShop, BigCommerce, Volusion. The same class of work, run with the same method.
On every route, what moves the quote is how much custom logic reaches into systems outside the store. A Magento store with nothing behind it can be a simpler project than a BigCommerce store wired into an ERP.
What it costs and how long it takes
Published agency rates for Magento to Shopify Plus migrations run from around $20,000 to well past $250,000, typically over two to six months. Those are the ranges Krish Technolabs and The Commerce Shop publish in their 2026 cost guides, read on 8 September 2026. The range is that wide because it runs from a small catalogue on a stock theme to a re-platform with ERP integration and a custom storefront. The number means little until the questions above are answered.
Crossdock's working band is £15,000 to £25,000 for a migration delivered as prime contractor, with £10,000 as a floor for a simple move. Above that band the project is usually carrying a systems decision as well, and it gets scoped and priced as two pieces of work rather than one.
What moves the number, in rough order: the rebuild column above, the number of systems the store has to keep talking to after the move, catalogue complexity rather than catalogue size, and whether the business can take a cutover window or needs both stacks running in parallel.
None of that includes the platform licence, which you pay Shopify directly. The full picture, licence and everything around it, is on Shopify Plus pricing.
What stands behind the practice
Crossdock is the operations practice of StoreBuilder Ltd, the company behind webuildstores.co.uk, storebuilder.co.uk and energypages.co.uk, and a Shopify Partner with client stores on Shopify and Shopify Plus.
We've delivered platform migrations onto Shopify from Magento, WooCommerce, Wix and EKM, along with the search, redirect and tracking work that decides whether a migration keeps its revenue. ERP, warehouse systems and specialist integrations go to specialist partners, named to you before you sign and working under one prime contract, so one company is accountable for the outcome rather than four.
The first step is the systems review, a short structured read of what your store contains and what the move involves. It's free.
More on how a project runs: the sequence and the cutover, what goes wrong and why, and the systems review itself.
Tell us what you need
What the systems are doing now, and what you need them to do. We'll tell you whether it's a platform problem or something cheaper.