The short answer
Retailers leave Magento for one reason more than any other: the cost of keeping it running. Hosting, security patches, version upgrades and the developers who manage them add up, and none of that money makes the store sell more.
Shopify takes that whole layer away. In return, it asks that your catalogue fits its structure, your URLs change, and your extensions are replaced. For an established retailer with thousands of products, those three things are the Magento to Shopify migration. Get them right and the move is also the best chance you’ll get to fix the catalogue, the filtering and the design at the same time.
I’ve engineered more than 350 Shopify stores and migrated over 500,000 products in 20 years in ecommerce. This guide covers both Magento 1 and Magento 2 (including Adobe Commerce), what maps across, how product and customer data moves, how rankings are protected, and when staying on Magento is the better call.
Want to know how your Magento catalogue would map across?
Book a free auditWho this guide is for
This guide is for owners and managers of established online stores running on Magento 1, Magento 2 Open Source or Adobe Commerce. That covers a wide range: fashion and homewares retailers with deep variant ranges, specialist retailers such as hi-fi and home cinema stores selling on specifications, trade suppliers with customer group pricing, and multi-brand retailers with several store views.
What they have in common is a store that earns real money, a catalogue that has grown for years, and a growing feeling that the platform costs more to keep standing than it returns.
It isn’t for every Magento store. If your business depends on deeply bespoke logic, or you’ve just finished a major upgrade that’s working, read when to stay on Magento first.
Magento 1 end of life
Magento 1 reached the end of its official support in June 2020. Adobe’s security bulletin APSB20-41, published on 22 June 2020, described that month’s releases as the final security patches for Magento Commerce 1.14 and Magento Open Source 1. There have been no official patches since.
Some Magento 1 stores are still trading more than six years later, usually kept running by an agency or by community-maintained forks. If yours is one of them, the practical points are these:
- Your store depends on whoever maintains it. Without official patches, the security and compatibility of the platform rests with your developer or hosting provider.
- Extensions have stopped moving. Most Magento 1 extension developers moved on years ago, so payment, shipping and feed integrations get harder to keep working.
- Magento 2 is not an upgrade. Moving from Magento 1 to Magento 2 is a rebuild on a new platform, with the same data, URL and extension work as moving to Shopify. Many Magento 1 retailers compare the two and choose Shopify for that reason.
A Magento 1 to Shopify migration follows the same process as a Magento 2 move. The data structures are older, and sometimes messier, but they map across in the same way.
Magento 2, Adobe Commerce and the upgrade cycle
Magento 2 is actively developed, but every release has a fixed support window. Adobe’s published lifecycle policy, updated in September 2026, shows how quickly those windows close:
| Release | Released | Regular support ends | Supported PHP versions |
|---|---|---|---|
| 2.4.5 | 9 Aug 2022 | Ended 12 Aug 2025 | 8.1 |
| 2.4.6 | 14 Mar 2023 | Ended 11 Aug 2026 | 8.2, 8.1 |
| 2.4.7 | 9 Apr 2024 | 31 May 2027 | 8.3, 8.2 |
| 2.4.8 | 8 Apr 2025 | 31 May 2028 | 8.4, 8.3 |
| 2.4.9 | 12 May 2026 | 31 May 2029 | 8.5 |
Each release also depends on supported versions of PHP, the language Magento is written in. The PHP project stopped supporting PHP 8.1 on 31 December 2025, and support for PHP 8.2 ends on 31 December 2026. So staying current on Magento means moving both the platform and the server software forward on a regular schedule, and updating extensions alongside them.
None of this means a particular store is in trouble. It does mean that Magento has a running cost Shopify doesn’t: every year or two, another upgrade project. On Shopify, the platform is updated continuously for every store, and there’s no server software for you to keep current.
How Magento maps to Shopify
| Magento | Shopify | What to watch |
|---|---|---|
| Simple products | Products | Usually straightforward |
| Configurable products | Products with variants | Up to 3 options and 2,048 variants per product |
| Bundle and grouped products | Bundles via theme or app | Plan how bundles are sold and priced |
| Attribute sets and attributes | Options, metafields and metaobjects | Decide which attributes are filterable |
| Categories | Collections and navigation | Nested trees become collections plus menus |
| Layered navigation | Collection filters | Built on structured product data |
| URL keys, often ending .html | /products/ and /collections/ URLs | Every URL needs a redirect |
| Customer groups and tier prices | B2B companies and catalogues | Available on all plans since April 2026, with limits |
| Store views | Shopify Markets or expansion stores | Countries, currencies and languages |
| CMS pages and blocks | Pages and theme sections | Content rebuilt in the new theme |
| Extensions | Apps or native theme features | Many become unnecessary |
Product data and attributes
This is where a Magento product migration is won or lost.
Magento stores often carry hundreds of attributes built up over years. Some are used, some were abandoned, some are duplicates with slightly different names. Moving them all across as they are recreates the mess on a new platform. The migration is the moment to decide what each attribute is for:
- Attributes buyers choose between become product options, like size, colour or finish.
- Attributes buyers filter on become structured metafields that power collection filters, like brand, material, fit or room.
- Attributes buyers compare become specification fields shown on the product page.
- Attributes nobody uses are left behind.
For a fashion retailer, that might mean merging three inconsistent “colour” fields into one clean option. For a hi-fi retailer, it might mean collapsing several overlapping “power” fields into one specification, so buyers can filter amplifiers by watts per channel across every brand. The principle is the same in any category: the data should match how your customers shop.
Shopify allows up to three options and 2,048 variants per product. Most Magento configurable products fit comfortably. Products with four or more option dimensions need restructuring, usually by moving one dimension into separate products or into a metafield, and some themes and apps still only handle 100 variants, so I check that before the build starts.
URLs, redirects and SEO
Magento lets you shape URLs freely, often with .html suffixes and, if configured, category paths inside product URLs. Shopify uses fixed patterns: products live under /products/, categories under /collections/ and information pages under /pages/, and those folder names can’t be changed. So almost every URL on your Magento store will change.
Each one needs a permanent redirect from the old address to the new. On a large catalogue that’s thousands of lines, and it has to cover more than products:
- Product URLs, including versions that sit under category paths.
- Category and subcategory URLs.
- Layered navigation URLs that have picked up rankings or links.
- CMS pages, blog posts and buying guides.
- Discontinued products, redirected to the closest live alternative.
- Old URLs that already redirect, so chains are collapsed rather than extended.
Shopify allows up to 100,000 redirects on its standard plans and 20 million on Plus. Most stores fit easily; very large catalogues with long histories sometimes don’t, and that’s one of the few genuine reasons to consider Shopify Plus migration.
Google’s own guidance on site moves recommends permanent redirects kept in place for at least a year, and warns that rankings can fluctuate while it recrawls. Meta titles, descriptions and structured data move with the content, and I capture rankings, traffic and revenue as a baseline before launch so any dip is spotted and fixed within days.
Extensions and integrations
A typical Magento store runs a long list of extensions. On Shopify they fall into three groups:
- No longer needed. Caching, full-page cache, security and many performance extensions exist because Magento is self-hosted. Shopify handles that layer.
- Built into a custom theme. Filtering, product tabs, specification tables, size guides and many layout features can be part of the theme itself, with no monthly fee.
- Replaced by apps or integrations. Reviews, email, search, subscriptions and ERP or accounting connections move to Shopify apps or custom integrations.
Integrations with ERP, warehouse or point-of-sale systems are often the biggest variable in a Magento migration. Some have reliable Shopify connectors; others need custom work. I name and scope them in the quote, so nothing is discovered halfway through.
Customers, orders and data migration
Customer accounts, addresses and order history all move, so repeat customers recognise the store and your team can still see past purchases. Marketing consent moves with each record.
Shopify’s own guidance is to import products first, then customers, then historical orders, so that each order links to the right customer and product. Historical orders are imported as records, not live orders, through a migration tool or the API, with staff notifications switched off so nobody gets thousands of order emails.
Passwords are the exception. They can’t be transferred between platforms. Shopify’s current customer accounts sign customers in with a one-time code sent to their email address, so they don’t need to set a new password. I set up the message that explains the change at launch.
Shopify’s free Store Migration app doesn’t list Magento as a supported source, so Magento data moves through specialist tools such as Matrixify, Cart2Cart or LitExtension, or through custom scripts. The tool matters less than the mapping behind it.
Store views, B2B and Shopify Plus
Magento’s multi-store setup and customer groups are the two areas where the move needs the most thought.
Store views
If you use store views for different countries, currencies or languages, Shopify Markets handles that from one store. If you run genuinely separate websites under the same brand, Shopify Plus includes nine expansion stores alongside the main store. Separate brands usually become separate Shopify stores.
Customer groups and tier pricing
Trade customers, installers and wholesale accounts often rely on Magento customer groups and tier prices. Since 2 April 2026, Shopify’s Basic, Grow and Advanced plans include company accounts, payment terms, volume pricing and up to three active price catalogues. Plus adds unlimited catalogues, catalogues for individual companies, deposits and partial payments.
So many Magento retailers who assume they need Plus don’t. My Shopify Plus migration guide sets out exactly where the line falls.
Preparing your Magento store before the move
A few jobs done before the project starts make a Magento migration faster, cheaper and safer:
- Export an attribute list with how often each attribute is used. It makes the rationalisation conversation quick.
- List every extension and what it actually does for the business today, not what it was installed for years ago.
- Pull your top pages from Search Console: the URLs that earn the most clicks and revenue. They’re checked one by one at launch.
- Document integrations: ERP, EPOS, warehouse, accounting, email and anything else that reads or writes orders.
- Prune dead products. Discontinued lines don’t need migrating; they need redirecting to the best live alternative.
- Agree trade pricing with whoever owns those accounts, so the plan decision is made on facts.
- Check your contracts. Note when your hosting, support retainer and extension licences renew, so the launch date avoids paying for both platforms longer than you need to.
Ways to migrate from Magento to Shopify
Migration app
Copies products, customers and orders. Doesn’t rationalise attributes, design the store, rebuild extensions or decide your redirects.
Right for: small, tidy catalogues with an in-house team.
Freelancer
Can work well on a mid-sized store. Check they’ve handled Magento attribute sets, large redirect maps and your integrations before.
Right for: straightforward stores with a clear brief.
Managed migration
One senior person accountable for the data map, design, redirects, integrations and launch, with a fixed fee and scope in writing.
Right for: established retailers whose revenue depends on getting it right.
How a Magento migration runs
My Shopify migration package takes four weeks from signed brief to a live store. Very large catalogues and complex integrations can take longer, and I’ll tell you if yours will after the audit, before you commit.
- Week 1: audit and mapCatalogue, attributes, extensions, integrations and rankings reviewed. Every Magento URL mapped to its Shopify address. Launch date locked.
- Week 2: design and buildA custom theme built around the restructured data while your Magento store keeps trading.
- Week 3: move and connectProducts, customers and order history imported. Payments, shipping, stock and ERP connected and tested. Redirects loaded.
- Week 4: test and launchCheckout tested on real devices, a final data sync so no orders are lost, DNS switched, then 30 days of monitoring and fixes.
What a Magento to Shopify migration costs
My Shopify migration package starts from $24,997 USD, or £18,747 + VAT for UK clients, with flexible plans depending on the deposit paid. It includes the audit, a custom theme, migration of products, images, customers, orders and content, every old address redirected, integrations connected and 30 days of post-launch fixes. I’m UK-based and work remotely with retailers all over the world. Outside the UK, the package starts from $24,997 with no VAT, quoted in US dollars after the free store audit.
Against that, set what you stop paying: Magento hosting, patching, upgrade projects and much of the developer retainer. Your Shopify plan and any apps are paid to Shopify and the app developers directly. My Shopify migration cost guide covers what moves the price, including the cost to migrate a Magento store with a large catalogue.

Common mistakes
Migrating every attribute as it is. Years of duplicated, unused attributes become years of clutter on Shopify.
Forgetting layered navigation URLs. Filter pages that picked up rankings or links need redirecting too.
Leaving redirect chains in place. Old Magento redirects should be collapsed into single redirects to the new URL.
Assuming every extension needs an app. Many aren’t needed at all, and many more belong in the theme.
Copying the Magento design. The move is the cheapest moment you’ll ever have to redesign.
Deciding on Plus before scoping B2B. Trade pricing often fits on a lower plan since April 2026.
If you’re choosing who to work with, my guide to choosing a Shopify migration agency has the questions to ask.
When to stay on Magento
- Your business logic is deeply custom. If the store depends on bespoke pricing, configuration or workflows that would need rebuilding from scratch, Magento may still be the better home.
- You’ve just finished an upgrade. If you’ve recently invested in a major Magento upgrade that’s working, get the return on it first and plan the move for the next upgrade cycle.
- You have a strong in-house Magento team. If the running costs are already absorbed by a team you’re keeping anyway, the case for moving is weaker.
For most established retailers, none of these apply, and the move pays off in lower running costs and a store the team can manage themselves. Lipton’s Audio & Video’s move to Shopify, with more than 2,800 products rebuilt as structured data, is set out in the Lipton’s Shopify migration case study. For the full service, see my Shopify migration service.
Get a straight answer on whether to move.
Book a free auditMagento to Shopify migration: FAQ
Sources
Magento 1 end of support: Adobe security bulletin APSB20-41, 22 June 2020. Adobe Commerce release dates, support windows and PHP compatibility: Adobe Experience League lifecycle policy (updated 18 September 2026), released versions (updated 14 October 2026) and system requirements (updated 13 October 2026). Magento URL settings: Adobe Experience League, catalog URLs (updated 8 October 2026). PHP 8.1 and 8.2 end of support dates: PHP project, as reported by isitpatched.com, 23 October 2026. Shopify options and variant limits: Shopify Help Center and changelog, 15 October 2025. Fixed URL folders and redirect limits: Shopify Help Center, accessed 24 October 2026. B2B on non-Plus plans: Shopify changelog, 2 April 2026. Import order, passwords and customer accounts: Shopify Help Center, accessed 24 October 2026. Store Migration app supported platforms: Shopify blog, 21 July 2026. Site moves: Google Search Central, updated 20 August 2026. KA Consultancy prices and proof points as published on the Shopify migration services page; migration results from the Lipton’s Audio & Video case study.