Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
A Shopify to Magento migration makes sense when your business has outgrown what Shopify's model allows without heavy workarounds: complex B2B pricing, deep ERP integration, unusual catalog structures, or a need to own and change the code. It rarely makes sense just to save on fees or because a single app is missing. If you do move, the work is a mapping exercise: Shopify products, variants, collections, customers, orders and URLs each need a clear home in Adobe Commerce or Magento Open Source.
This guide gives you a signals table to make the call and a data mapping list to plan the move.
Should you move? Signals table
Shopify and Adobe Commerce are both capable platforms built on different trade-offs. Shopify is a hosted SaaS where Shopify runs the platform and you extend it with apps. Adobe Commerce and Magento Open Source give you the full application to customize, with the hosting and upgrade responsibility that comes with it. For the full comparison, read Magento vs Shopify.
| Area | Signal that moving pays off | Signal to stay on Shopify |
|---|---|---|
| B2B | Company accounts, buyer roles, negotiated quotes, shared catalogs and requisition lists are core to revenue | B2B is a small share handled by a wholesale channel |
| Catalog | Complex configurable, bundle or kit products; many attributes; layered navigation is central | Simple products with a few options each |
| Integrations | ERP, PIM or WMS must run deep, custom logic inside the commerce layer | Integrations work well through existing connectors |
| Customization | Checkout, pricing or fulfilment rules keep hitting platform limits | Your needs are met by apps and themes |
| Multi-store | Several brands, regions or B2B and B2C sites from one admin with different catalogs and prices | One brand, a few markets |
| Ownership | You need control of code, data location and hosting | You prefer not to manage hosting, upgrades and security patches |
| Team | You have, or will hire, PHP and Magento developers or an agency | Your team is non-technical and moves fast with apps |
| Costs | App subscriptions and workarounds keep growing with complexity | Total cost is predictable and acceptable |
If most of your ticks are in the right-hand column, staying is probably the better business decision. The migration itself costs money and attention, and Magento brings ongoing duties: upgrades, security patches and hosting.
Choose the right destination
"Magento" can mean three different products, and the choice affects the data mapping:
- Magento Open Source: free, self-hosted, without the Adobe Commerce-only features such as B2B modules, gift cards and content staging.
- Adobe Commerce (PaaS): licensed, on-premises or on Adobe Commerce on Cloud infrastructure, with B2B and merchandising features.
- Adobe Commerce as a Cloud Service: Adobe's SaaS edition with a headless storefront and out-of-process customization only.
Whichever you pick, target the current release. Version 2.4.9 has been generally available since May 12, 2026, with standard support until May 31, 2029.
Data mapping list
Shopify's admin exports products, customers and orders as CSV, and its Admin API exposes more detail. Adobe Commerce imports products, customers, addresses and advanced pricing through System > Data Transfer > Import, or through its REST API. In between, you transform the data. Here is how the main objects map.
| Shopify | Adobe Commerce / Magento | Notes |
|---|---|---|
| Product with variants | Configurable product with simple child products | Each variant becomes a simple product with its own SKU; options become configurable attributes |
| Product with no variants | Simple product | Map weight, price, compare-at price (as special price or MSRP, by business rule) |
| Product options | Attributes in an attribute set | Create attributes and option values before import |
| Metafields | Custom product attributes | Decide the type (text, select, multiselect) per metafield |
| Tags | Attributes or categories | Tags often encode filters; turn them into filterable attributes |
| Manual collections | Categories | Assign products and positions |
| Automated collections | Categories plus rules or merchandising tools | Rule-based categories need Adobe Commerce Visual Merchandiser or an extension |
| Product images and alt text | Product media gallery | Download images; keep alt text and order |
| Customers and addresses | Customers and customer addresses | Shopify's customer CSV columns do not include passwords, and Shopify says passwords cannot be migrated by CSV; plan a reset or account activation email |
| Customer tags and segments | Customer groups or attributes | Groups drive pricing and tax in Magento |
| Orders | Orders (via API or migration tool) | Usually imported as historical records; decide how many years |
| Discount codes | Cart price rules | Rebuild rules; test stacking behavior |
| Gift cards | Adobe Commerce gift cards or an extension | Migrate balances and codes; Open Source needs an extension |
| Markets, languages, currencies | Websites, stores and store views | Plan scope before import; prices and translations depend on it |
| Pages and blog posts | CMS pages and a blog extension | Move content, titles and meta descriptions |
| Redirects in Shopify | URL rewrites | Combine with new redirects for old Shopify URLs |
URL patterns to redirect
Shopify uses fixed path prefixes, so the redirect map is predictable:
/products/handleto the new product URL/collections/handleto the matching category/collections/handle/products/handleto the product URL (these collection-scoped product URLs are common in Shopify themes)/pages/handleto the CMS page/blogs/blog-name/handleto the blog post
Add these as permanent redirects in Magento's URL rewrites or at the web server or CDN. Our ecommerce SEO migration checklist has a redirect-map template and a launch monitoring plan.
Migration steps
- Inventory apps. List each Shopify app and what job it does. For each, choose a native Magento feature, an extension or custom code.
- Design the catalog model. Attribute sets, configurable attributes, categories and store views come first.
- Build the store on hosting that meets the 2.4.9 requirements, including the theme and checkout.
- Script the transform. Export from Shopify, transform to Magento import formats, import, and reconcile counts. Repeat until clean.
- Rebuild integrations against Magento's APIs: ERP, shipping, tax, email and analytics.
- Test end to end, including payments, tax by region, discounts and order export.
- Cut over with a final export of new customers and orders, DNS switch and redirects.
- Re-engage customers with a clear account activation or password reset message.
Common pitfalls
- Underestimating hosting and maintenance. On Shopify, the platform is maintained for you. On Magento, upgrades and patches are your job or your agency's.
- Treating tags as data. Shopify stores often use tags for filters, badges and logic. Each use needs a proper Magento equivalent.
- Losing reviews. Reviews often live in a Shopify app; export them separately and check their structured data on the new site.
- Forgetting subscriptions. Subscription contracts usually live with a third-party provider; confirm how they transfer and how payment tokens are handled with that provider.
Frequently asked questions
Is there a tool that moves Shopify to Magento automatically?
Third-party migration services move products, customers and orders, and can save time. They do not design your attribute model, rebuild apps or set redirects for you, so expect manual work around them.
Can customer passwords move?
No. Shopify's documented customer CSV columns do not include passwords, and its help center notes that encrypted passwords cannot be moved by CSV. Plan an activation or reset email at launch.
Will SEO suffer?
Some fluctuation is normal during any site move. Complete redirects, migrated metadata and an unblocked new site keep it short.
Next step
If the signals point toward Adobe Commerce, Mistri's Magento migration services cover catalog modeling, data transforms and redirect mapping, with a scope set after an initial audit.
Sources
Import and export customers (Shopify Help Center); Data import (Adobe Experience League); How to move a site with URL changes (Google Search Central).
