Your support ends on 31 May 2027
Your store runs Magento Open Source 2.4.7-p9. Adobe's standard support for 2.4.7 ends on 31 May 2027. After that date Adobe no longer commits to security patches or fixes for Magento Open Source 2.4.7, so any weakness found later may stay open on your store.
To release the upgrade safely before that date, we need your approval by 30 November 2026. That lets us plan in December, build in January and February, and release by April 2027, with time to spare before the deadline.
Adobe does offer one extra year of extended support on 2.4.7, to May 2028. That year applies to licensed Adobe Commerce only. It does not apply to Magento Open Source, so 31 May 2027 is the date that counts for you.
Why upgrade now
- No gap in support. You stay on patched software the whole way through, which reduces your security and PCI exposure.
- The longest runway available. 2.4.9 is supported to 31 May 2029. Moving to 2.4.8 instead would buy only one more year, and then you would face this project again.
- Planned, not rushed. We schedule the work around your trading peaks. Leaving it close to the deadline means competing for Magento developers when demand for them is highest.
- Your server stack moves too. PHP, the database, search and cache all move onto supported versions at the same time. Magento 2.4.7 supports PHP 8.2 and 8.3 only, so the store cannot move to a newer PHP without this upgrade.
What 2.4.9 involves for your store
2.4.9 is the largest change to Magento's internal framework in the 2.4 line. It adds few new features for merchants, and we do not sell it on new features or speed. The reason to move is support.
Three internal parts of Magento are replaced in 2.4.9:
- the Laminas framework, replaced by Magento's own framework
- the Zend cache, replaced by Symfony Cache
- the TinyMCE admin editor, replaced by HugeRTE
Extensions and custom code that use the first two directly need updating. Because of this, extension upgrades are the largest part of the work.
Size of the job: moderate to heavy.
- The upgrade moves two minor releases, from 2.4.7 to 2.4.9.
- PHP moves to version 8.5.
- All three framework replacements apply to your store.
- Your store has 22 extensions and little custom code.
The server stack moves to Adobe's current requirements for 2.4.9: PHP 8.5, MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9, RabbitMQ 4.3, Varnish 8 and Composer 2.10.
Estimate
| Workstream | Hours |
|---|---|
| Planning and technical discovery | 12 |
| Magento core upgrade | 20 |
| Server platform upgrade | 22 |
| Custom code compatibility | 6 |
| Theme compatibility | 10 |
| Third-party extension upgrades (22 extensions) | 88 |
| Functional and regression testing, including admin content editing | 16 |
| Mobile and responsive testing | 4 |
| Speed check after release | 3 |
| User acceptance testing support | 6 |
| Production deployment | 4 |
| Hypercare and monitoring after release | 5 |
| Project management and coordination | 20 |
| Subtotal | 216 |
| Contingency (15%) | 32 |
| Total | 248 |
Assumptions
- We start a code scan in discovery to check how much of your custom code uses the replaced framework parts. Custom code and testing hours may rise after that scan. If they do, we tell you before we do the work.
- The April 2027 release assumes approval in November 2026 and the build in January and February 2027.
- We make no changes to your live store during the December and January trading freeze.
- The upgrade keeps your store's current features. It adds no new features.
Not included
- Licence or renewal fees for third-party extensions.
- Replacing an extension that has no version compatible with 2.4.9. If discovery finds one, we quote the replacement separately as a variation.
- Content fixes caused by the change of admin editor, beyond the checks in testing.
- New features. If discovery finds any you want, we quote them separately.
Timeline
| When | What happens |
|---|---|
| By 30 November 2026 | You approve the proposal |
| December 2026 | Planning, technical discovery and the code scan. No live changes. |
| January to February 2027 | Core, server, extension, theme and custom code upgrade on a separate copy of your store |
| March 2027 | Testing and user acceptance testing with your team |
| April 2027 | Release to your live store, then hypercare and monitoring |
| 31 May 2027 | Adobe support for 2.4.7 ends. You are already on 2.4.9. |
Risks and how we manage them
| Risk | Likelihood | Impact | How we manage it |
|---|---|---|---|
| Approval slips and the release misses 31 May 2027 | Medium | High | Approve by 30 November 2026 to keep the April release |
| Custom code needs more work than expected | Medium | Medium | Code scan in discovery, and the contingency line |
| An extension has no 2.4.9 version | Low | Medium | Discovery flags it early. A replacement is quoted as a variation. |
| Testing misses a problem | Medium | Medium | A sign-off checklist for your team's user acceptance testing |
| Admin content displays differently after the editor change | Low | Low | Content-editing checks in testing and user acceptance testing |
The upgrade reduces your exposure to known security weaknesses. It cannot remove all risk, and the benefit also depends on how the store and its server are configured.
Next steps
- Read the proposal and send us any questions.
- Approve by 30 November 2026.
- We book discovery for December and send you the extension list with each target version.
Appendix A: extension list
Your store has 22 third-party extensions. In discovery we list each one with its current version and the target version that supports 2.4.9. Any extension with no compatible version is marked, with the replacement options.
| Extension | Vendor | Current version | Target version for 2.4.9 | Notes |
|---|---|---|---|---|
| To be completed in discovery |