All guidesShopify development

Magento to Shopify migration: what it costs, what moves, and when to start

What a Magento or Adobe Commerce store moves, rebuilds and pays when it switches to Shopify, with the support dates that set the deadline and a cutover plan that keeps you selling.

The short version

A Magento to Shopify migration moves products and customers through Magento's admin export and an import app such as Matrixify, pulls order history from Magento's database, rebuilds the theme and extensions as Shopify theme code and apps, and redirects every old .html URL to Shopify's /products/ and /collections/ paths before the domain moves. Adobe sets the timing: Adobe Commerce 2.4.6 left standard support on 11 August 2026 and 2.4.7 leaves on 31 May 2027. A US agency's 2026 planning ranges put a simple migration at $5,000 to $20,000 and a mid-market one at $20,000 to $60,000, while the import app costs about ₹1,880 to ₹18,795 a month for the weeks you need it. Indian stores should also price Shopify's third-party transaction fee of 2% to 0.2%.

Adobe's support dates decide when to move

A store on Adobe Commerce 2.4.6 or older is already past standard support, and 2.4.7 follows on 31 May 2027. Upgrading and moving to Shopify both take months, so the real decision is which of the two projects to fund, and it has to be made now.

Adobe's lifecycle policy sets a fixed end date for standard support on each release line:

Release lineReleasedEnd of standard support
2.4.59 August 202212 August 2025
2.4.614 March 202311 August 2026
2.4.79 April 202431 May 2027
2.4.88 April 202531 May 2028
2.4.912 May 202631 May 2029

Three details on the same page change the urgency:

  • Extended support is narrow. Adobe gives Adobe Commerce customers on 2.4.6 and 2.4.7 one extra year at no cost, to 31 August 2027 and 31 May 2028. The policy covers Adobe Commerce only, so a Magento Open Source store should plan around the standard dates.
  • Adobe Commerce on Cloud has a hard stop. From 1 June 2027, Adobe says it will no longer maintain Cloud environments running unsupported versions. It may suspend traffic, which takes the storefront offline, and then terminate the environment, permanently deleting its data.
  • PHP runs its own clock. PHP 8.1 reached end of life on 31 December 2025, and Adobe flags PCI compliance as at risk for stores still running it, and for PHP 8.2 from the end of 2026. PCI compliance is the merchant's responsibility to assess.

Upgrading to 2.4.8 or 2.4.9 keeps your custom code and buys time until May 2028 or May 2029, but every extension has to be tested on the new version, and then the next deadline arrives. Moving to Shopify ends the version and patch cycle, because Shopify runs the platform. Upgrade if the store depends on heavy custom logic that a Magento team already maintains well. Move if most of your Magento spend goes on keeping the platform patched rather than on selling. The rest of this guide covers the move; for the platform-neutral steps, see our Shopify replatforming guide.

What moves from Magento, and what you rebuild

Products, customers, order history, gift cards and CMS pages can all move to Shopify. The theme, extensions, checkout customisations and customer passwords cannot, so they are rebuilt or replaced.

Shopify publishes migration guides for WooCommerce, Wix, Squarespace and several other platforms, but none for Magento. The table below is drawn from Adobe's documentation and the import apps' own tutorials.

DataWhere it comes from in MagentoHow it reaches Shopify
ProductsAdmin export, entity type ProductsAn import app such as Matrixify; custom attributes become metafields
Tier and group pricesAdmin export, entity type Advanced PricingRebuilt as B2B volume pricing or discounts
CustomersAdmin export, Customers Main File and Customer Addresses as two filesAn import app, or Shopify's customer CSV
Order historyNot in the admin export; read from the databaseAn import app that reads the exported tables
Gift cardsAdobe Commerce onlyShopify's gift card import
Cart price rules and couponsRules and codes set up in the adminRecreated as Shopify discounts, or imported with Matrixify
CMS pagesContent in the adminCopied, or imported as pages
Customer passwordsStored as hashesNot needed: Shopify's customer accounts sign in with a one-time code
Theme and extensionsYour Magento codebaseRebuilt as a Shopify theme and apps

Matrixify is a common choice because it publishes step-by-step Magento tutorials, and its Magento product tutorial says the process works the same way for Magento 1.x and 2.x. It recognises a Magento export by its file name, so a product file's name must contain "magento" and "products". Run its dry run first: it converts the file and shows the result without changing the store. Connector apps that log in to both stores, such as Cart2Cart's Magento importer, are the alternative. Whichever you pick, check it covers every row of the table before paying.

Configurable, bundle and grouped products need decisions

Magento has seven product types; Shopify has one product with up to three options and 2,048 variants. Simple and configurable products map cleanly, while bundle and grouped products need a decision before anything is imported.

  • Configurable products. In Magento, each option of a configurable product is a separate simple product with its own SKU and stock. On Shopify they become variants of one product. Shopify's variant rules allow up to three options per product, so a configurable product built on four or more attributes has to be restructured: merge two attributes into one option, or split the product.
  • Bundle products. Magento's build-your-own bundles have no native Shopify equivalent. Shopify needs a bundles app installed before you can create bundles, so import the component products first and rebuild each bundle in the app.
  • Grouped products. These present standalone products together. The closest Shopify match is a collection, or a product page section that lists the related items. Decide per group whether it earns a page of its own.
  • Virtual and downloadable products. Services, warranties and files become products that do not require shipping, with an app delivering the file where one is needed.
  • Custom attributes. Matrixify turns every exported custom field into a product metafield. Sort them first: attributes the theme displays or filters on stay, and years of unused attributes can be left behind.
  • Handles. Matrixify uses the Magento URL key as the Shopify handle by default. Keep it: /blue-kurta.html becomes /products/blue-kurta, and the redirect map stays a simple pattern.
  • Images. Give Matrixify the old store's domain and it builds full image links from Magento's media paths for the import to fetch. Keep the Magento server online until the import has finished.

Customers and order history come out of different places

Customers leave Magento through the admin export, and orders do not, because Magento's export tool has no order entity. Plan each separately and import in the order Shopify gives: products, then customers, then orders.

Customers. Adobe's export tool, at System > Data Transfer > Export, lists Customers Main File and Customer Addresses as separate entity types, so export both. Matrixify's Magento customer import carries fields with no Shopify equivalent, such as gender and the Magento customer group, across as tags, and stores date of birth and VAT ID as metafields. Phone numbers in invalid formats fail the import, so clean them first or move them into the customer note.

Passwords. Magento stores customer passwords as hashes, and they stay behind. On Shopify's current customer accounts this costs nothing: customers enter their email address and receive a one-time 6-digit code, with no password at all. Launch on these accounts rather than the legacy ones; our customer accounts guide covers the choice.

Orders. Matrixify's Magento order tutorial reads them from the database. Connect a tool such as DBeaver to Magento's MySQL database and export the Magento 2 tables sales_order, sales_order_item, sales_order_address, sales_order_payment and sales_shipment_track to CSV, plus sales_order_status_history if you want order comments. Zip them into a file whose name contains "magento" and "order". The import brings line items, customer details, shipping cost, refunds, fulfilments and transactions, and links line items to products by SKU, which is why products go first. Turn off the staff new-order notification before importing, or the team receives one email per historical order.

Decide how much history earns the import. Lifetime value, repeat-purchase reports and returns on recent orders need it, while orders from a decade ago rarely do. Archive the Magento database either way.

Redirects from .html URLs keep your rankings

Every Magento URL with traffic or links needs a 301 redirect to its Shopify page, in place before the domain moves. Magento catalogue URLs usually end in .html and Shopify's never do, so nearly every old URL changes.

Your old URL format is set at Stores > Settings > Configuration > Catalog > Catalog > Search Engine Optimization: the product and category URL suffix, and whether product URLs include the category path. Adobe's catalog URL documentation says the category path is left out by default, and shows both forms:

PageMagentoShopify
Product/helena-hooded-fleece.html/products/helena-hooded-fleece
Product with category path/women/tops-women/hoodies-and-sweatshirts-women/helena-hooded-fleece.html/products/helena-hooded-fleece
Category/women/tops-women.html/collections/tops-women
CMS page/about-us/pages/about-us

Then build the map:

  • Start from the generated redirects. Matrixify writes redirects from Magento's URL structure to Shopify's during the product import: old product URLs, old category URLs, and every category and product combination. If you change a handle after that, change its redirect too.
  • Count before you import. Shopify's redirect limit is 100,000 per store, or 20,000,000 on Plus. Category paths multiply: 20,000 products in an average of three categories is 60,000 product redirects before categories, pages and store views. Large catalogues should drop combinations that never received traffic.
  • Add what the catalogue export misses. CMS pages, store-view URLs that carry a store code, and every landing page with traffic in Search Console over the last 12 months.
  • Leave filtered URLs out. Layered navigation creates URLs with query strings, and Shopify warns that those might not work as expected with redirects. Redirect the category, not each filter combination.
  • Point straight at the final page. Magento can create automatic redirects when a URL key changes, so some old URLs already hop once. Google's site move guidance asks for redirects to the final destination, and chains of ideally no more than 3.

Redirects live at Content > Menus > URL redirects in Shopify and can be imported as a CSV. Google says a small to medium site can take a few weeks for most pages to move, and recommends keeping redirects for at least a year. On Shopify they cost nothing, so keep them for good.

Extensions, checkout and B2B pricing are where scope hides

A Magento store's extensions and custom modules set the size of the migration more than its catalogue does. List every one before agreeing a timeline, and mark each as built into Shopify, replaced by an app, rebuilt in the theme, or dropped.

  • Dropped. Caching, full-page cache warmers and security patching exist because Magento is self-hosted. Shopify runs the hosting, so they go.
  • Checkout. On Magento a developer can change checkout freely. On Shopify, apps that customise the information, shipping and payment steps are Plus only, according to Shopify's checkout customisation page. Extensions on the thank you and order status pages, public apps built on Shopify Functions, and the free Checkout Blocks app (with fewer features on Basic) work from Basic. List what your Magento checkout does today and which step each change touches.
  • Cart price rules. Discount logic beyond Shopify's built-in discounts now runs on Functions. Our Functions guide covers what can be rebuilt and how.
  • Customer groups and tier prices. Since 2 April 2026, Basic, Grow and Advanced include native B2B: company profiles, payment terms and volume pricing, with up to 3 active B2B catalogs, per Shopify's changelog. Unlimited catalogs, catalogs assigned directly to a company, deposits and partial payments remain Plus only. Our wholesale guide covers the setup.
  • Websites and store views. Countries, currencies and languages that Magento ran as separate store views usually become markets on one Shopify store; see selling internationally on Shopify.
  • Integrations. ERP, warehouse, marketplace and accounting connections are rebuilt against Shopify's APIs or replaced by the vendor's Shopify app. These are often the longest line in the plan.
  • Product reviews. Reviews are not part of the catalogue export. Export them from Magento's database or your reviews extension and import them into a Shopify reviews app that accepts a CSV, so star ratings survive the move.

Plus starts from ₹1,75,000 a month on Shopify's India pricing, so confirm that a Plus-only item is truly needed before it decides the plan. Our app audit guide helps keep the replacement app list short.

Payments, GST and COD for Indian Magento stores

Shopify Payments is not available in India, so an Indian store keeps a gateway such as Razorpay and pays Shopify a third-party transaction fee on top of the gateway's own. Magento Open Source charges no fee of this kind, so put it in the cost comparison before you commit.

Shopify's India pricing sets that fee at 2% on Basic, 1% on Grow, 0.6% on Advanced and 0.2% on Plus. Plans billed monthly cost ₹1,994, ₹7,447 and ₹30,164 (₹1,499, ₹5,599 and ₹22,680 a month billed yearly). Our plan guide works out where each plan breaks even on prepaid revenue.

  • Gateway. The Razorpay module on Magento does not carry over. Razorpay's Shopify documentation says the website must be reviewed before integration and only the account owner can connect it, at Settings > Payments > Add payment method, searching by provider for "01 Cards, UPI, NB, Wallets by Razorpay". Start that review weeks before cutover. Our gateway comparison covers the alternatives.
  • GST. Shopify's GST FAQ says it cannot set multiple tax line items, so CGST and SGST become one combined rate for in-state sales. Shopify also does not create a GST-compliant bill, so a GST invoicing app takes over from whatever Magento used. HSN codes go in the HS tariff code field in each product's Shipping section, which needs at least 6 digits.
  • COD. Turn on cash on delivery in Shopify's payment settings and test it with a real order. If RTO already hurts, the move is a good time to add order confirmation, as our RTO guide sets out.
  • Shipping. Reconnect your courier aggregator through its Shopify app, and test a prepaid and a COD order through to label creation.

What a Magento to Shopify migration costs

Most of the cost is build work: the theme, extension rebuilds, integrations and testing. The import tools are a small line. A US agency's 2026 planning ranges put a simple store at $5,000 to $20,000 and a mid-market store at $20,000 to $60,000.

Those figures come from an August 2026 cost breakdown that puts enterprise and B2B projects with ERP or PIM work at $60,000 to $150,000 or more, standard projects at 12 to 20 weeks and advanced ones at 20 to 30. They are US market planning ranges, not quotes. For rupee build costs, see our India development cost guide. Line by line, a migration pays for:

LineCostNotes
Import appMatrixify: ₹1,879.50 (Basic), ₹4,698.76 (Big) or ₹18,795.05 (Enterprise) per 30 daysBasic covers 5,000 products, 2,000 customers and 1,000 orders per file; Big covers 50,000, 20,000 and 10,000. Needed only for the migration weeks.
Shopify plan₹1,994 to ₹30,164 a month billed monthly; Plus from ₹1,75,000Choose with the transaction fee in view
Transaction fee2% to 0.2% of payments through a third-party gatewayApplies to Indian stores, since Shopify Payments is unavailable
AppsThe monthly total of your extension replacementsThe App Store shows estimated prices in your billing currency
ThemeFree, paid or customA Magento theme cannot be copied across
Build and testingUsually the largest lineGrows with integrations, B2B logic and custom checkout

Set that against what Magento costs you each year: hosting, the Adobe Commerce licence if you pay one, extension renewals, and the developer hours spent on patches and upgrades. A move pays back through those lines, and the upgrade you would otherwise fund before 2027 or 2028 belongs in the comparison too.

A cutover plan that keeps the store selling

Build the Shopify store in full while Magento keeps trading, then switch the domain in one planned window. Google recommends moving all URLs at the same time rather than one section at a time, and a single cutover is also simpler to test.

  1. List and decide. Every extension, integration and checkout change, each with its Shopify answer, and the redirect map built from real traffic.
  2. Build and import. Theme, apps, products and customers go into the new store behind its password page, each import tested with a dry run first.
  3. Freeze catalogue edits. Agree a date after which product changes happen in Shopify only.
  4. Test real orders. Prepaid through the gateway, COD, a discount code, a GST invoice, a shipping label, a wholesale order if you sell B2B, and a customer sign-in.
  5. Load the redirects. All of them, before the domain moves.
  6. Run the final order import. Export the orders placed on Magento since the first import, filtered by date, and import them just before cutover.
  7. Move the domain. Connect it in Shopify, remove the password page and publish the products.
  8. Watch the first 48 hours. Order flow, payment success rate, 404s in Search Console, and the old URLs of your top pages.
  9. Archive Magento, do not delete it. Keep a database and file backup for refunds, disputes and anything the import missed. On Adobe Commerce Cloud, take it before the contract ends, because Adobe's policy describes permanent deletion when it terminates an environment.

We have run this pattern on live stores moving from other platforms. Jimmy Luxury moved from WordPress to Shopify with around a hundred orders a day coming in and no pause in trading. Miduty was rebuilt on a separate Shopify store and cut over at 400 to 500 orders a day with zero downtime. Our migration service page explains how we scope a move. If you would like a second opinion on your extension list or redirect map before you start, get in touch.

Questions

How much does it cost to migrate from Magento to Shopify?

A US agency's 2026 planning ranges put a simple store at $5,000 to $20,000, a mid-market store with a custom theme and several integrations at $20,000 to $60,000, and enterprise or B2B projects at $60,000 to $150,000 or more. The import app is a small part of that: Matrixify costs about ₹1,880, ₹4,700 or ₹18,795 per 30 days depending on volume. The largest lines are rebuilding extensions, integrations and the theme. Indian stores should add Shopify's third-party transaction fee of 2%, 1%, 0.6% or 0.2% by plan.

How long does a Magento to Shopify migration take?

A US agency's August 2026 estimates put standard Magento to Shopify projects at 12 to 20 weeks and advanced ones at 20 to 30 weeks. A D2C store with a standard catalogue, few integrations and no B2B pricing sits at the short end. ERP and warehouse integrations, customer-specific pricing and custom checkout logic push it longer. Start before your release line leaves support: 31 May 2027 for Adobe Commerce 2.4.7.

Will I lose SEO rankings moving from Magento to Shopify?

Not if every Magento URL with traffic or links has a 301 redirect to its Shopify page before the domain moves. Magento URLs usually end in .html and Shopify uses /products/ and /collections/ paths, so nearly every URL changes. Matrixify generates redirects for products, categories and category and product combinations. Expect some movement anyway: Google says a small to medium site can take a few weeks for most pages to move.

Can I migrate customer passwords from Magento to Shopify?

No. Magento stores passwords as hashes and they do not move to Shopify. On Shopify's current customer accounts this does not matter, because customers sign in with their email address and a one-time 6-digit code instead of a password. Imported customers can sign in this way from the first day. Only stores that choose legacy customer accounts would need to invite customers to set new passwords.

Is Shopify Plus better than Magento or Adobe Commerce?

It depends on how much custom logic you run. Adobe Commerce gives full control of the code, but you fund upgrades and patching, and 2.4.7 leaves standard support on 31 May 2027. Shopify Plus starts from ₹1,75,000 a month in India and removes that cycle. Many D2C stores leaving Magento do not need Plus at all: since April 2026 Basic, Grow and Advanced include native B2B. Plus earns its fee when you need checkout step customisation, unlimited B2B catalogs or the lowest transaction fee.

When does support end for Magento 2.4.7?

Adobe's lifecycle policy lists the end of standard support for Adobe Commerce 2.4.7 as 31 May 2027, with one extra year of extended support for Adobe Commerce customers to 31 May 2028. 2.4.6 left standard support on 11 August 2026. From 1 June 2027, Adobe says it will no longer maintain Cloud environments running unsupported versions and may suspend their traffic.

Can I import Magento orders into Shopify?

Yes, with an import app. Magento's admin export has no order entity, so Matrixify's method exports the order tables from Magento's database, including sales_order, sales_order_item and sales_order_address, and converts them. Line items link to products by SKU, so import products first, then customers, then orders. Turn off the staff new-order notification first, or the team receives one email for every historical order.

Get started

Talk to us about your store.

Average reply 11 min

Book a call

30 minutes with Suvam. Leave knowing what to fix, build or leave alone.

Book a call
Mon to Sat, 9 to 23 IST

Email us

A brief, a bug or a question. All welcome.

suvam@knox.team