
Upgrade to Adobe Commerce 2.4.9 without breaking your store
Older 2.4.x releases are losing security support. We upgrade on a staging copy first and release with a rollback plan.
Get an upgrade estimateWhat’s includedFree · No obligation · Reply within one business day
- From 2.4.6, 2.4.7 or 2.4.8
- PHP 8.5 and MySQL 8.4 changes included
- Fixed price after a free audit
Stores we have built and run
A Magento upgrade service moves your store from an older 2.4.x release to a supported one, today Adobe Commerce 2.4.9, without breaking extensions, integrations or checkout. The work covers the server stack (PHP 8.5, MySQL 8.4 or MariaDB 12.3, OpenSearch 3, Valkey 9), every extension and your custom code, tested on staging first.
Where your version stands
Adobe’s published support dates (checked November 2026). Full details in the release tracker.
Until May 31, 2029
Until May 31, 2028
Until May 31, 2027
Until August 31, 2027
Until May 31, 2027
Until May 31, 2027
Why it matters
What staying current protects
Indicative timelines
| Starting version | Path | Timeline* |
|---|---|---|
| 2.4.8 | Direct | 1–2 weeks |
| 2.4.7 | Direct + server | 2–3 weeks |
| 2.4.6 or older 2.4.x | Via 2.4.8 | 3–5 weeks |
| 2.3.x or older | Code rebuild | After audit |
*Estimates for a typical store, confirmed with a fixed price after the audit.
How it works
What’s included
What 2.4.9 changes
- PHP 8.5 (8.2 to 8.4 not listed for 2.4.9)
- MySQL 8.4 or MariaDB 12.3
- OpenSearch 3 and Valkey 9
- Extensions may need new versions
Dates and full requirements for every release: Magento release tracker.
Is this right for you?
- Your store runs 2.4.4, 2.4.5 or 2.4.6, which are past standard support
- You are on 2.4.7 and standard support ends on May 31, 2027
- Your hosting cannot run PHP 8.5 or the newer database yet
- Previous upgrades broke extensions or took too long
- You are on Magento 1 or 2.3: that is closer to a rebuild, see migrations
- You plan to leave Magento within a year: compare the cost first
- Upgrade audit with extension compatibility list
- Upgraded and tested staging store
- Release plan with rollback
- Post-launch support window
How it works
You see the findings, the scope and the price before any code changes.
AuditWe review code, extensions, hosting and speed.
Plan & priceA fixed scope and price, or a retainer.
Build on stagingTested on a copy of your store, never live.
Launch & supportA planned release, rollback ready, then monitoring.
For your technical team
How we build it
The stack, standards and handover your developers can expect.
- PHP 8.5 and Composer 2.10
- MySQL 8.4 or MariaDB 12.3
- OpenSearch 3, Valkey 9, RabbitMQ 4.3, Varnish 8
- Every extension checked against 2.4.9 and PHP 8.5
- Custom code updated and statically analysed
- composer.json and applied patches cleaned up
- Full rehearsal on a staging copy
- Code and database backups before go-live
- A tested rollback path
Questions before you book
Frequently asked questions
Will my store go offline during the upgrade?
All work happens on staging. The live switch is a short planned maintenance window, usually minutes.
Do I need new hosting for 2.4.9?
Often the server needs PHP 8.5 and MySQL 8.4 or MariaDB 12.3. We check this in the audit and can handle the server changes.
Can I go straight from 2.4.6 to 2.4.9?
Stores on 2.4.6 or older usually upgrade in two steps, through 2.4.8, so each step can be tested.
How much does an upgrade cost?
It depends mainly on the number of extensions and the amount of custom code. After the free audit you get a fixed price before work starts.
Which Magento versions are still supported?
See our release tracker for current dates. As of November 2026, 2.4.7, 2.4.8 and 2.4.9 are in standard support; 2.4.6 is in extended support.
What happens if I do not upgrade?
Unsupported versions stop receiving regular security patches, and payment providers, extensions and hosting gradually drop support for old PHP and database versions.
What do you need from our team during the upgrade?
Access to the code repository and a staging server, your extension list, and someone to test key business flows on staging before release. We only ask for the access the upgrade needs.
What if an extension vendor has no 2.4.9 version?
We find a maintained alternative, patch the module, or replace it with a small custom module, and agree the choice with you before release.
Related services
Which version are you on?
Tell us your current version and number of extensions for a quick estimate.
Free · No obligation · Reply within one business day




