Adobe Commerce 2.4.9 upgrade planning guide

Updated Adobe Commerce 2.4.9 planning guide covering current PHP, OpenSearch, Valkey, message-broker, API and extension-readiness considerations.

Reviewed 13 October 2026. Adobe's official Adobe Commerce 2.4.9 release notes were last updated 12 August 2026 when this article was reviewed. The notes are the source of truth for the version-specific statements below; store-specific compatibility still depends on installed extensions, custom code and infrastructure.

Platform changes that affect upgrade planning

Adobe documents PHP 8.5 as fully supported for 2.4.9 and PHP 8.4 as an upgrade-only path rather than the recommended production runtime. PHP 8.2 and 8.3 are no longer supported. Composer 2.x compatibility includes Composer 2.9.

The release also adds support for OpenSearch 3.x, MariaDB 11.8/12.x and Valkey 9.x. Adobe lists RabbitMQ 4.2 as a short-term compatibility path and identifies Apache ActiveMQ Artemis as the long-term message-broker direction. Those infrastructure changes make an upgrade more than a Composer version bump.

API, checkout and admin changes

The release includes REST product-gallery inheritance changes, new and expanded GraphQL capabilities, additional CAPTCHA/reCAPTCHA enforcement paths, admin improvements and Braintree updates. Stores with custom storefronts or integrations should compare their own API and checkout usage with the official release notes rather than assume the changes are irrelevant.

Framework and extension readiness

Adobe documents significant dependency changes including Symfony Cache replacing Zend_Cache, HugeRTE replacing TinyMCE, native MVC replacing Laminas MVC and Symfony 7.4 LTS support. Custom modules and third-party extensions that depend on old framework behaviour should therefore be part of pre-upgrade compatibility review.

Upgrade checklist

  1. Record the current Commerce/Magento version, PHP, database, search, cache and queue services.
  2. Inventory Composer packages, custom modules, extensions and theme/storefront dependencies.
  3. Identify payment, shipping, tax, ERP/PIM/CRM and API integrations that must be regression tested.
  4. Build and resolve the upgrade in a non-production environment with representative configuration/data.
  5. Test admin, indexing, search, customer accounts, cart, checkout, payment, shipping, emails, cron, imports/exports and APIs relevant to the store.
  6. Confirm deployment, cache/index steps, monitoring and rollback expectations before production release.

What this article does not claim

It does not claim that every extension supports 2.4.9, that every store should upgrade immediately or that the infrastructure combinations listed by Adobe are interchangeable without testing. Recheck the official release notes and system requirements when planning a real upgrade because Adobe can update guidance after this review date.

Discuss upgrade readiness

Send the current Commerce/Magento version, infrastructure stack, important extensions and integrations if you need a store-specific upgrade assessment.

Contact eComHut

Frequently asked questions

Is PHP 8.4 the recommended production runtime for Adobe Commerce 2.4.9?

No. In the August 2026 release notes Adobe describes PHP 8.5 as fully supported and PHP 8.4 as allowed for upgrade purposes only.

Does 2.4.9 support OpenSearch 3?

Yes. Adobe states that 2.4.9 is compatible with OpenSearch 3.x while retaining OpenSearch 2.x compatibility.

Should an upgrade be tested outside production?

Yes. Custom modules, extensions, integrations and checkout behaviour need representative testing before a production release.