Adobe Commerce Upgrade Plan for Stores on PHP 8.2

Adobe Commerce stores on 2.4.6 and 2.4.7 have two dates to plan around. PHP 8.2 stops receiving security fixes on December 31, 2026. Version 2.4.7 leaves standard support on May 31, 2027.

Adobe Commerce 2.4.9 carries support to May 2029. It runs on PHP 8.5 in production, and PHP 8.4 is allowed for the upgrade itself.

Clearing the PHP date is an urgent task. While you can do it on 2.4.7 without changing versions, you cannot do the same on 2.4.6. Whether you should use the same window to move to 2.4.9 depends on your hosting model and your extension list. Your release calendar matters too, because Black Friday falls on November 27.

Who Is Affected?

• Adobe Commerce stores on 2.4.6 or 2.4.7 that still run PHP 8.2.
• Adobe Commerce on Cloud stores on any version from 2.4.4 to 2.4.9 that run services below Adobe’s minimum versions.
• Stores on 2.4.4 or 2.4.5, where PHP 8.1 reached end of life on December 31, 2025.
• Magento Open Source stores on PHP 8.2, which do not receive extended support.

2.4.8 stores should already be off PHP 8.2, so they face no PHP deadline this year. The Cloud dependency dates still apply to them.

On-premises stores are not subject to Adobe’s enforcement, but the PHP date applies to every store that runs 8.2.

Adobe Commerce Support Deadlines by Version

According to Adobe’s lifecycle policy, each release line gets three years of standard support from general availability. Standard support covers quality fixes and security patches, along with full support from Adobe.

Adobe gives Adobe Commerce customers on 2.4.6 and 2.4.7 one year of extended support at no extra cost. It covers quality and security patches for the core application.

Magento Open Source does not get it. Adobe also states that it does not fix third-party software, such as PHP and MySQL, that reaches end of life during a support period.

So May 31, 2027 changes the support tier for 2.4.7. It does not switch the store off. The date that stays fixed is the one PHP sets.

PHP 8.2 End of Life and PCI Compliance

According to php.net, PHP 8.2 receives security fixes until December 31, 2026. PHP 8.3 and 8.4 follow on December 31, 2027 and December 31, 2028. PHP 8.5, the version 2.4.9 runs on, is covered until December 31, 2029.

Adobe’s lifecycle policy flags the PCI exposure. It says compliance is at risk from the end of 2026 for 2.4.6 stacks on PHP 8.2, and it advises planning an upgrade or migration before year end.

Adobe also states that PCI compliance is the merchant’s responsibility to assess, and it recommends consulting your qualified security assessor. Its upgrade guide adds that merchants must be on the security patch to remain PCI compliant.

Your options depend on your version

• 2.4.7. Adobe lists PHP 8.3 for 2.4.7, so you can move to 8.3 and stay on 2.4.7. That buys one year, to December 31, 2027.
• 2.4.6. Adobe lists PHP 8.1 and 8.2 only. No supported PHP above 8.2 exists for 2.4.6, so clearing the date means upgrading Commerce.
• 2.4.8. Adobe lists PHP 8.3 and 8.4, so you should already be clear of the date.
• 2.4.9. PHP 8.2 and 8.3 are unsupported. According to Adobe’s release notes, PHP 8.5 is fully supported and PHP 8.4 is allowed for upgrade purposes only.

Adobe notes that a PHP change can surface deprecations in custom code and third-party extensions, so test on staging before you change production.

Adobe Commerce on Cloud Dependency Deadlines

Adobe has set dependency dates for Adobe Commerce on Cloud. Environments that miss them may have Admin access or inbound traffic suspended.

Contact Adobe Support early if you expect to miss a date. Elasticsearch to OpenSearch and Redis to Valkey are migrations to different software, so custom code and extensions that reference the old service may need changes. The OpenSearch target depends on your version, so check Adobe’s enforcement policy for your exact release.

Adobe states that this policy does not cover on-premises deployments. If you self-host, nobody enforces these dates, but you still own the dependencies.

Adobe Commerce 2.4.9 System Requirements

Adobe supports only the combinations it lists for 2.4.9. Compare your current stack against the table below to see what has to change first.

The Cloud template lists MariaDB 12.3 as recommended, with 11.8 also shown. Check your database version against Adobe’s list before you schedule the upgrade.

On-premises stores on MySQL 8.0 have a separate problem. MySQL 8.0 reached end of support on April 30, 2026. Adobe lists MySQL 8.4 for 2.4.8 and 2.4.9 on-premises and does not list MySQL for 2.4.7. Check your database against Adobe’s requirements for your exact version.

Extension and Custom Code Risks in a 2.4.9 Upgrade

While the storefront may appear unchanged after the upgrade, the underlying code changes. Adobe’s 2.4.9 release notes list these framework changes:

• Native MVC replaces Laminas MVC. Extensions that touch controllers or routers may need changes.
• Symfony Cache replaces Zend_Cache. Review any custom code that calls Zend_Cache classes directly.
• Symfony moves to 7.4 LTS. Custom classes that extend Symfony core classes may need updates.
• HugeRTE replaces TinyMCE. Check any extension that loads TinyMCE or adds TinyMCE plugins.
• PHPUnit moves to 12.x. Older test suites need attention.

Upgrade Path by Version

• 2.4.4 or 2.4.5. Security-only fixes run to May 31, 2027, and Cloud version enforcement starts June 1, 2027. Plan a move to 2.4.9. Cloud customers can also consider Adobe Commerce as a Cloud Service.
• 2.4.6. Standard support has ended, and Adobe Commerce customers get extended support to late August 2027. Adobe lists PHP 8.1 and 8.2 only, so clearing the PHP date means upgrading Commerce.
• 2.4.7. Move to PHP 8.3 as a bridge, or plan 2.4.9 with PHP 8.5.
• 2.4.8. 2.4.9 is optional for now. PHP 8.5 is the target when you go.

Upgrade to 2.4.9 or Move to Adobe Commerce as a Cloud Service

If you run on Adobe Commerce on Cloud, Adobe offers a second route. According to its lifecycle policy, Adobe Commerce as a Cloud Service is Adobe’s recommended long-term destination for Cloud customers.

Staying on 2.4.9 keeps your current setup and clears the PHP requirement. Moving to the Cloud Service is a larger platform decision, so ask your developers to assess your customizations before you choose. The Cloud Service route applies to Cloud customers only.

Adobe Commerce Upgrade Timeline Before the Holiday Freeze

If your team freezes releases before Black Friday, the usable windows are short. The below sequence fits a PHP-only move, a 2.4.9 upgrade, or a move to the Cloud Service.

Step 1: Record what you run

Version, patch level, PHP, database, search, cache, queue, and extensions, on every environment.

Step 2: Ask extension vendors for dates

Request written confirmation of 2.4.9 and PHP 8.5 support.

Step 3: Run a compatibility analysis

On Cloud, the Site-Wide Analysis Tool in the Admin generates an upgrade compatibility report. Adobe decommissioned that tool for on-premises customers in April 2024, so on-premises teams need a code-level check from their developers.

Step 4: Upgrade a staging copy

Move dependencies first, then the application.

Step 5: Test the revenue paths

Test checkout, search, cart, and your custom integrations.

Step 6: Schedule production around trading and document the result

On Cloud, Adobe asks for 48 business hours’ notice for production service upgrades. Keep records your security assessor can review.

On 2.4.7, if the full move does not fit before year-end, move PHP to 8.3 first and schedule the version upgrade for the new year. You still clear the December 31 date.