ecommercecraft

Migrations and upgrades

Magento 1 or 2 to Adobe Commerce, and cloud moves, without the drama. Data, extensions and search rankings carried over with a rehearsed cutover.

Who this is for

  • Merchants still on Magento 1 or on a Magento 2 version that no longer receives security patches
  • Teams planning a hosting move to Adobe Commerce Cloud or Upsun
  • Agencies that need a senior engineer to de-risk a migration already underway

What you get

  • A code and extension inventory

    Every custom module and third-party extension marked keep, replace or drop, with the effort in hours.

  • Data that arrives complete

    Customers, orders, catalog and CMS content migrated and reconciled against the source.

  • Search rankings kept

    A redirect map for every indexed URL, checked before launch, not after.

  • A rehearsed cutover

    A written runbook, run at least once on a production copy, with a rollback path.

How it works

  1. Weeks 1 to 2

    Inventory

    Extensions, custom code, data and integrations listed and each one given a decision.

  2. Build phase

    Rehearse

    Code ported and data migrated in repeated dry runs against a copy of production.

  3. Launch week

    Cut over

    Final data sync, redirects live, a monitored launch and a rollback plan on the table.

In detail

A migration is rarely one move. It is a data migration, an extension audit, a theme rebuild, a redirect map and a cutover weekend, and any one of them can push the launch date.

I have worked on Magento since 2009, from Magento 1 Enterprise builds in Magento’s original Expert Consulting Group to Magento 2.x and Adobe Commerce on PHP 8 today. That covers both sides of most migrations: the codebase you have and the platform it is moving to.

The work starts with an inventory. Every custom module and third-party extension gets a decision: keep it, replace it with a maintained alternative, or drop it. Customer, order and catalog data are mapped and migrated in rehearsal runs against a copy of production, so the final cutover repeats something that already worked. Redirects are generated and checked before launch so search rankings survive the move.

The same method applies to version upgrades within Magento 2 and Adobe Commerce, and to hosting moves to Adobe Commerce Cloud or Upsun (formerly Platform.sh): find what breaks, fix it on a branch, rehearse, then switch.

Timelines depend on the inventory, so I quote after that step. I either lead the work alongside your team or deliver it hands-on, and the project ends with a stable store and a short list of follow-ups.

Related case study

Magento Inc. (Expert Consulting Group)Sporting goods and luxury watches

11Engineers led on Easton-Bell Sports

Read the case study

Not sure what your store needs next?

A 30-minute call is enough to find out.

Book a callSend a message