Magento 2.4.9 upgrade: what breaks, and a 10-step checklist

With 2.4.6 out of standard support since 11 August 2026, the next question is where to go. 2.4.9 is the newest release line, and it is a bigger step than a patch: almost every service under the store changes version, and some extensions need updates before they work at all. Here is what changes, what tends to break, and the order we would do it in.

What 2.4.9 needs on the server

Adobe’s system requirements for 2.4.9 on your own hosting:

• PHP 8.5. PHP 8.4 is allowed only to get through the upgrade, not for production, and PHP 8.2 and 8.3 are no longer supported.
• MySQL 8.4, or MariaDB 12.3. Adobe asks you to upgrade MariaDB to 12.3 before you upgrade to 2.4.9.
• OpenSearch 3. Elasticsearch is not on the 2.4.9 list.
• Valkey 9 for cache and sessions. Adobe added Valkey because Redis 7.2 reached its end of support and changed its licence.
• Varnish 8, RabbitMQ 4.3 and Composer 2.10.

So the hosting matters as much as the code. Before you plan the upgrade, check that your host offers these versions, or plan the move to one that does.

What breaks: the changes that hit extensions

Adobe lists these as the main backward-incompatible changes in 2.4.9:

• Zend_Cache is replaced with symfony/cache for the default cache and the full-page cache. Extensions that use Zend_Cache classes have to move to the Symfony cache APIs.
• Symfony 7.4 LTS: custom classes that extend Symfony core classes need updated type declarations and method signatures.
• GraphQL limits: at most ten aliases per request, and a configurable maximum query length. Headless and PWA front ends that send large queries need a test.
• New Relic moves from its REST API v2 to NerdGraph.
• Admin passwords get a configurable minimum length, and admins can set up more than one two-factor method.

The usual pattern: Magento itself upgrades cleanly, and the trouble sits in third-party modules and custom code written for older versions. Before you start, list every module and check that its vendor supports 2.4.9 and PHP 8.5.

What we ran into on a live 2.4.9 store

Our demo store, Neaterie, runs Magento 2.4.9 with Hyvä 1.5 on PHP 8.5 in production mode, on our own server. Three things are worth knowing before you switch:

• PHP 8.5 deprecations stop the page in developer mode. In one of our own modules, imagedestroy() is now deprecated, and Magento’s developer mode turns the deprecation notice into an exception. Click through your custom features in developer mode on staging before production sees them.
• OpenSearch wants memory. On a small server it took about 1.7 GB of RAM until we capped its heap. Size the server for the search service, not only for PHP and the database.
• Keep the search index on a persistent volume. When we recreated the OpenSearch container without one, the index was gone and every category showed “0 products” until a reindex. A small watchdog now counts the indexed products and rebuilds the index when the number drops.

A 10-step upgrade checklist

1. 01Back up code, database and media, and test that you can restore them.
2. 02Build a staging copy of the live store on the new stack: PHP 8.5, MySQL 8.4 or MariaDB 12.3, OpenSearch 3 and Valkey 9.
3. 03List every extension and custom module. Check each vendor’s support for 2.4.9 and PHP 8.5, and plan a replacement for any that are abandoned.
4. 04Search your code for Zend_Cache and for classes that extend Symfony core classes, and update them.
5. 05On MariaDB, upgrade the database to 12.3 first, as Adobe asks.
6. 06Run the upgrade on staging with Composer 2.10, then setup:upgrade, compile and deploy the static content.
7. 07Switch staging to developer mode and click through the shop, the checkout and the admin to bring deprecations to the surface.
8. 08Test everything that earns money: search, category pages, cart, checkout, payment and shipping methods, order emails, and any headless or GraphQL front end.
9. 09Reindex, warm the full-page cache and compare page speed with the old store.
10. 10Go live in a quiet hour with the backup ready, and watch the logs and the orders for the first days.

Magento upgrades cleanly. The surprises live in the modules around it.

2.4.8 or 2.4.9?

If your extensions are not ready for PHP 8.5 yet, 2.4.8 is the smaller step: it runs on PHP 8.3 or 8.4, MySQL 8.4 and OpenSearch 3, and you can move to 2.4.9 once your modules catch up. A store that is already on 2.4.8 should plan 2.4.9 when its vendors support it.

Where to start

Start with the list of modules: it decides how big the job is. Our free audit checks your version, modules, hosting stack and checkout, and gives you the upgrade steps in order, with an estimate.

Sources: Adobe Commerce system requirements and the 2.4.9 release notes on Experience League, and Adobe’s backward-incompatible changes highlights on developer.adobe.com, checked on 27 October 2026. Requirements change with each patch release, so check them again before you plan.