Magento 1 to Shopify Migration: What’s Different
A Magento 1 to Shopify migration moves the same records as a Magento 2 migration: products, customers, orders, redirects and content. What changes is the starting point. Magento 1 has had no vendor security patches since June 2020, its data usually leaves through older export paths and raw database tables, and most stores carry years of extensions nobody maintains any more. Magento 2 brings its own differences, mainly multi-source inventory and, on Adobe Commerce, content staging. Plan for the version you are actually on, not for a generic “Magento” migration.
This guide covers what stays the same across both versions, where Magento 1 needs extra care, where Magento 2 does, and whether upgrading to Magento 2 first is worth it. Platform facts come from Adobe’s end-of-support notices, Shopify’s Help Center and the migration tools’ own documentation.
Why the version matters in a Magento 1 to Shopify migration
Adobe ended support for Magento 1 on 30 June 2020. The last security patch for the 1.x line shipped a week earlier, and Adobe said plainly that it would not respond to further Magento 1 security issues. Its own end-of-support notice told merchants that anyone still running Magento 1 after that date had increased responsibility for their site’s security and PCI DSS compliance.
Some stores bridged the gap with OpenMage LTS, a community-maintained fork of Magento 1 that has kept shipping releases with newer PHP support. That keeps the core alive, but it does not update the third-party extensions a typical Magento 1 store depends on, and it is still a self-hosted platform you are responsible for securing.
For a migration, that history has three practical effects:
- The timeline is set by risk, not convenience. A store taking card payments on unpatched software should treat the move as overdue. Plan a short, firm project rather than a long redesign.
- The server is fragile. Old PHP versions, abandoned modules and hand-applied patches mean heavy export jobs can fail or slow the live store. Run exports against a copy where you can.
- Nobody remembers everything. Ten-year-old stores have custom fields, cron jobs and integrations whose owners have long gone. Inventory them before you map anything.
What is the same on Magento 1 and Magento 2
Both versions store the catalogue in the same entity-attribute-value (EAV) structure: a product is a row plus values spread across attribute tables. Both use configurable products, attribute sets and custom attributes, and both have to be translated into Shopify’s model of products, up to three options, variants and metafields. We cover that mapping in detail in our guide to Magento to Shopify product migration, and it applies to either version.
Customer passwords do not move on either version. Shopify hashes passwords its own way and cannot import hashes from another platform. That matters less than it used to. On Shopify’s new customer accounts, shoppers sign in with their email address and a one-time six-digit code, so there is no password to carry across. If you keep legacy customer accounts, plan an account-invite email instead.
Historical orders are the same story on both: Shopify’s admin cannot import them from a CSV file, so they go in through a migration app or the API. Our breakdown of Shopify migration apps covers which tools carry orders and which do not.

Where Magento 1 needs extra care
Getting the data out
Magento 1’s admin can export products and customers to CSV, and that file is what most migration tools start from. Matrixify’s Magento guides, for example, take the standard admin product export and work the same way on 1.x and 2.x. Orders are different. Matrixify’s order guide works from database table exports, and the table names change between versions: on Magento 1 the order data lives in sales_flat_order, sales_flat_order_item, sales_flat_order_address and sales_flat_order_payment. On Magento 2 the same tables drop the flat.
Practically, that means a Magento 1 migration usually needs someone with database access, not just admin access. Take a full database dump early and work from that copy.
URLs and handles
Shopify product URLs are always /products/handle and collections are /collections/handle. Magento URLs are whatever the store configured, often with a .html suffix and category paths baked in. Every old URL that earns traffic needs a 301 redirect to its new home.
There is a version-specific detail here. Matrixify’s product guide builds the Shopify handle from url_path on Magento 1 and from url_key on Magento 2. If your Magento 1 store has category paths in its product URLs, check the generated handles before import, because changing handles later means changing the redirects with them. Our guide to 301 redirects during a migration covers how to build and test the map.
Extension data
Magento 1 extensions often wrote to their own database tables: reviews, loyalty points, gift registries, product attachments, custom options. No migration tool knows about a module that its vendor abandoned years ago. List every installed extension, decide whether its data is worth keeping, and if it is, export that table and map it to a Shopify app or to metafields yourself. Expect this step to take longer than the catalogue.
Where Magento 2 needs extra care
Multi-source inventory
Magento 2.3 introduced Multi-Source Inventory, which tracks stock per source (a warehouse, a store, a drop-shipper) rather than as one number. Shopify tracks inventory per location. A store that uses multiple sources needs a source-to-location map before import, and a decision on sources that should not become Shopify locations at all, such as a supplier feed. A Magento 1 store, or a Magento 2 store on a single default source, has one quantity per product and a much simpler job.

Adobe Commerce staging
On Adobe Commerce, the paid edition, content staging lets merchants schedule product and content changes. Under the hood, the catalogue tables gain a row_id, so one product can have several versions waiting for future dates. Exports and direct database reads need to pick the current version only, or you will import scheduled prices and copy as if they were live. Check any scheduled updates before the final export.
Magento 1 vs Magento 2 at migration time
| Area | Magento 1 | Magento 2 |
|---|---|---|
| Vendor security patches | None since June 2020 (OpenMage is community-maintained) | Supported release lines receive patches |
| Order tables | sales_flat_order and related |
sales_order and related |
| Handle source in Matrixify | url_path |
url_key |
| Inventory | One quantity per product | One quantity, or multiple sources (2.3 and later) |
| Scheduled content | Not applicable | Adobe Commerce staging versions to filter out |
| Extension data | Often abandoned modules with their own tables | Usually maintained, still needs mapping |
| Customer passwords | Never migrate. Use one-time-code sign-in or account invites | |
Should you upgrade to Magento 2 first?
Rarely. Adobe’s Data Migration Tool moves data and settings from Magento 1 to Magento 2, but themes, extensions and custom code have to be rebuilt for Magento 2. Upgrading as a stepping stone means paying for one re-platform to reach the start line of another. If Shopify is the destination, go there directly from Magento 1. Our replatforming glossary entry sets out what a platform move involves in general.
The exception is a store that needs Magento’s open, self-hosted model: deep custom checkout logic, complex B2B pricing rules that no Shopify app covers, or hosting requirements that rule out a hosted platform. That is a platform-fit question, and it should be answered before any data moves.
A Magento 1 migration sequence that holds up
- Secure and freeze. Take a full database and media backup, stop non-essential admin changes, and confirm who still has server access.
- Inventory. List extensions, custom attributes, integrations, scheduled jobs and every URL with traffic or backlinks.
- Export. Pull products and customers from the admin, orders from the
sales_flat_*tables, and extension data from its own tables. - Dry run. Import a sample with a dry-run or demo mode, check handles, variants and metafields, and fix the mapping in the file rather than in Shopify.
- Redirects. Build the old-to-new URL map from
url_path, including the.htmlvariants, and test it before launch. - Customers. Decide on new customer accounts with one-time codes or legacy accounts with invites, and write the launch email either way.
- Delta and cut over. Re-run orders and customers created since the first export, switch DNS, and watch 404s and checkout for the first days.

The Shopify migration checklist turns these steps into a tickable list, and the Shopify migration cost guide explains what drives the budget, including the custom-data work that Magento 1 stores tend to need.
FAQ
Is Magento 1 still safe to run?
Adobe stopped releasing Magento 1 security patches in June 2020. Community forks such as OpenMage LTS still ship updates to the core, but third-party extensions and your own hosting remain your responsibility, including PCI DSS compliance if you take card payments.
Can Shopify’s free Store Migration app import from Magento?
No. Shopify’s Store Migration app does not list Magento as a source. Magento stores use a spreadsheet importer or a hosted connector service instead. Matrixify, for example, documents that its Magento route works the same way on 1.x and 2.x.
Is a Magento 2 to Shopify migration easier than Magento 1?
Usually a little, because extensions are more often maintained and the export paths are more standard. Multi-source inventory and Adobe Commerce staging add work that Magento 1 does not have, so check which of those your store uses.
The takeaway
Treat a Magento 1 to Shopify migration as a security project with a data problem attached: move promptly, work from a database copy, and budget time for extension data and redirects built from url_path. On Magento 2, the extra work sits in inventory sources and staged content. Either way, skip the Magento 2 detour if Shopify is where you are going. If you want a second pair of eyes on scope, our Magento to Shopify migration service starts with exactly this inventory.