E-commerce migration
Migrate to Adobe Commercefor enterprise-grade scalability and B2B capabilities
Whether you are leaving Magento 1 or arriving from another platform, the work sits in product types, scopes and the things Adobe's migration tool doesn't move. Here is that list.
A data model with more moving parts
Adobe Commerce has seven product types: simple, configurable, grouped, virtual, bundle, downloadable and gift card, the last available only in Adobe Commerce. A configurable product is a parent over separate simple products, each with its own SKU and stock. Stores coming from a platform where variants live inside one product record have to create those child products explicitly.
Attributes use an entity-attribute-value model, and most settings can vary by website, store and store view. That scope tree is what makes it a good fit for several brands or languages on one install. It is also where imports go wrong: a value set at the wrong scope looks right in one storefront and wrong in another. So we map scopes before attributes.
What the Data Migration Tool leaves to you
If you are moving from Magento 1, Adobe's Data Migration Tool does the bulk of the database work, in settings, data and delta modes. Its documentation is clear about the gaps, and they should be in your plan:
- Media files are not part of the tool's transfer. They are copied by hand from the old media directory to pub/media.
- Settings mode doesn't move every configuration setting, and doesn't move time zones. Each setting has to be checked in the new Admin.
- Delta mode only follows data created by Magento's own modules. New attributes or CMS pages entered in the Admin during the delta window are not carried across.
- Third-party extension data needs the extension's Magento 2 version and, where the tables differ, custom mapping files.
- Split databases aren't supported.
Which version you land on
Adobe's lifecycle policy, last updated in September 2026, gives standard support until May 31, 2029 for 2.4.9, May 31, 2028 for 2.4.8 and May 31, 2027 for 2.4.7. Standard support for 2.4.6 ended on August 11, 2026. A migration starting today should target 2.4.9 unless an extension you rely on rules it out, and that check belongs in the first week of the project, not the last.
The rest of the rebuild
Themes and custom code don't transfer from Magento 1, or from another platform, so storefront and customisations are new work. We inventory each extension and customisation and sort them into keep, replace with a current extension, rebuild, or drop. Customisation that exists only to work around an old bug or a plugin that is long gone is common, and dropping it is the cheapest saving in the project.
What we can show you
We have no published Adobe Commerce migration. The nearest proof we can offer is the method behind our published upgrades: an eight-month PHP 5.6 to Laravel 13 move for a cabinet manufacturer with workflows verified against the old system in parallel, and a long-running WooCommerce store. Those are other platforms, so judge us on the plan for yours.
Adobe Commerce migration questions
Is Magento 1 data still movable?
Yes. Adobe still documents the Data Migration Tool for moving Magento 1 data. Check first that your Magento 1 version and your database setup meet its prerequisites; split databases aren't supported.
Will our Magento extensions come with us?
Not as they are. Extension code has to be replaced with a version built for the new platform, and any extension data with a different table structure needs custom mapping.
Send us your extension list
An export of installed extensions and your current version is enough for a first read on what moves, what gets replaced and what can go.
We reply within one business day (IST).