Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
A Magento upgrade has no standard price, because the cost depends on your store, not on the version number. Five things drive almost all of it: how many versions you are jumping, how many third-party extensions you run, how much custom code you have, how your theme is built, and how much your hosting stack has to change. A store that is one version behind with a dozen well-maintained extensions is a small project. A store three versions behind with heavy customization is a large one. A reliable fixed quote only comes after an audit of those five areas.
This guide explains each driver, gives you a matrix to score your own store, and covers the costs that are easy to forget.
What you are actually paying for
The new Magento version itself is not the cost. Magento Open Source is free to download, and Adobe Commerce releases are available to licensed customers. What you pay for is the work around it:
- Audit and planning: finding out what will break before you start.
- Code and extension work: updating, replacing or fixing modules so they run on the new version and PHP.
- Theme work: fixing frontend templates, layouts and JavaScript that changed between versions.
- Infrastructure changes: new PHP, database, search and cache versions on every environment.
- Testing: regression, integration, performance and user acceptance testing.
- Deployment and aftercare: go-live, monitoring and fixing what surfaces in the first weeks.
Adobe's own upgrade guide names the same effort factors: technical complexity, customizations, number of extensions, how often you upgrade, third-party integrations, testing strategy and how closely the code follows best practices.
Cost-driver matrix: score your store
For each driver, pick the column that best describes your store. Mostly low signals point to a small project, mostly high signals to a large one. One high signal can outweigh several low ones.
| Driver | Low effort | Medium effort | High effort |
|---|---|---|---|
| Version gap | Patch release on the same line, or one minor version (for example 2.4.8 to 2.4.9) | Two minor versions (2.4.7 to 2.4.9) | Three or more (2.4.6 or older to 2.4.9), or Magento 1 |
| Third-party extensions | Under 15, all from active vendors with releases for the target version | 15 to 40, a few needing replacement | 40 or more, several abandoned or heavily patched |
| Custom code | A few small modules using plugins, observers and service contracts | Several modules, some overriding core classes with preferences | Core files edited directly, large custom checkout or pricing logic |
| Theme | Hyvä or a lightly customized Luma child theme | Custom Luma-based theme with many template overrides | Heavily overridden theme, old JavaScript, or a theme switch during the upgrade |
| Hosting stack | Already on the target PHP, database, search and cache versions | One or two services to upgrade | New PHP, database, search engine and cache at once, or a host change |
The extension counts are rules of thumb, not thresholds. Ten poorly written extensions can cost more than forty clean ones.
Each driver in more detail
Version gap
Each minor version brings new PHP requirements and dependency changes. Going from 2.4.6 to 2.4.9, for example, moves PHP from 8.2 to 8.5, replaces Elasticsearch with OpenSearch 3, swaps Redis for Valkey 9 and changes the supported databases. Each of those is a piece of work. If your version is past standard support, read our guide to Magento 2.4.6 end of support to see how the timing affects your options.
Third-party extensions
Extensions are usually the biggest variable. For each one, you either install a compatible release from the vendor, replace it with an alternative, or fix it yourself. Abandoned extensions are the expensive case. An upgrade is also a good time to remove modules you no longer use, which lowers the cost of every future upgrade.
Custom code
Custom modules that follow Adobe's extension patterns (plugins, observers, service contracts) usually need small changes. Code that edits core files, overrides whole classes or relies on libraries Adobe has since removed needs more work. Adobe Commerce customers can run Adobe's Upgrade Compatibility Tool, which reports critical issues, errors and warnings against the target version. Magento Open Source stores rely on static analysis and manual review instead, since the tool requires an Adobe Commerce licence.
Theme
Luma-based themes with many template overrides tend to need the most frontend fixes, because each overridden file may differ from the new core version. Hyvä themes have their own release cycle, so the theme vendor's compatibility matters too.
Hosting stack
If your host can provide the new PHP, database, OpenSearch and Valkey versions as a managed change, this cost is small. If you need a new server build or a host move, it grows. Check Adobe's system requirements table for your target version before you get quotes.
Costs that are easy to forget
- Extension licence renewals: some vendors charge for updates after the first year.
- A staging environment: you need one that matches production, which may mean extra hosting for a few months.
- Internal time: your team has to test orders, check content and sign off.
- Integration partners: ERP, PIM or marketplace connectors may need their own updates.
- Aftercare: a few weeks of monitoring and quick fixes after go-live.
- Deferred upgrades: skipping versions makes the next upgrade bigger. Adobe's guidance is to upgrade every patch release cycle for exactly this reason.
How to keep upgrade costs down
- Upgrade regularly. Small, frequent upgrades cost less in total than one big jump every few years.
- Prune extensions. Every module you remove is one less thing to update, test and pay for.
- Keep custom code clean. No core edits, and use plugins and observers over preferences where possible.
- Automate tests. Even a small automated test suite for checkout and key journeys cuts regression time.
- Audit before you quote. A short audit turns an open-ended estimate into a fixed scope.
Our Magento upgrade checklist shows every task in a typical upgrade, which also helps you compare quotes line by line.
FAQ
Is upgrading cheaper than replatforming?
Usually, if Magento still fits your business, because you keep your data model, URLs, integrations and customizations. Replatforming means rebuilding all of those. Compare both on the drivers above rather than on headline estimates.
Why do upgrade quotes vary so much?
Quotes made without an audit have to guess at extensions, custom code and testing scope. Some quotes also leave out testing or aftercare. Ask each provider what is included and what assumptions they made.
Do security patches cost as much as a version upgrade?
No. A security patch release on your current line is a much smaller change than a minor version upgrade, though it still needs testing.
Getting a fixed quote
The fastest way to an accurate number is an audit of the five drivers above against your target version. Mistri's Magento upgrade services begin with that audit, and the fixed quote follows from what it finds.
Sources
Adobe Commerce upgrade guide overview (Adobe Experience League); Upgrade Compatibility Tool overview (Adobe Experience League); System requirements (Adobe Experience League).
