Magento upgrade guide

Magento upgrade planning: what to check before you start

A Magento upgrade is not only a core package change. Custom modules, themes, third-party extensions, PHP, Composer dependencies, integrations and operational workflows all need to move together.

Inventory

Know what the current platform actually contains

Before estimating an upgrade, create an inventory of Magento version, PHP version, Composer packages, extensions, custom modules, theme customisation, integrations, cron jobs, queues and deployment steps. Unknown dependencies are where upgrade projects lose time.

  • Magento/PHP versions
  • Composer package inventory
  • Custom modules and preferences/plugins
  • Theme overrides
  • Third-party extensions
  • Integrations and external APIs
  • Deployment and environment differences
Compatibility

Check the target version against every dependency

An extension being “Magento compatible” in general is not enough. Confirm support for the actual target release and PHP version. Where an extension is abandoned, decide whether to replace it, remove it or own the required changes.

Testing

Build a regression plan around business-critical flows

Technical tests matter, but the upgrade must also be validated against customer and operational workflows: catalogue, pricing, checkout, payments, order export, fulfilment, admin jobs and scheduled processes.

  • Customer registration/login
  • Product and category behaviour
  • Cart and checkout
  • Payment methods
  • Order processing and integrations
  • Cron/indexers/queues
  • Admin operational tasks
Deployment

Rehearse the production change

A staging upgrade that works is not the same as a rehearsed production deployment. Time database changes, static deployment, maintenance windows and validation, then define what happens if the launch must be rolled back.

Frequently asked questions

Questions we are often asked

Can we skip Magento versions?

Sometimes an upgrade path can move across several releases, but compatibility and database/application upgrade requirements must be validated for the specific starting point.

Should we upgrade extensions at the same time?

Yes where required for compatibility, but each change should be understood and tested.

How long does an upgrade take?

It varies widely with custom code, extensions, integrations and test coverage; a technical inventory is needed for a credible estimate.

Related expertise

Continue exploring

Need help applying this to your platform?

We can review your current environment and turn the guidance into a prioritised technical plan.

Start a Conversation