Magento migration and Adobe Commerce moves in 2026

Plan a move to Magento or Adobe Commerce around products, custom fields and order history. Separate version upgrades from a change of platform.

Magento migration is possible, but the transfer route depends on your starting platform, edition and version. Retail teams moving from Magento 1 can use Adobe’s Data Migration Tool for supported version pairs. A move from another platform needs destination-ready imports and a separate plan for order history. Themes and checkout customisations need rebuilding or adapting.

The main risk is a store that contains the records but loses their relationships. A jacket with missing size options cannot be bought correctly. An imported order without its original reference is harder for staff to find.

Identify the migration you are actually making

Record the source and destination edition, exact version and hosting arrangement before choosing a migration method. Magento Open Source and Adobe Commerce are distinct products. Magento 1 and Magento 2 identify generations, so “Magento to Magento” alone does not specify a supported transfer.

For a Magento 1 to Magento 2 migration, match the source version to a configuration supplied with Adobe’s Data Migration Tool. Its documented edition routes cover Open Source to Open Source, Open Source to Commerce and Commerce to Commerce. Adobe’s configuration guide lists those routes and their version-specific directories.

A move between Magento 2 releases follows Adobe’s upgrade procedure. It is a different task from importing another platform’s records into a new store. For Magento 2, use the application version and installed package records to identify the starting installation. Adobe documents the available version checks.

Keep a working source store available while the destination is prepared. Commit to the new platform once its required extensions and checkout can handle your actual retail operations. If Shopify is your destination, the related Shopify migration guide covers that separate move.

Inventory custom data and storefront dependencies

Build a field map that records what each source field means and where its value belongs in the destination. Keep record transfer separate from the work needed to make those records usable.

Catalogue and order transfer map

ItemTransfer routeRetained informationLimit or manual action
Products and attributesSupported Magento 1 mapping or prepared product importStock keeping unit (SKU), names, prices and mapped attribute valuesDefine missing attributes and valid options before import
Attribute sets and variantsVersion-tool mappings or destination configuration plus product importAttribute-set assignment and parent-to-child SKU relationshipsCheck required fields and every sellable variation
Websites and store viewsVersion-tool settings or manual destination setupMapped store structure and scoped valuesRebuild another platform’s structure and language assignments
Customers and addressesSupported version transfer or customer importMapped identities and address fieldsResolve duplicates and test account access separately
OrdersSupported version transfer or a separately designed history transferOrder reference, line items and financial records included in the mappingStandard Admin import does not list orders as an import entity
MediaSeparate Magento 1 media copy or supported image importProduct images and their assignmentsCheck files as well as database references
Extensions and checkoutCompatible replacements or custom developmentOnly data explicitly handled by the chosen mappingRebuild behaviour, theme changes and payment connections

For product imports, Adobe’s field reference explains sku, store_view_code and attribute_set_code. It also distinguishes simple products from configurable products. Keep custom fields such as material or capacity as named attributes when customers use them to compare products.

Record each extension’s version, stored data and replacement alongside its owner. Include checkout changes, stock integrations and scheduled exports. A copied extension table does not supply working destination code.

Ask for a migration quote that separates data mapping from theme and extension work. Include trial transfers, checkout testing and cutover support in the scope. Catalogue size alone does not describe the rebuild effort or establish a Magento 1 to Magento 2 migration cost.

Choose a supported transfer route

Use Adobe’s Data Migration Tool for its documented Magento 1 to Magento 2 routes. The installed tool release must match the destination Magento 2 release, under Adobe’s installation requirements. A matching release still needs the correct source-version configuration and custom mappings.

The tool moves settings, bulk data and then incremental changes, called deltas. It checks database structures and record volumes. Adobe’s migration explanation describes this sequence. These checks help identify transfer problems, while storefront tests establish whether customers can use the migrated data.

Custom extension data needs separate attention. Adobe documents automatic transfer where the relevant structures match, mapping for smaller differences and custom steps for major changes. Follow its customisation guidance for those cases. Do not bypass an unmapped-field error by discarding data that your store still needs.

For another source platform, prepare files against the destination’s own samples. The Admin import procedure supports product and customer data, including addresses, plus other listed entities. It does not provide a general historical-order CSV import. Use a separately specified history transfer or a restricted archive for those orders.

Use Add/Update when that operation fits the trial. Replace can delete and recreate matching products, breaking existing references. Create required custom attributes first because an unknown attribute column does not create its definition.

Rebuild and reconcile the destination

Prepare and test the destination before attempting the final transfer of changes. Use a separate test environment with access restricted to the migration team.

  1. Back up the source database and media. Prepare the destination against its system requirements, then save its initial database state. Adobe’s prerequisites cover database access and destination cron restrictions.
  2. Run a full rehearsal against a source copy. For a version-tool migration, follow settings, data and delta order. Adobe’s migration overview also restricts Admin and code changes during the transfer.
  3. Correct mappings and repeat the trial where required. For configurable imports, use an exported destination example to check the parent and variation rows. Adobe’s configurable-product example explains those relationships.
  4. Finish the theme, extension replacements and checkout configuration. Rebuild search indexes and test store-view behaviour. Keep the migration dataset consistent while incremental changes are still arriving.
  5. Compare source and destination counts using the same agreed inclusion rules. Investigate rejected records and unexplained differences before scheduling the final delta or final source export.

As an illustrative acceptance sample, take one jacket with four sellable colour-and-size variants. Expect one configurable parent linked to all four child SKUs. Compare its material attribute and each store view’s description with the source.

If the agreed customer sample contains 25 unique accounts, expect 25 accepted destination accounts or an explained mapping for each exclusion. For sampled orders, match the original reference and customer, then compare line quantities, discounts, tax and the paid total. A matching order count alone does not prove the history is correct.

Keep catalogue answers and orders traceable

Preserve stable product identifiers and attribute meanings so search and shopping assistance still refer to the right items after migration. If identifiers change, keep an explicit old-to-new mapping for product feeds and connected systems.

Test a request for a particular material and size against the migrated catalogue. The answer must refer to an eligible variant with the correct availability. A generic parent description cannot replace missing variant stock or dimensions.

Give authorised support staff a documented way to find both migrated and archived orders. A restricted archive can retain historical orders when the destination does not contain them. Record its search method and access permissions, along with the original order references.

An assistant’s catalogue connection does not establish access to that archive. Connect order support only through a defined, authorised lookup route. Staff must still be able to answer an older-order enquiry when automated lookup does not cover that history.

Protect URLs and checkout at cutover

Map useful old product URLs to their matching destination pages and test the redirects before switching traffic. Preserve a working product URL when possible. When a URL changes, send it to the equivalent item with a permanent redirect and check that the destination is available.

Reconfigure payment credentials and callbacks for the destination. Test shipping and tax rules as well as stock updates from connected systems. Set order email senders and recipients, then confirm the customer and fulfilment team receive the intended notifications once.

Use these acceptance checks before routing live customers to the new store:

  • Buy the illustrative jacket in one size and colour through the payment provider’s test flow. The order must show the chosen child SKU and agreed total. Stock must update for that variation through the intended inventory process.
  • Open an older order by its original reference as an authorised support user. Expect the matching customer, purchased items and recorded payment or refund information in the destination or archive.
  • Follow an old product URL and complete the same purchase path. Expect the correct item, an available option and a usable checkout without a redirect loop.
  • Check a failed payment. The store must not present it as a paid order or send a paid-order notification.

For a version-tool move, use Adobe’s cutover plan to control source maintenance mode and incremental updates. Confirm the final captured orders and stock changes before switching. Restart destination jobs in the planned sequence and monitor incoming orders after release.

Retain source records and a recovery point

Keep source backups and a tested way to restore service until the new store’s transactions reconcile. Name the person who can stop cutover and the evidence they need to approve it.

Stop if an accepted source order is absent, a configurable product loses a sellable variant or the final delta has unexplained differences. A checkout that charges the wrong amount also fails acceptance. Keep traffic on the source while the team fixes those problems.

If you return traffic to an available source after the destination has accepted orders, pause new destination sales first. Reconcile every destination order and payment before reopening the source. Simply restoring an earlier database can lose those orders or create duplicate fulfilment.

Bring in a migration specialist for unsupported custom records, changed extension schemas or a delta that will not reconcile. Give them the source-version details, field map and failed-record examples. Keep the original records available until each discrepancy has an explained outcome and staff can retrieve the history they need.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup