How long does a Magento 2 upgrade take?

Two to four weeks for stores on a recent minor version. Four to eight for stores on a major version behind. Older 2.3.x stores get a fixed quote after discovery because the migration path is longer.

Will my third-party modules still work?

We audit every third-party module against the target version before work begins. Modules without a compatible release are flagged and you decide whether to upgrade, swap or build a custom fix. We do not surprise you mid-cutover.

We aim for under 15 minutes of read-only mode during the cutover. Database migrations and reindexing happen in the background. We schedule the cutover in your lowest-traffic window.

Full database snapshot before cutover. Full file system snapshot. Rollback plan tested on staging. We do not start production work until the rollback path is proven.

Do you handle Adobe Commerce upgrades too?

Yes. Adobe Commerce upgrades follow the same process. Adobe Commerce Cloud customers get an additional ECE-Tools and infrastructure review.

Magento Optimization

Mise à niveau Magento 2

Mettez votre boutique à jour vers la dernière version Magento 2.4.x sans temps d'arrêt et sans modules cassés. Prix fixe, plan de retour inclus.

Timeline: 2 to 4 weeks
Audit: Pre-upgrade compat
Patches: All current
Rollback: Tested plan

Overview

What it is.

Les mises à niveau de Magento échouent lorsqu'elles cassent des modules que personne n'a testés, rendent le processus de paiement indisponible un dimanche ou dégradent silencieusement la vitesse du site. Les nôtres ne le font pas. Nous réalisons un audit de compatibilité sur chaque module, corrigeons ceux qui nécessitent une correction, appliquons les correctifs de sécurité et effectuons la transition à un moment de votre choix. Chaque mise à niveau est accompagnée d'une base de performance avant et après, afin que vous puissiez prouver que la mise à niveau n'a pas empiré les choses. Plan de retour inclus. Mise à niveau typique : 2 à 4 semaines.

What you get

Deliverables.

Pre-upgrade compatibility audit (custom modules + third-party extensions)
Composer dependency upgrade with version pinning
All current Magento security patches applied
Custom-module compatibility fixes
Third-party extension upgrade or vendor liaison
Performance baseline before and after
Rollback plan tested on staging
Production cutover during agreed maintenance window

Honest limits

What it isn't.

Vendor support response times for third-party modules are outside our control
Stores on EOL versions (2.3.x and below) get a longer fixed quote
We do not bypass official Magento patches with custom workarounds

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Compatibility audit
Audit custom modules, third-party extensions and theme for upgrade compatibility.
02
2. Staging upgrade
Full upgrade on staging. Issues catalogued and resolved.
03
3. QA + sign-off
Customer journeys tested. Performance baselined. Sign-off from your team.
04
4. Production cutover
Upgrade in the agreed maintenance window. Rollback plan ready if needed.

Frequently asked

Questions we get from people about to book.

How long does a Magento 2 upgrade take?: Two to four weeks for stores on a recent minor version. Four to eight for stores on a major version behind. Older 2.3.x stores get a fixed quote after discovery because the migration path is longer.
Will my third-party modules still work?: We audit every third-party module against the target version before work begins. Modules without a compatible release are flagged and you decide whether to upgrade, swap or build a custom fix. We do not surprise you mid-cutover.
What about downtime?: We aim for under 15 minutes of read-only mode during the cutover. Database migrations and reindexing happen in the background. We schedule the cutover in your lowest-traffic window.
Is my data safe?: Full database snapshot before cutover. Full file system snapshot. Rollback plan tested on staging. We do not start production work until the rollback path is proven.
Do you handle Adobe Commerce upgrades too?: Yes. Adobe Commerce upgrades follow the same process. Adobe Commerce Cloud customers get an additional ECE-Tools and infrastructure review.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Magento Optimization

Mise à niveau Magento 2

Mettez votre boutique à jour vers la dernière version Magento 2.4.x sans temps d'arrêt et sans modules cassés. Prix fixe, plan de retour inclus.

Timeline: 2 to 4 weeks
Audit: Pre-upgrade compat
Patches: All current
Rollback: Tested plan

Overview

What it is.

What you get

Deliverables.

Pre-upgrade compatibility audit (custom modules + third-party extensions)
Composer dependency upgrade with version pinning
All current Magento security patches applied
Custom-module compatibility fixes
Third-party extension upgrade or vendor liaison
Performance baseline before and after
Rollback plan tested on staging
Production cutover during agreed maintenance window

Honest limits

What it isn't.

Vendor support response times for third-party modules are outside our control
Stores on EOL versions (2.3.x and below) get a longer fixed quote
We do not bypass official Magento patches with custom workarounds

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Compatibility audit
Audit custom modules, third-party extensions and theme for upgrade compatibility.
02
2. Staging upgrade
Full upgrade on staging. Issues catalogued and resolved.
03
3. QA + sign-off
Customer journeys tested. Performance baselined. Sign-off from your team.
04
4. Production cutover
Upgrade in the agreed maintenance window. Rollback plan ready if needed.

Frequently asked

Questions we get from people about to book.

How long does a Magento 2 upgrade take?: Two to four weeks for stores on a recent minor version. Four to eight for stores on a major version behind. Older 2.3.x stores get a fixed quote after discovery because the migration path is longer.
Will my third-party modules still work?: We audit every third-party module against the target version before work begins. Modules without a compatible release are flagged and you decide whether to upgrade, swap or build a custom fix. We do not surprise you mid-cutover.
What about downtime?: We aim for under 15 minutes of read-only mode during the cutover. Database migrations and reindexing happen in the background. We schedule the cutover in your lowest-traffic window.
Is my data safe?: Full database snapshot before cutover. Full file system snapshot. Rollback plan tested on staging. We do not start production work until the rollback path is proven.
Do you handle Adobe Commerce upgrades too?: Yes. Adobe Commerce upgrades follow the same process. Adobe Commerce Cloud customers get an additional ECE-Tools and infrastructure review.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Mise à niveau Magento 2

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Compatibility audit

2. Staging upgrade

3. QA + sign-off

4. Production cutover

Questions we get from people about to book.

Tell us about your project.

Mise à niveau Magento 2

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Compatibility audit

2. Staging upgrade

3. QA + sign-off

4. Production cutover

Questions we get from people about to book.

Tell us about your project.