To migrate from Magento to Shopify, you rebuild the storefront on Shopify, move products, customers and order history across, replace every custom module and extension with an app, a native feature or a little code, and give every old Magento URL a 301 redirect. The data moves easily. What does not map one to one is how Magento models products, stores, customer groups and URLs, and that is where the project is decided.
We are noprob agency, and we run these moves with the Shopify Launch Sprint. This article covers only what is specific to Magento 2 and Adobe Commerce. For the parts that are the same on every platform, read our guide to migrating to Shopify, the migration SEO checklist, what a Shopify migration costs and how to choose a Shopify migration agency.
One thing first: we have no Magento case study. Our two real migrations are Integratori DTC Nazzi, from WooCommerce, and Cumini, from a proprietary platform tied to the ERP. This article rests on those, on our process, and on Adobe’s and Shopify’s official documentation.
Why do stores migrate from Magento to Shopify?
Stores migrate from Magento to Shopify mostly because of what it takes to keep Magento running, not because of what it can do. Magento, in its Open Source or Adobe Commerce form, is flexible and powerful. The cost sits around it:
- Patches and upgrades. Adobe publishes security patches regularly, recommends the latest one for your release, and gives every release line a support end date (versions page). Someone has to apply, test and deploy each one.
- The stack underneath. PHP, the database, the search engine and caching are yours or your host’s to keep current. If your Magento runs on PHP, as Magento does, note that CERT-EU advisory 2026-018 (21 October 2026) describes two PHP flaws rated CVSS 9.2 that allow remote code execution without authentication, and says PHP 8.1 and earlier have no official fix. Whether it affects your store depends on the PHP version it runs on: check it, or ask your host.
- Developer dependence. Extensions conflict, modules are custom, and few people know your codebase. Every change becomes a ticket for the same one or two developers.
Our view: the license is rarely the real number, the people are. A store that needs a developer on call just to stay safe is paying for maintenance instead of growth.
When is staying on Magento the better call?
Staying on Magento is the better call when the logic in your custom modules is your competitive edge and rebuilding it would cost more than the maintenance you would save: deep B2B pricing and approval rules tied to an ERP, or websites with genuinely different catalogs. Shopify can reach much of this with B2B, Markets, Shopify Functions and apps, but that is a rebuild of the logic, not a transfer. If the honest answer after the inventory below is “stay”, we will say so.
How do Magento product types map to Shopify?
Magento has several product types and Shopify has one product with options and variants, so the mapping is done type by type. Adobe lists the types in its product types documentation.
- Simple products become Shopify products. This is the easy part.
- Configurable products become one Shopify product with options (size, color) and one variant per combination. In Magento each combination is a separate simple product with its own SKU, so the import must fold the children into the parent. Shopify limits how many options a product can have (how variants work), so a configurable with more attributes needs a decision before import: split it or turn some attributes into separate products.
- Grouped products, where several standalone items sit on one page, have no direct equivalent. You choose between a collection, a bundle, or the Combined Listings app, which presents separate products as one listing and is available only on Plus and enterprise commerce plans.
- Bundle products (build-your-own sets) move to a bundles app: Shopify’s help says bundles need a bundles app installed.
Attribute sets are the other half: Magento attribute sets and custom attributes become metafields and metaobjects. Our rule: keep the attributes a customer sees or filters by, and drop the rest. Navigation is decided here too: Shopify’s storefront filters are built from product data, so Magento’s layered navigation is rebuilt on the attributes you keep.
What happens to store views, websites and customer groups?
Magento’s website, store and store view hierarchy does not exist in Shopify as such, so you replace it with Markets, separate stores where needed, and B2B for customer groups. In Adobe Commerce, websites contain stores and stores contain store views, and settings, catalogs, prices and base currencies can differ by scope.
- Store views by language or currency map to Shopify Markets, where you set language, currency, pricing and domain per market on one store.
- Websites with separate catalogs, prices or legal entities are a decision: one store with markets, or separate Shopify stores. Shopify Plus supports expansion stores for this. Decide website by website.
- Customer groups with tier prices map to Shopify B2B, where customers are set up as companies with their own pricing, products, payment and shipping methods. Shopify says B2B is available on Basic, Grow, Advanced and Plus, so check which B2B features each plan includes against your price lists.
What happens to Magento extensions and custom modules?
Every Magento extension and custom module ends in one of four ways on Shopify: a native feature, an app, code written in the store, or retirement. None of them transfers.
- Native feature: discounts, gift cards, basic SEO fields, blog and redirects are built in.
- App: reviews, loyalty, subscriptions, advanced filters. Export the app data first, because reviews and loyalty points are data, not settings.
- Store code: custom discount, shipping or payment logic can run as Shopify Functions; anything storefront-specific is code in the store.
- Retire: modules installed for a campaign years ago and never removed.
Start the inventory from your code, not from memory: list what sits in the app/code folder and in composer.json, and write each module’s job in one sentence. In the Sprint we write the store’s code from scratch for your store only: no dead code, no apps slowing it down, which is why we retire as much as possible before the build.
How do Magento URLs become a redirect map?
Magento URLs become a redirect map by exporting Magento’s own URL rewrite table, flattening the paths to Shopify’s fixed prefixes, and checking every row against the pages Google knows. Magento keeps the URLs it has generated in a url_rewrite table (request path, target path, redirect type and store), the same data you see in the admin under Marketing, SEO & Search, URL Rewrites (Adobe’s URL rewrites documentation). Export it per store, then add a crawl, Search Console pages and backlinks, as in our SEO checklist.
These are the Magento patterns to expect, and where they usually land:
- Product URLs with a suffix. The suffix is configurable (html or htm, or none). /blue-shirt.html goes to /products/blue-shirt.
- Product URLs with a category path. Adobe warns that including category paths can make several URLs point at one page. /men/shirts/blue-shirt.html and /blue-shirt.html both go to the same /products/blue-shirt.
- Category URLs. /men/shirts.html goes to a collection. Shopify collections are flat, so nested categories are decided one by one: keep as a collection, merge, or retire.
- Old redirects. Rows in the table with a 301 type are chains waiting to happen. Point every one at the final Shopify URL.
- System paths. /catalog/product/view/id/34 and /catalog/category/view/id/12 get a row if Search Console shows impressions.
- Store codes in the path (/default/, a language code): one set of rows per store view.
- Filter and sort URLs (color, price, sort order, page number). Do not write a row per combination. Send the base path to its collection and let the rest go.
Google’s site move guide says to map each old URL to its matching new one, not everything to the homepage, and to keep the redirects generally at least a year. Shopify imports them from a CSV through URL redirects.
Shopify or Shopify Plus for a Magento store?
For a Magento store, the choice between Shopify and Shopify Plus comes down to four requirements, not to revenue: B2B depth, several storefronts, checkout changes and combined listings.
- B2B: available on Basic, Grow, Advanced and Plus. Compare the features with your price lists, not only the availability.
- Several storefronts: Markets covers language, currency, pricing and domain on one store. Separate catalogs or legal entities point to more stores, which means Plus expansion stores.
- Checkout: if your Magento checkout has custom rules, test how much Shopify Functions reproduce before you choose. Shopify says advanced checkout customization is available only on Plus.
- Grouped products as one listing: the Combined Listings app is available only on Plus and enterprise commerce plans.
Our opinion: write the requirement list before you ask for any quote, and check plan prices on Shopify’s site, because they change. The Sprint price is public, from €5,800 excl. VAT in 4 installments and set by your revenue tier: see the Sprint page.
How long does a Magento to Shopify migration take?
A Magento to Shopify migration runs in six steps, and the Sprint puts them on a fixed calendar: store ready on day 14, go-live between day 15 and 30, then 90 days of support. We have no Magento timeline of our own to quote. Store views, custom modules, B2B rules, ERP connections and catalog data quality are what stretch it.
- Inventory: modules, product types, attributes, store views, customer groups and the url_rewrite export.
- Decisions in writing: plan, markets, what is rebuilt, what is retired.
- Build the new store while Magento keeps selling, as at Nazzi, built in May and June while the old store kept selling.
- Import products first, then customers, then historical orders, as Shopify’s migration guide recommends. Passwords cannot be moved in a usable form (Shopify’s Magento guide), so plan activation emails.
- Load the redirect CSV and place test orders.
- Cutover: import what changed since the first import, switch the domain, check tracking, crawl the old URL list again and watch Search Console.
What does our experience prove, and what does it not?
Our experience proves a process, not Magento expertise: two real migrations, and neither was from Magento. Nazzi, a supplement brand, went from WooCommerce to Shopify on 19 July 2026 and, from go-live to 12 October, sold 105% more online than in the same days of 2025, with orders up 77%. One store, with its own seasonality. For its URLs we checked 215 archived WooCommerce addresses and delivered the 301 redirect CSV.
Cumini, a luxury multibrand boutique, went live on Shopify on 19 May 2025 after being on a proprietary platform tied to the ERP, and from June 2025 to May 2026 online sales were up 67.7% on the 12 months before. That platform resembles a heavily customized Magento store in one way: it was tied to an external vendor and to the ERP, with little room to change anything. We built a solution that connects Shopify to that ERP. It is a similarity, not a Magento case.
What it means for you: we run the inventory first and tell you, before you sign, which modules map to native features and which are real rebuild work.
Frequently asked questions
Will I lose my Google rankings migrating from Magento to Shopify?
Rankings usually move for a while after any migration, and nobody can promise zero movement. A complete 301 redirect map, built from Magento’s URL rewrite table plus a crawl and Search Console, decides how fast they settle.
Do I need Shopify Plus to leave Magento?
Not always. Plus is needed for specific things: the Combined Listings app, expansion stores and the deepest checkout changes. Choose the plan from your B2B, multi-store and checkout requirements, not from your revenue.
What happens to my Magento extensions on Shopify?
They do not transfer. Each extension and custom module ends in one of four ways: a native Shopify feature, an app, code written in the store, or retirement. Start from the job each one does, not from its name.
Can I move customers, passwords and order history from Magento?
Customers and historical orders can be imported with CSV files, migration apps or the Shopify APIs, products first, then customers, then orders. Passwords cannot be moved in a usable form, so customers get an activation email or a password reset after launch.
How do I replace Magento store views and websites on Shopify?
Language and currency store views usually become Shopify Markets on one store. Websites with separate catalogs, prices or legal entities may need separate stores, which is where Plus and its expansion stores come in.
How long does a Magento to Shopify migration take?
It depends on store views, custom modules, B2B rules, ERP connections and catalog data quality. With the Shopify Launch Sprint the store is ready on day 14 and go-live falls between day 15 and 30, followed by 90 days of support.
A Final Note
Moving from Magento is a translation job with two hard parts: the logic hidden in modules and the URLs Google already knows. Both are found by an inventory, not by a quote.
The Shopify Launch Sprint moves your store to Shopify in 14 days with our Custom AI System: a fixed calendar, a public price and 4 written guarantees.
Antonio Manitta
Founder & eCommerce Manager at NoProb Agency
For over 7 years I have helped fashion, supplements, and DTC brands scale their eCommerce. I work in long-term partnership with three brands at a time, building stable systems that compound.
About NoProb →
