Magento
Magento 1 to Magento 2 Migration: Steps, Data, Cost and Checklist
Sergey
Published
Updated
8 min read
8 min read

Are you interested in the Magento Migration service?
Depending on your needs, we can offer many migration options. Would you like to know which ones?
If your store still runs on Magento 1, you already know it's living on borrowed time. This guide explains what a Magento 1 to Magento 2 migration actually involves: why it's a rebuild rather than an upgrade, how the data moves, the steps, what drives the cost, a checklist, and your options if you can't migrate yet.
Is Magento 1 still supported?
No. Adobe ended support for Magento 1 on June 30, 2020. Since then there have been no official security patches, and the platform was never updated for current PHP versions.
That doesn't mean every Magento 1 store is about to break. Some stores run patched builds, often on OpenMage, a community-maintained fork of Magento 1. But the risks grow every year: payment providers and PCI audits ask harder questions, extensions stop working, and fewer developers know the code.
Why Magento 1 to Magento 2 is a rebuild, not an upgrade
Magento 2 was rebuilt from the ground up. The database structure, themes, extensions and custom code all work differently. In practice:
- Your data moves with Adobe's Data Migration Tool and scripts.
- Your theme doesn't. It has to be rebuilt for Magento 2, either on the standard theme, on Hyvä, or as a separate headless storefront.
- Your extensions don't. Each one needs a Magento 2 version, a replacement, or a rebuild.
- Your custom code doesn't. Pricing rules, checkout changes and integrations are rewritten for Magento 2.
So the right question is not "how do we upgrade" but "what do we need to rebuild, and what can we drop".
What moves and what gets rebuilt
| Moves with the Data Migration Tool | Gets rebuilt for Magento 2 |
|---|---|
| Products, categories and attributes | Theme and page layouts |
| Customers and addresses | Extensions, replaced or rewritten |
| Orders, invoices and credit memos | Custom modules and pricing logic |
| CMS pages and blocks | Integrations with ERP, CRM, payments and feeds |
| URL rewrites | Email templates |
| Store, website and tax settings | Admin workflows your team relies on |
Magento 1 to Magento 2 data migration
Adobe's Data Migration Tool moves data from a Magento 1 database into a fresh Magento 2 installation. It works in three modes:
- Settings: store configuration, websites and tax rules.
- Data: products, categories, customers, orders and CMS content, in bulk.
- Delta: only what changed since the last run, such as new orders and customers. This is what lets the old store keep selling until launch.
The tool handles standard Magento tables well. Most of the real work is in everything else:
- Custom attributes and tables from extensions need map files that tell the tool where each field goes, or they're skipped.
- Product data is worth cleaning before you move it: discontinued products, duplicate attributes and broken images slow down the new store.
- Customer accounts move with their addresses and order history. Check whether passwords carry over in your setup, and plan a reset email if they don't.
- Run it more than once. Do a full test migration on staging, compare product counts, prices and order totals with the old store, fix the maps, and repeat until the numbers match.
Magento 1 to Magento 2 migration, step by step
- Audit the store. List every extension and what it does, all custom code, integrations, and the pages that bring search traffic. Decide what's still needed. Old stores usually carry features nobody uses.
- Choose the target. A current Magento 2.4 release on hosting that meets its requirements (PHP 8 and a search engine such as OpenSearch), and a front-end approach: standard theme, Hyvä, or a headless storefront.
- Rebuild on staging. Theme, extensions, custom modules and integrations, on a copy customers can't see.
- Migrate the data. Settings, then data, then test, fix the maps and run again.
- Protect your search rankings. URL rewrites migrate, but check them: map every old URL with traffic to its new address and keep titles, descriptions and structured data.
- Test the whole store. Test orders with every payment and shipping method and every customer group, emails, invoices and admin tasks.
- Launch with a delta. Freeze changes on the old store, run the delta migration, switch the domain, and check the first orders.
- Watch the first weeks. Monitor 404 errors and crawl reports in Google Search Console and fix missed redirects quickly.
How much a Magento 1 to Magento 2 migration costs
There's no honest average, because the cost depends on what the old store does, not on its size. The main drivers:
- Extensions and custom code. Each one is a decision: find a Magento 2 version, replace it, rebuild it or drop it.
- The front-end. A standard theme costs less than a custom design; Hyvä or headless change the scope again.
- Integrations. Every connected system has to be reconnected and tested.
- Data quality. Clean data migrates in days; years of inconsistent attributes take longer.
- SEO risk. The more search traffic your URLs carry, the more care the redirects need.
A small store with standard extensions can move in weeks. A store with custom pricing, several websites and integrations takes months. Our own Magento 1 migrations start with a plan and a fixed estimate, from $6,000.
If you're not ready to migrate yet
Not every Magento 1 store can move this quarter, and some run safely for years with the right care. These are the realistic options.
Keep Magento 1 secure in the meantime
- Security patches. OpenMage, a community fork of Magento 1, is free and keeps releasing security fixes. Paid patch subscriptions exist too: Mage One, for example, lists prices from €29 a month for small shops, rising with annual revenue (its published price list dates from 2020).
- Patches are only part of the job. Someone still has to apply them, keep the store running on current PHP versions, watch the traffic and fix what breaks. That's development and support work, paid separately. Our support starts at $800 a month.
What that looks like in practice
One of our clients has run a custom store on Magento 1.7 with us since 2014. We keep it patched, made it run on PHP 8.5, monitor its traffic in Cloudflare and apply security rules there, and read the server logs to see where attackers are probing for weak spots. When we find one, we close it, and the same hole rarely comes back.
There were periods when Magento 1 stores were attacked heavily and a new issue showed up every month or every few months. In the last eight or nine months we haven't seen a single error linked to a break-in attempt. Support for this store, including the tasks the client sends us, runs about $800 a month. We also recently replaced its search with a separate service next to the store: it now handles typos, answers much faster, adds almost no load to the site and searches the blog too.
Staying is possible, but it's a choice you renew every year, not a plan.
Move to another platform, or go headless later
- Another platform. If the catalog is simple, a hosted platform may cost less to own. Compare the full cost first in Magento vs Shopify, and see how a move to a new platform works in our step-by-step migration guide.
- Headless. A headless storefront needs Magento 2 behind it, so it comes after the migration, not instead of it.
Magento 1 to Magento 2 migration checklist
- [ ] List of extensions, with a decision for each: keep, replace, rebuild, drop
- [ ] List of custom code and integrations
- [ ] Pages with search traffic, from Google Search Console
- [ ] Target Magento 2 version, hosting and front-end chosen
- [ ] Map files for custom attributes and tables
- [ ] Test migration on staging, with counts checked against the old store
- [ ] Redirect map for every URL with traffic
- [ ] Test orders for every payment method, shipping method and customer group
- [ ] Password reset email ready, if passwords don't carry over
- [ ] Launch plan: change freeze, delta migration, domain switch, rollback
- [ ] 404 and crawl monitoring for the first weeks
Questions about Magento 1 to Magento 2 migration
How long does a Magento 1 to Magento 2 migration take?
From a few weeks for a small store with standard extensions to several months for a store with custom features, several websites and integrations. The audit gives you a timeline for your store.
Can we use the Data Migration Tool ourselves?
Yes, it's free and documented by Adobe. It moves standard data well. The time goes into mapping custom fields, rebuilding the theme and extensions, and testing, which the tool doesn't do.
Do our Magento 1 extensions work on Magento 2?
No. Each extension needs its Magento 2 version from the vendor, a replacement, or a rebuild. It's also a good moment to drop the ones you no longer use.
Will we lose our search rankings?
Not if every URL with traffic is redirected to its new address and titles, descriptions and structured data move with the pages. Expect some movement for a few weeks after launch.
How much does it cost to keep Magento 1 running?
Patches can be free (OpenMage) or a paid subscription. The bigger cost is the work around them: applying patches, PHP compatibility, monitoring and fixes. For one long-running Magento 1 store we support, that comes to about $800 a month, including the client's own tasks.
Can we keep our current design?
The design can stay, but the theme has to be rebuilt for Magento 2. Many stores use the migration to refresh the front-end at the same time.
Moving off Magento 1? We'll audit your store, tell you what has to be rebuilt and what can go, and give you a plan with a fixed estimate before any work starts. See our Magento 1 to Magento 2 migration services.