Magento to Shopify migration: a plan for data, redirects, integrations and cutover
Magento to Shopify migration plan: when to stay, how to map data, redirects, integrations and cutover, with Adobe support dates and Shopify limits.
By Rokibul Hasan8 min read
- Shopify
- E-commerce

A Magento to Shopify migration is four jobs that happen to share a launch date: moving data, keeping URLs alive, reconnecting integrations and switching over without losing orders. The data tends to get the attention, and the other three are where a rushed move hurts.
This guide is for owners and e-commerce leads on Magento Open Source or Adobe Commerce who are weighing a move. It starts with whether you should move at all, because sometimes the answer is no, then sets out a plan for each job. It also corrects two claims that still appear in many migration guides.
Is a Magento to Shopify migration right for you?
Start with your version. Adobe's lifecycle policy, last updated in September 2026, gives these dates for Adobe Commerce:
| Version | End of standard support | End of extended support |
|---|---|---|
| 2.4.6 | 11 August 2026 | 31 August 2027 |
| 2.4.7 | 31 May 2027 | 31 May 2028 |
| 2.4.8 | 31 May 2028 | To be confirmed |
| 2.4.9 | 31 May 2029 | To be confirmed |
Adobe describes the extra year as being for Adobe Commerce customers, and the page does not mention Magento Open Source. If you run Open Source, do not assume those extended dates apply to you. On Adobe's cloud, the policy says that from 1 June 2027 Adobe will stop maintaining environments on unsupported versions.
On 7 September 2026 Adobe released an urgent fix for CVE-2026-75650, which it says has been exploited in the wild, and told merchants to rotate their encryption key and related credentials as well as patching.
Staying is often the right call when:
- You are on a supported version with people who know it. 2.4.9 has standard support until 2029, so no deadline is forcing you out.
- B2B is the business, and you rely on Adobe Commerce's company hierarchies, negotiable quotes or purchase order approvals. Shopify now has native B2B on every plan, but compare feature by feature.
- Your custom pricing, configurators or multi-site logic are the advantage, and rebuilding them costs more than the upkeep you would save.
- You want less upkeep without leaving Adobe. Adobe Commerce as a Cloud Service is Adobe's managed SaaS option, though it does not support Luma storefronts.
- You are on Open Source and the pain is the front end. The Hyvä Theme went free and open source in November 2025, and the community Mage-OS distribution reached 4.0.0 on 30 October 2026.
Moving tends to make sense when you sell a standard retail catalogue, a small team spends much of its budget on upgrades and patches, or your version is out of support and an upgrade is a large project anyway. If you are unsure about Shopify itself, read Shopify vs a custom ecommerce website first.
Job one: map the data
Magento's model is richer than Shopify's, so expect to translate rather than copy.
| Magento | Shopify | Watch for |
|---|---|---|
| Configurable product | Product with variants | Three options per product, 2,048 variants |
| Grouped product | No direct match | Separate products, or a bundle |
| Bundle product | Shopify Bundles app for fixed bundles | Build-your-own bundles need another app or custom work |
| Attributes and attribute sets | Metafields | Decide which ones feed filters |
| Categories | Collections | Nested menus are rebuilt by hand |
| Customer groups and tier prices | Tags, segments or B2B catalogues | Three catalogues below Plus |
| Websites and store views | Markets, or separate stores | Decide before importing anything |
Shopify's own Store Migration app does not list Magento as a source, so your route is CSV files (15 MB per file), third-party apps such as LitExtension and Cart2Cart, or the API. Try any app on a sample first. Shopify's Plus launch checklist sets the order: products, then customers, then historical orders, so that orders can attach to the right records.
Variants. Many guides still quote a limit of 100 variants per product. Shopify's help pages now say 2,048, with up to three options. A Magento product with four configurable attributes still has to be restructured.
Customers. Passwords cannot be migrated, and many guides conclude that every customer must reset theirs. That is out of date for a new store. Shopify deprecated legacy customer accounts on 26 February 2026, and the current accounts sign people in with a one-time code sent by email. There is no password to reset, so tell customers how sign-in works and make sure their email addresses are clean. Set marketing consent per channel from your Magento records.
Orders. Orders cannot be imported by CSV, so use an app or the API. Shopify suggests at least your returns window, and two to five years where you can. Its orderCreate mutation does not touch inventory or send receipts by default, but test on a real plan: trial and development stores are limited to five new orders a minute. Shopify also warns that imported orders can trigger notifications, so turn those off first.
Gift cards. Move these last, close to launch, because a card used on the old store cannot be updated on Shopify afterwards.
Job two: protect your URLs
Every product and category URL will change. Magento addresses often end in .html, while Shopify uses fixed paths such as /products/ and /collections/.
Build the list of old URLs from your sitemap, Search Console and analytics, not only the catalogue. Map each one to its closest match and import the file:
Redirect from,Redirect to
/blue-mug.html,/products/blue-mug
/kitchen/mugs.html,/collections/mugs
Shopify's redirect rules contain several traps for a Magento store:
- Limits. 100,000 redirects, or 20,000,000 on Plus.
- Blocked prefixes. You cannot redirect paths that begin with
/apps,/application,/cart,/carts,/orders,/servicesor/shop. If your Magento categories live under/shop/, that needs a plan before launch. - Query strings. Shopify says these might not work as expected. If your filters or paging use URLs like
?color=49or?p=2, test them. - Live pages win. A redirect only fires from a broken URL, so nothing on Shopify can sit at the old address.
Google's site move guidance adds the rest: use permanent redirects, point straight at the final URL, keep redirects for at least a year, and expect temporary ranking changes. It suggests moving small and medium sites all at once.
Job three: reconnect integrations
List every extension and every system that talks to Magento, then give each one a verdict: native on Shopify, replaced by an app, rebuilt, or dropped.
| System | The question to answer first |
|---|---|
| ERP or accounting | Which system owns stock, prices and orders from now on? |
| Payments | Does your gateway work with Shopify? Shopify's pricing page lists a fee for other providers, from 2% on Basic to 0.2% on Plus |
| Shipping, tax, email, reviews, loyalty | Is each covered natively or by an app, and can you export the history? |
| Custom checkout logic | Does it fit Shopify's checkout, and does it need Plus? |
Rebuilt integrations should use Shopify's GraphQL Admin API, since REST has been legacy since October 2024. Webhooks can arrive twice or out of order, and Shopify says delivery is not always guaranteed, so any link to an ERP needs a reconciliation job as well.
Job four: cut over
Rehearse this sequence on the new store first:
- Freeze. Stop catalogue and content changes on Magento, and lower your DNS TTL if your provider allows it.
- Final import. Bring across orders and customers created since the first pass, then gift cards.
- Test. Place orders through Shopify's Test payment gateway, then one real order that you refund.
- Switch DNS. Point your domain to Shopify, changing only the web records so your email keeps working. Shopify says this can take up to 48 hours.
- Decide what the old site does. Some visitors will reach Magento during that window, so show a holding page or import any orders it takes afterwards.
- Open the store. Remove the password page and turn notifications back on.
- Keep Magento. Hold a full backup and a private copy for reference.
The first two weeks after launch
Crawl your old URL list and confirm each one lands on a live page in a single hop. Submit the new sitemap in Search Console and watch for spikes in 404s. Update Merchant Center feeds, ad destinations and links in email flows, which all still point at old addresses. Rankings can take weeks to settle, so judge the move on a month of data.
What a Magento to Shopify migration costs, and who should do it
In the US, Shopify's plans run from $39 a month on Basic to a starting price of $2,300 on Plus, with apps on top. Compare that with what you pay today for licences, hosting and developer time. The one-off work depends on your catalogue, integrations and redirects, so be wary of a fixed figure offered before anyone has seen them.
For a large catalogue with several integrations, an agency or Shopify partner with Magento migrations in its portfolio is the safer choice. Ask to speak to a merchant they moved.
I build Shopify apps and integrations on official APIs, so the part of this plan I would quote is the custom work. A Magento feature rebuilt as a custom app is what my Shopify app plans cover, starting from $2,000 for one focused feature and from $4,500 where order and product data must stay in sync. These are starting prices, with a fixed quote after a brief. My guide to building a Shopify app explains what is involved.
FAQ
Will I lose SEO rankings moving from Magento to Shopify?
Some movement is normal. Google says to expect temporary fluctuation during a site move, and rankings can take weeks to settle. Lasting losses are far more likely when redirects are missing or poor, so map every old URL to its closest match with permanent redirects, keep them for at least a year and crawl the old list after launch.
Can customer passwords be migrated from Magento to Shopify?
No. Shopify does not let you import customer passwords. That matters less than it used to, because legacy customer accounts were deprecated in February 2026 and current accounts sign people in with a one-time code sent by email. Customers have nothing to reset, but tell them how sign-in works before launch.
Should I upgrade Magento or migrate to Shopify?
It depends on what your store does. Upgrading makes sense if your team knows Magento and custom features or B2B workflows are central to how you sell, and 2.4.9 has standard support until May 2029. Migrating makes sense for a standard retail catalogue where upkeep takes budget away from selling. Price both as real projects before you decide.
If you are planning a move, send me a short brief: your Magento version, catalogue size, the systems connected to it and when you need to be live. You can start from the Shopify app plan, read about my Shopify app development work, or look at the wider automation options for a store once the move is done.


