What an Adobe Commerce or Magento upgrade costs, and how to plan one
Ask AI about this article
On a planning call this year, someone at a B2B merchant we work with asked the question every upgrade conversation comes back to: "how much that's going to cost, and how much time is it?"
Fair question. Here is the honest short answer. The cost of an Adobe Commerce or Magento upgrade is almost never the update itself. That part is a Composer change and a bin/magento setup:upgrade. The cost is everything attached to the store: third-party extensions, your own custom code, the PHP and database versions underneath, and the integrations that talk to it, your ERP connector above all. Nobody can price those honestly until they have tried the upgrade on a copy of your store.
So the real answer is a sequence. Dry run first, then a number, then a planned window, and the store stays patched the whole time. This post walks through each step. It applies whether you run Adobe Commerce, Magento Open Source or Mage-OS. If you are still deciding whether you need to upgrade at all, start with what happens to your Magento store after end of support.
How much does an Adobe Commerce upgrade cost?
We don't quote an upgrade before a dry run, and we'd be a little wary of anyone who does. Two stores on the same version can be very different projects. Six things set the price, and you can rate your own store against each one today:
| Cost driver | Points to a smaller upgrade | Points to a bigger one |
|---|---|---|
| How far behind you are | One release line, say 2.4.7 to 2.4.8 | Two or more lines, with several PHP versions to cross |
| Third-party extensions | A short list, all maintained, licenses current | A long list, some abandoned, some licenses lapsed |
| Your own custom code | Hooks in through Magento's plugins and events | Replaces core classes, or edits files in vendor/ |
| Integrations | Your ERP, tax and payment vendors support the target version | A connector stuck on an old version, or a homegrown sync with no tests |
| Hosting | Your host already offers the PHP, database and search versions you need | The server has to move first |
| Testing | A written list of what to check, and a staging site that matches production | Testing starts after go-live |
Mostly in the right-hand column? That is still a solvable project. It needs more weeks, and it needs them on a calendar instead of in a panic.
Why does a Magento upgrade cost more than the update itself?
Because Adobe tests the core, and nobody tests your store but you. Every piece you have added has to be checked against the new version, and some of it has to change.
Extensions
Every third-party module needs a release that works on your target version. Some vendors have one ready on day one. Some make you renew a license before you can download it, and we have seen lapsed licenses block a dry run outright. Some vendors have quietly stopped. In our experience the Magento update is the easy part. "Is this module still supported?" is where the time goes, so ask it months early.
Your custom code
Custom code that hooks in through plugins and events usually survives an upgrade. Code that replaces core classes often doesn't. Releases also swap libraries underneath you. In 2.4.9, Adobe replaced Zend_Cache with Symfony Cache, swapped Laminas MVC for its own implementation, moved to Symfony 7.4, and changed the admin editor from TinyMCE to HugeRTE. Any custom code that leans on those needs work.
The stack under the store
Each release line runs on specific PHP and database versions, so your hosting moves with the upgrade. Here is the picture from Adobe's system requirements (latest patch of each line) and its lifecycle policy, as of November 2026:
| Release | PHP | MySQL 8.4 | Standard support ends |
|---|---|---|---|
| 2.4.6 | 8.1, 8.2 | No | August 11, 2026 (Adobe Commerce extended support to August 31, 2027) |
| 2.4.7 | 8.2, 8.3 | No | May 31, 2027 |
| 2.4.8 | 8.3, 8.4 | Yes | May 31, 2028 |
| 2.4.9 | 8.5 (8.4 only while upgrading) | Yes | May 31, 2029 |
Read it like a route map. Going from 2.4.6 to 2.4.9 means PHP 8.2 to 8.5. For a lot of stores it means a database change too. MySQL 8.0 reached end of support on April 30, 2026, and Adobe doesn't support MySQL 8.4 before 2.4.8. That is why your hosting company belongs in the plan from the first week, not the last.
Integrations, and the ERP connector most of all
For a distributor or manufacturer, this is the line that decides the timeline. Before you pick a target version, ask every vendor whose code runs inside your store which Magento versions they support. Start with the ERP connector. Whether your sync runs to Epicor P21, NetSuite, Microsoft Dynamics or Infor, "does your connector support 2.4.8?" is a one-line email that can move your whole plan.
Integrations you built yourself need the same check. 2.4.9 made the web API stricter: bulk endpoints now return an error when the request body isn't an array, and malformed requests get a clear "400 Bad Request". A sync that has been getting away with a sloppy payload finds out on upgrade day, unless it finds out on staging first. If you have never written down every system that touches your store, our ERP integration readiness checklist is a quick way to do it.
Testing, and the cleanup after launch
Look back through our own upgrade tickets and a pattern shows up. More than once, the upgrade ticket has been followed by a second one for post-upgrade issues. On one store, that cleanup covered a missing chat widget, a shipping-rate problem and a blog that stopped rendering. Two third-party extensions also had to be rolled back to earlier releases. That is normal. It is also the line most budgets forget. Test the ways orders come in and the data going out to your ERP, not just the pages, and leave room after launch for a cleanup pass.
What does a dry run tell you?
A dry run is the upgrade done for real on a copy of your store, with nobody depending on it. You run the update and write down everything that blocks it. Then you fix just enough to get it running, and work through the store and its integrations to see what breaks. What comes out is a list: what blocked the update, what broke after it, and what to do about each one.
That list is the estimate. It turns "it depends" into work you can price, schedule and argue about. Have two things ready before you start: current licenses for your paid extensions, so you can download compatible versions, and a staging copy that matches production, data included.
How do you phase an upgrade so it never becomes a panic project?
Spread the work across the year, so the upgrade window itself stays short. Here is the order we would use:
- Take inventory. Any time, and it takes an afternoon. Write down your version and edition (
bin/magento --version), the third-party packages incomposer.json, your custom modules, every integration and who owns it, and your PHP, database and search versions. Our Adobe Commerce EOL checker shows your support dates. - Run the dry run. Do it a quarter or more before your deadline, so the estimate arrives while you still have choices.
- Do the pre-work on your current version. Update the extensions that already have releases for both versions, replace the dead ones, and move the parts of the stack your current version already supports. On 2.4.7, for example, you can move to PHP 8.3 now, because 2.4.8 runs on it too. Everything you finish here comes out of the upgrade window.
- Book a quiet window. No feature launches, no new integration, no peak season. A merchant we work with put it well: "we need to sort of actually schedule in kind of a pause." If an ERP integration is mid-build, finish it first. That gives you a known-good result to test the upgraded store against. If it hasn't started, upgrade first, so it only gets built once. Either way, make one big change at a time, so when something breaks you know which change did it.
- Go live, then clean up. Plan the cleanup pass before launch, not after.
- Ship it, or redo the dry run. An upgrade finished on a dev server and left there for months goes stale. Patches land, extensions move, and the testing you did no longer matches what is live. If the window slips by a season, run the dry run again.
Then put the next one on the calendar. Adobe gives each release line three years of standard support from its release date. A store that moves to a new line soon after it ships has most of those three years to plan the next move calmly.
How do you keep the store secure until the upgrade?
Patch, every month. Patching is the bridge between today and the upgrade window.
- Apply every patch your version gets. On Adobe Commerce 2.4.6, extended support runs to August 31, 2027, then a security-only period runs to May 31, 2028. Adobe's own advice on that last stretch: "Treat the security-only period as migration time, not as a long-term support tier." Extended support is an Adobe Commerce benefit. Magento Open Source stores on 2.4.6 don't get it.
- Backport what Adobe doesn't ship. When a fix lands only on newer lines, it can often be carried back by hand. One store we look after is still on 2.4.6, and it carries Adobe's security fixes through October 2026, the last two backported by hand from 2.4.7. We wrote up how that works in keeping Magento 2.4.6 patched while you plan.
- Keep patches as files, not edits. Ours live in a folder in the repository and get applied on every
composer install, so the upgrade can drop them cleanly when it lands. Patches typed straight intovendor/vanish on the next deploy, or get in the upgrade's way. - Watch the clocks patching can't stop. PHP 8.2, the newest PHP that 2.4.6 runs on, reaches end of security support on December 31, 2026. A patched Magento on an unsupported PHP still leaves a gap.
Patching buys time. It doesn't buy a new version. Planning the upgrade, and keeping the store patched until it happens, is the heart of our Adobe Commerce support and maintenance work.
Should you upgrade in place, move to Mage-OS or Magento Open Source, or replatform?
There are four honest paths:
| Path | Fits when | What you sign up for |
|---|---|---|
| Upgrade in place | The store still does what the business needs | The cost drivers above, and nothing else |
| Move to Mage-OS | You are on Magento Open Source and want to stay open source | The same upgrade work to reach a 2.4.9 base, on a distribution the community maintains |
| Adobe Commerce to Magento Open Source | Your license pays for features nobody uses | Replacing or dropping the Commerce-only features, plus a data cleanup |
| Replatform | The business has outgrown the build, or shrunk away from it | A new build, new integrations and a migration, a bigger project than an upgrade nearly every time |
Four questions, asked in order, usually settle it:
- Does the store still do what the business needs? If yes, upgrade in place. That is usually the answer.
- Do your B2B rules live in Adobe Commerce features or in your ERP? Company accounts, shared catalogs and negotiable quotes are Adobe Commerce features, and they are a good reason to stay. If your pricing and availability come from the ERP, the license may be buying less than you think. Our guide to moving from Adobe Commerce to Magento Open Source walks through that test. Our Adobe Commerce vs Magento Open Source comparison covers the editions side by side.
- Are you on Magento Open Source and planning to stay there? Then look at Mage-OS. Its 3.x line is built on Magento Open Source 2.4.9. Getting there from an older version is the same upgrade work, but you land on a base with its own release cadence. The Mage-OS 3.0 release notes list PHP 8.3 to 8.5, with 8.4 recommended, which can matter if your host doesn't offer 8.5 yet.
- Would you rebuild most of it anyway? We do hear "should we just rebuild it?" on upgrade calls, and sometimes that is the right call. But a rebuild hangs on business decisions, like which features you still need and which programs you are keeping. Those have to be made before anyone can scope it. One destination is Adobe Commerce as a Cloud Service, Adobe's versionless SaaS edition, where Adobe applies the updates for you. Its compatibility promise covers customizations built on Adobe's API-first extensibility model, and it doesn't support Luma storefronts at all. A store with a Luma theme and a lot of custom PHP is rebuilding, so treat that as a replatform, not an upgrade. The replatforming playbook and the replatforming cost calculator help with that comparison.
Whichever path you pick, the work has a known shape: audit, update, fix, test, launch. That is the kind of Adobe Commerce development work we plan with merchants before the deadline, not after it.
What should you budget for every year?
An upgrade gets expensive when it is treated as a one-off. Budget it as a standing line instead:
- A release-line upgrade every couple of years. You don't need every release. Skipping one at a time is fine. Skipping three is how an upgrade turns into a migration.
- Monthly patches, applied and tested.
- Extension license renewals. Many paid extensions only give you updates while the license is active, and a lapsed one can stall the next dry run.
- Hosting moves for PHP, the database and search, timed with the upgrades. The upgrade is also a good moment to take a fresh look at the hosting bill.
- A test pass every time any of the above changes.
If you need a number to start the budget conversation, our Adobe Commerce platform page carries a planning range for yearly maintenance.
Want a head start before any of that? Open your store's composer.json and read the require block. Apart from Magento itself, every line there is something your upgrade has to carry along. How long is yours?