Magento Open Source upgrade proposal: 2.4.8-p5, your options

Your support runs until 31 May 2028

Your store runs Magento Open Source 2.4.8-p5. Adobe's standard support for 2.4.8 runs until 31 May 2028. Until then Adobe keeps releasing security patches for it, so your store stays patched as long as those patches keep being applied.

This means the upgrade is not urgent. You have time to choose the path that costs you least, and we recommend you use it.

Adobe now ships one full Magento release a year, in May. The next one, 2.4.10, is already in early testing: its first preview (2.4.10-alpha1) came out in October 2026.

Our recommendation

Option A (recommended): wait for 2.4.10 and upgrade once, in the second half of 2027.

• One upgrade instead of two. You skip the 2.4.9 cycle and the cost that comes with it.
• A later support end date. 2.4.10 is a newer release than 2.4.9, so its support runs later than 2.4.9's 31 May 2029.
• A settled release. We plan the work after 2.4.10 has had its first patch, so early problems are already fixed.
• Done before the deadline. The target is release before the December 2027 trading freeze, more than 5 months before 31 May 2028.

Option B: move to 2.4.9 sooner.

• One more year of support. 2.4.9 is supported to 31 May 2029, one year past 2.4.8.
• The big framework change, done early. 2.4.9 carries the largest internal change in the 2.4 line. Doing it now spreads that work ahead of 2.4.10.
• Only worth it alongside other planned work. If you already plan changes to the store, bundling them with this upgrade can make sense. On its own, option B means two upgrades where option A needs one.

Either way: keep the monthly security patches applied on 2.4.8 until the upgrade is live. We do this as part of your existing support arrangement.

What the upgrade 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, and 2.4.10 builds on the same changes.

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.

• The upgrade moves one minor release, from 2.4.8 to 2.4.9.
• PHP moves from your current 8.x version to 8.5.
• The database moves to MariaDB 12.3, and the Valkey cache moves from 8.1 to 9.
• All three framework replacements apply to your store.
• Your store has 21 extensions and little custom code.

For 2.4.9, Adobe's current server requirements are PHP 8.5, MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9, RabbitMQ 4.3, Varnish 8 and Composer 2.10. Adobe has not yet published the requirements for 2.4.10.

Estimate

We are not quoting hours or a price in this proposal.

• Option A: we can estimate a 2.4.10 upgrade only after Adobe publishes 2.4.10's requirements. We send you that estimate then.
• Option B: we are reviewing the hours for your 21 extensions and the server work before we quote. If you choose option B, we send you the reviewed estimate, with a 15% contingency line, before any work starts.

Assumptions

• We start a code scan in discovery to check how much of your custom code uses the replaced framework parts.
• 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.
• Monthly security patches stay applied on 2.4.8 until the upgrade is live.

Not included

• Licence or renewal fees for third-party extensions.
• Replacing an extension that has no version compatible with the target release. If discovery finds one, we quote the replacement separately.
• Content fixes caused by the change of admin editor, beyond the checks in testing.
• New features. If you want any, we quote them separately.

Timeline for option A (recommended)

If 2.4.10 is late or brings new breaking changes, we move you to 2.4.9 instead, well before 31 May 2028. If you choose option B, we agree its timing with you and keep it clear of the December and January trading freeze.

Risks and how we manage them

Each of these steps reduces exposure. None of them removes risk completely.

Next step

A 15-30 minute call to choose option A or option B. If you choose option A, we confirm the patch routine and come back to you when 2.4.10 is released. If you choose option B, we send you the reviewed estimate.

Appendix A: extension list

Your store has 21 third-party extensions. Before we quote either option, we list each one with its current version and the target version that supports the release you choose. Any extension with no compatible version is marked, with the replacement options.