Migrations and upgrades
A platform chosen on evidence, then a move or upgrade with data and search rankings carried over and the cutover rehearsed before launch.
Who this is for
- Merchants who have outgrown their platform and need to choose the next one
- Merchants on Magento 1, or on a Magento 2 or Adobe Commerce version that no longer receives security patches
- Agencies that want a senior architect to check a migration already underway
What you get
A platform decision in writing
Whether to upgrade or replatform, and to which platform, decided against your catalog, integrations, team and budget.
An inventory of what moves
Every custom module, extension and integration marked keep, replace or drop, with the effort in hours.
Data and rankings carried over
Customers, orders, catalog and CMS content reconciled against the source, and a redirect map checked for every indexed URL.
A rehearsed cutover
A written runbook, run at least once on a production copy, with a rollback path.
How it works
Weeks 1 to 2
Inventory
Build phase
Rehearse
Launch week
Cut over
In detail
A replatforming project bundles a data migration, an extension and integration audit, a theme rebuild, a redirect map and a cutover weekend. Any one of them can push the launch date. Many merchants are stuck one step earlier, unsure whether to upgrade the platform they have or move to another.
I start with that decision. I weigh an upgrade of your current platform against a move to another one, based on your catalog, integrations, team and budget, and write down one recommendation. Then comes the inventory. Every custom module, extension and integration gets a decision: keep it, replace it with a maintained alternative, or drop it. I map customer, order and catalog data and migrate it in rehearsal runs against a copy of production, so the final cutover repeats something that already worked. I generate and check redirects before launch so search rankings survive the move. The same method covers version upgrades and hosting moves to Adobe Commerce Cloud or Upsun (formerly Platform.sh).
You get a written platform recommendation and, after launch, a stable store with a short list of follow-ups.
All my migration work has been on Magento and Adobe Commerce. I started in 2009 on Magento 1 Enterprise in Magento’s original Expert Consulting Group, and today I work on PHP 8, so I know both ends of a Magento 1 move.
Timelines depend on the inventory, so I quote after that step. I either lead the work alongside your team or deliver it hands-on.
Questions
How long does a migration take, and what does it cost?
That depends on what the inventory finds, so I quote a fixed scope after it. The inventory takes the first two weeks. It starts with the stay-or-move decision, then lists every extension, custom module, data set and integration with its own decision and the effort in hours.
Should we upgrade or move to another platform?
We settle that first, before any migration work. I compare the two options against your catalog, integrations, team and budget. You get one written recommendation, and the inventory builds on it.
How do you protect our search rankings?
I generate a redirect map before launch and check it for every indexed URL. In launch week the redirects go live with the final data sync, and the launch is monitored.
Can our team or agency do the work?
Yes. I either lead the work alongside your team or agency or deliver it hands-on. An agency with a migration already underway can also ask me to check it.
What if something goes wrong at launch?
The cutover follows a written runbook that has run at least once on a copy of production. A rollback plan is ready in launch week, so you can return to the old store if the launch fails.
Related case study
11Engineers led on Easton-Bell Sports
Leading Magento Enterprise builds in Magento's own consulting group
Read the case study