Upgrading to Magento 2.4.9 is mostly a server project: the new release needs PHP 8.5, OpenSearch 3, Valkey 9 and a newer database before the Magento code itself can move. Adobe released 2.4.9 on May 12, 2026, and supports it until May 31, 2029. This checklist covers what to verify before, during and after the upgrade, in the order we work through it on client stores.
Should you upgrade now?
| You are on | Regular support ends | Recommendation |
|---|---|---|
| 2.4.6 or older | Ended (2.4.6 on August 11, 2026) | Upgrade now; Open Source no longer gets regular fixes. |
| 2.4.7 | May 31, 2027 | Plan the move to 2.4.9 within the next few months. |
| 2.4.8 | May 31, 2028 | Stay current on security releases; upgrade when your extensions support 2.4.9. |
Not sure which version you run? bin/magento --version tells you, and our free WhizzyScan also checks it against Adobe's security bulletins.
2.4.9 system requirements
These are the versions Adobe tested for on-premises installs. Adobe supports only the listed combinations.
| Software | 2.4.9 | 2.4.8 (latest security release) |
|---|---|---|
| PHP | 8.5 | 8.4, 8.3 |
| MySQL | 8.4 | 8.4 |
| MariaDB | 12.3 | 11.4, 11.8 |
| Search | OpenSearch 3 | OpenSearch 3 (Elasticsearch 8 also listed) |
| Cache | Valkey 9 | Valkey 8.1 |
| RabbitMQ | 4.3 | 4.3 |
| Varnish | 8 | 8 |
| Composer | 2.10 | 2.10 |
| nginx | 1.30 | 1.30 |
Source: Adobe Commerce system requirements, last updated September 18, 2026. Check it again before you start, because Adobe updates it with each security release.
Before the upgrade
1. Take inventory
- Current Magento version and the latest security release you applied.
- PHP, database, search engine, cache and message queue versions on the server.
- Every third-party module (
bin/magento module:status) and every custom module inapp/code. - Your theme: Luma-based, Hyvä, or custom.
2. Check every extension
For each module, find out whether the vendor has a 2.4.9 and PHP 8.5 compatible version. Group them into: update available, needs a patch from us, and abandoned, replace or remove. Abandoned extensions are the usual reason upgrades slip.
3. Plan the server changes in the right order
You cannot jump everything at once. A safe order:
- Move from Redis to Valkey for cache and sessions if you have not already; current Magento releases no longer list Redis as supported.
- Move search to OpenSearch 3 and reindex.
- Upgrade the database to a supported version and test a full backup and restore.
- Install PHP 8.5 next to your current PHP, so you can switch per site.
4. Expect editor changes in the admin
Release coverage of 2.4.9 reports that the default WYSIWYG editor moves from TinyMCE to HugeRTE, an open-source fork. Custom admin modules that extend the editor need testing.
5. Build a staging copy
Copy production code, database and media to a staging server that matches the target stack. Every step from here runs on staging first.
During the upgrade (on staging)
composer require magento/product-community-edition=2.4.9 --no-update
composer update
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy
bin/magento indexer:reindex
bin/magento cache:flushFor Adobe Commerce, use magento/product-enterprise-edition. Fix compile errors one extension at a time, and record every change so you can repeat it exactly on production.
Test what earns money
- Search, layered navigation, product and category pages.
- Cart, every shipping method, every payment method, coupon codes.
- Order emails, invoices, the admin order grid, ERP or marketplace syncs.
- Cron jobs and message queue consumers.
- Core Web Vitals on the main templates, compared with production.
Release day
- Freeze content changes in the admin.
- Take a database and file snapshot.
- Enable maintenance mode, deploy, run
setup:upgrade, compile and deploy static content. - Switch to production mode if you are not already in it.
- Disable maintenance mode and run the test list again on live.
- Keep the snapshot until you are sure; rolling back is a restore, not a guess.
After the upgrade: protect your SEO
- Regenerate the sitemap and confirm it is generated for the live store view.
- Compare a crawl of titles, canonicals, status codes and robots tags with the pre-upgrade crawl.
- Check page caching: one new block declared
cacheable="false"makes whole pages uncacheable. - Watch Search Console coverage and Core Web Vitals for two weeks.
Our technical guide to Magento SEO has the full list.
Frequently asked questions
How long does an upgrade to 2.4.9 take?
The Magento part can take a few days. The server changes and extension work around it decide the real timeline, so the inventory step is where you learn how long yours will take.
Can I skip versions, for example from 2.4.6 to 2.4.9?
Yes, Composer can take you straight to 2.4.9. The work is the same either way: all server requirements and extensions must be ready for the target version.
Do I need to upgrade if I am on 2.4.8?
Not urgently. 2.4.8 is supported until May 31, 2028. Keep applying its security releases and plan the move when your extensions are ready.
Can you do the upgrade for us?
Yes. We run the compatibility audit, rehearse on staging and release with a rollback ready. See our Magento upgrade service.