Skip to content
MAGENTO

How to Migrate From Magento 1 to a Current Magento Version (2.4.x)

The six steps to move a Magento 1 store to a current version of Magento with Adobe's Data Migration Tool, what the tool does not move, the commands, and the errors that stall a run.

Shane Blandford
Shane Blandford · FOUNDERPUBLISHED · 5 MIN READ

To migrate a Magento 1 store to a current version of Magento, you install a new store on a supported release, move the data with Adobe's Data Migration Tool, copy media files by hand, rebuild the theme, extensions and custom code (the tool does not carry those over), redirect every changed URL, rehearse the whole run on a copy of the database, and then cut over by pointing DNS at the new store. Adobe says the effort depends on how the site was built and how far it was customized.

Last updated: November 18, 2026.

Magento 1 Open Source no longer gets Adobe security fixes. Adobe's Magento Open Source maintenance policy lists June 2020 as the end of Adobe security maintenance for Community Edition 1.5 through 1.9.

Key takeaways

  • The Data Migration Tool moves data and settings. Media files, the theme, extensions, custom code, admin user accounts and API credentials are copied or rebuilt by hand.
  • The tool's version must match the target Magento release exactly, and it runs in a fixed order: settings, then data, then delta.
  • Rehearse on a copy of the Magento 1 database, never the live one, and expect several runs while you fix map errors.
  • Adobe's 9-hour benchmark excludes URL rewrites, which Adobe puts at about 85% of the data. Time your own rehearsal instead.
  • A stalled migration can often be picked up from its config.xml, map files and logs. We take over stalled migrations as well as new ones.

Orange Collar Media has built Magento stores since 2008 (800+ Magento builds) and migrates stores from Magento 1, older Magento releases, Shopify, BigCommerce and WooCommerce. For the service view, see our Magento migration services page. This guide is the how-to.

What should you check before you start a Magento 1 migration?

Check your source version, your extensions and their data, your customizations, your media, and how much old data you are carrying. The tool's supported-versions page lists Adobe Commerce 1.11.x to 1.14.x and Magento Open Source 1.6.x to 1.9.x as sources, so confirm the exact version first.

SOURCE VERSIONAdobe Commerce 1.11.x to 1.14.x, or Magento Open Source 1.6.x to 1.9.x
EXTENSIONSList every one. Note which have a current-release version, which to drop and which to rebuild
EXTENSION DATADecide which extension tables to carry over. Where the new structure differs, the tool's map files handle it
THEME AND CUSTOM CODERebuilt for the new architecture, so scope it page by page
MEDIAProduct, category and WYSIWYG images are copied by hand from media to pub/media
ADMIN USERS AND API ACCESSAdmin accounts, roles and SOAP, XML-RPC and REST credentials are re-created by hand
OLD DATALogs, quotes, recently viewed and compared products, visitors and old promotions can be cleared first
HARDWAREAdobe says to build the new environment to at least match the Magento 1 topology
TARGET VERSIONA supported release; see our versions guide for current support windows

Adobe's best-practices page says to remove outdated and redundant data before you migrate, which shortens the data run. For the target release, our Magento versions guide lists current release dates and support windows.

What does the Data Migration Tool move, and what do you rebuild?

The tool moves store data and settings. Adobe lists four kinds of data that need manual migration: media, storefront design, admin user accounts and access control lists.

PRODUCTS, CATEGORIES, CUSTOMERS, ORDERS, CONFIGURATION, PROMOTIONSData Migration Tool, settings and data modes
PRODUCT, CUSTOMER AND RMA ATTRIBUTESData Migration Tool, EAV step
URL REWRITESData Migration Tool, URL Rewrite step. Check the output
ORDERS, REVIEWS AND PROFILE CHANGES AFTER THE MAIN RUNDelta mode
ATTRIBUTES AND CMS PAGES EDITED IN THE ADMIN AFTER THE MAIN RUNNot tracked by delta. Freeze them or redo them by hand
THIRD-PARTY EXTENSION DATAInstall the extension's current version first. Delta needs custom configuration
MEDIA FILESCopy by hand from media to pub/media. Do not copy the Magento 1 media .htaccess files
THEME AND STOREFRONT DESIGNRebuild
EXTENSIONS AND CUSTOM CODEReplace with a current version or rebuild
ADMIN USERS, ROLES AND API CREDENTIALSRe-create by hand

How do you migrate a Magento 1 store, step by step?

Follow these six steps in order. Each one has a gate: do not start the next until the check for the current one passes.

01

Audit the Magento 1 store

Record the version, every extension, every customization, the theme, integrations (ERP, payments, shipping) and the URL structure. Export indexed URLs and top landing pages now; they become your redirect list. Clear junk data. This inventory becomes the scope.

02

Map extensions and rebuild the theme

Install a fresh supported release on the new hardware. For each extension, install a current version or rebuild it; install the ones whose data you migrate before the data run. Rebuild the theme and custom behavior for the new architecture.

03

Migrate the data with the Data Migration Tool

Install the tool at the exact version of your Magento release, fill in config.xml (both databases and the Magento 1 crypt key), and stop all Magento 1 cron jobs. On a copy of the Magento 1 database, run settings, copy media to pub/media, then run data. When the tool stops on an unmapped table or field, fix the map file and run again with --reset.

04

Preserve URLs and SEO

Compare the URL Rewrite step's output with your redirect list. Redirect every changed URL with a 301, keep titles, meta data and canonical tags, and crawl the new store for 404s and redirect chains before launch.

05

Test against real data

Check catalog, pricing, tax, shipping, checkout, payment, order emails, customer login and admin on the migrated copy, and test integrations with real order flows. Start delta mode so new Magento 1 orders keep flowing across while you test.

06

Cut over

Put Magento 1 into maintenance mode and stop admin work, stop delta with Ctrl+C, start cron on the new store, flush caches, reindex, warm the page cache and run final checks. Then point DNS and load balancers at the new store and watch 404s, crawl errors and orders.

Two Adobe rules apply while data moves: do not change the Magento 1 admin except for order management (shipping, invoices and credit memos), and do not change the new store's admin or storefront. Adobe also warns that deleting a product on the new store that appears in past Magento 1 orders can cause delta errors.

Adobe's benchmark used a test database with 177,000 products, 355,000 orders and 214,000 customers on a virtual machine with one 2.6 GHz CPU core and 2.5 GB of RAM. Settings took about 10 minutes and data about 9 hours, but the 9 hours exclude URL rewrites, which Adobe says make up about 85% of the data. Estimated downtime was a few minutes for reindexing and DNS, plus page cache warm-up. Your rehearsal on a copy is the only timing that counts for your store.

What commands does the Data Migration Tool use?

Every mode uses the same pattern: bin/magento migrate:<mode> followed by the absolute path to config.xml. Adobe recommends running the modes in the order below.

COMPOSER REQUIRE MAGENTO/DATA-MIGRATION-TOOL:<VERSION>Installs the tool. Adobe says the tool and Magento versions must match
BIN/MAGENTO MIGRATE:SETTINGS <PATH TO CONFIG.XML>Moves websites, stores, store views and configuration
BIN/MAGENTO MIGRATE:DATA <PATH TO CONFIG.XML>The bulk move. Each step runs an integrity check, the transfer and a volume check
BIN/MAGENTO MIGRATE:DELTA <PATH TO CONFIG.XML>Moves changes since the last run. Runs continuously, restarting every 5 seconds, until Ctrl+C
--RESET (-R)Starts the mode from the beginning. Use it between rehearsal runs
--AUTO (-A)Keeps the run going past integrity check errors. Read the log before you trust the result

The config.xml template sits under vendor/magento/data-migration-tool/etc/, in a folder for your edition pair (opensource-to-opensource, opensource-to-commerce or commerce-to-commerce) and your Magento 1 version. Copy config.xml.dist to config.xml and set the source and destination database details. The crypt_key value is required and comes from the key tag in the Magento 1 app/etc/local.xml file. Custom map files go in your own module, with their path set in config.xml. To speed up the data run, Adobe suggests the direct_document_copy option, which needs both databases on the same MySQL server.

Which errors stop a Magento 1 data migration?

Most stops come from data the map files do not describe. Adobe documents these cases:

THE TOOL REPORTS A DIFFERENCE AND WILL NOT STARTA table or field differs between the databases and is not declared in the map files, often one that belongs to a Magento 1 extension. Add an ignore or rename rule to the map file, or install the extension's current version
VOLUME CHECK WARNINGSRecord counts differ between source and destination. Adobe says to expect them if you test the new store while delta runs
DELTA ERRORS AFTER CATALOG EDITSA product removed from the new store still appears in Magento 1 orders. Avoid catalog, sales rule and CMS changes while delta runs
THIRD-PARTY DATA MISSING AFTER DELTADelta only tracks data created by Magento's own modules. Extension data needs custom delta configuration

What if your Magento 1 migration has stalled?

A stalled migration can often be resumed from where it stopped rather than restarted. We migrate stores from Magento 1 and take over stalled prior migrations. Start by recording what already ran: the target version and tool version, the config.xml and map files used, which modes completed, and the log errors. Then fix the map errors on a test copy before another full run. Send us that record through the migration page and we will say whether it is a pick-up or a restart.

How much does a Magento 1 migration cost?

The cost depends on extensions, theme complexity, data volume and integrations, so it is quoted after scoping. Our Magento cost guide breaks down what drives the number. If your store already runs a 2.x release of Magento and only needs a newer one, the version upgrade service page explains how an upgrade differs from a migration.

FAQ

How long does it take to migrate from Magento 1 to current Magento?+
It depends on your customizations, extension count and data volume. Adobe's benchmark data run (177,000 products, 355,000 orders, 214,000 customers) took about 9 hours, not counting URL rewrites, which Adobe says are about 85% of the data. The theme and extension rebuild is scoped separately. We give a timeline after scoping.
Is Magento 1 still supported by Adobe?+
No. Adobe's Magento Open Source maintenance policy lists June 2020 as the end of Adobe security maintenance for Community Edition 1.5 through 1.9, so those releases get no new security patches.
Can I migrate from Magento 1 without losing SEO?+
Yes, if you redirect every changed URL with a 301, keep titles, meta data and canonical tags, and crawl both sites to compare. The Data Migration Tool has a URL Rewrite step, but check its output against your list of indexed URLs.
Does the Data Migration Tool move my theme, extensions and images?+
No. It moves store data such as products, customers, orders, configuration and promotions. Adobe lists media, storefront design, admin user accounts and access control lists as manual work, and extensions and custom code are rebuilt for the new architecture.
Which Magento 1 versions can I migrate from?+
Adobe Commerce 1.11.x to 1.14.x and Magento Open Source 1.6.x to 1.9.x, per Adobe's Data Migration Tool documentation.
Should I move to current Magento or switch platforms?+
Adobe's Data Migration Tool only moves Magento 1 data into Magento. Moving to another platform means a different import route and a rebuild there. List what your store depends on (custom logic, B2B features, integrations) and check each option against that list before you decide.
Can you fix a Magento 1 migration that stalled?+
Often, yes. We take over stalled migrations. We start from the config.xml and map files, the modes that completed and the error log, then decide whether to continue or restart.
Shane Blandford

Shane Blandford

FOUNDER

Founder of Orange Collar Media, a Denver ecommerce agency behind 800+ Magento and Shopify builds. In Magento since version 1.x - building, rescuing, and supporting revenue-critical stores since 2008.

All posts by Shane Blandford→

KEEP READING

Related from the Journal.

Your store can sell more. Let's find out how much.

Start a project