Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
Standard support for Magento 2.4.7 (Adobe Commerce and Magento Open Source) ends on May 31, 2027. For Adobe Commerce customers, Adobe then provides one year of extended support, with quality and security patches for the core application, until May 31, 2028. Adobe's lifecycle policy does not say that Magento Open Source gets this extra year, so Open Source stores should treat May 31, 2027 as the deadline. To be on a supported version with full support by the deadline, you should start your upgrade around December 2026 and aim to go live by mid-May 2027. Below is a month-by-month plan that works back from May 31, 2027.
What happens to 2.4.7 and when
Dates are from Adobe's lifecycle policy. 2.4.7 became generally available on April 9, 2024.
| Date | What changes |
|---|---|
| May 31, 2027 | End of standard support. No more full Adobe Commerce support for this line. |
| June 1, 2027 to May 31, 2028 | Extended support: quality and security patches for the core application. Adobe says this is at no additional cost for Adobe Commerce customers. |
| June 1, 2028 | Cloud enforcement date for Adobe Commerce on Cloud environments still on 2.4.7. |
Two other dates matter. 2.4.7-p10 supports PHP 8.3 and 8.2. PHP 8.2 stops receiving security fixes on December 31, 2026, and PHP 8.3 on December 31, 2027, according to php.net. So if you are on PHP 8.2 today, your PHP version goes out of security support before 2.4.7 itself does. Moving to PHP 8.3 on 2.4.7 is a sensible first step if your upgrade cannot start right away.
2.4.7-p10 also no longer lists MySQL 8.0, which reached end of support on April 30, 2026. Adobe's supported databases for that patch are MariaDB 10.11 and 11.8.
Which version should you upgrade to?
Aim for 2.4.9. It became generally available on May 12, 2026 and is supported until May 31, 2029. 2.4.8 is supported until May 31, 2028, only a year beyond 2.4.7's extended support, so stopping there means planning another upgrade soon after. Our post on what's new in Magento 2.4.9 explains the platform changes, the biggest being PHP 8.5, Valkey 9, OpenSearch 3 and MySQL 8.4 or MariaDB 12.3.
A six-month upgrade plan working back from May 31, 2027
This plan assumes a typical mid-sized store: a few dozen third-party extensions, some custom modules, an ERP or PIM integration and a custom or Hyvä theme. Smaller stores can compress it; complex B2B or multi-site stores may need to start earlier.
| Month | Phase | Key tasks | Done when |
|---|---|---|---|
| December 2026 (M-6) | Audit | Inventory extensions, custom modules, integrations and hosting versions. Check vendor support for 2.4.9 and PHP 8.5. Agree your trading blackout dates. | You have a written list of every module with an action: update, replace, remove or rewrite. |
| January 2027 (M-5) | Scope and environments | Fix the scope and budget from the audit. Order hosting changes (PHP 8.5, Valkey 9, OpenSearch 3, database). Build a staging environment that matches the target stack. | Staging runs the target services, and the scope is signed off. |
| February 2027 (M-4) | Code upgrade | Upgrade Magento and extensions with Composer in a branch. Fix PHP 8.5 issues and code that depends on removed libraries. Update the theme. | The site installs, compiles and runs on staging without errors. |
| March 2027 (M-3) | Integrations and data | Test ERP, PIM, payment, shipping and marketing integrations. Upgrade a fresh copy of the production database. Reindex search and check results. | Orders, stock and prices flow end to end on staging. |
| April 2027 (M-2) | Testing and sign-off | Full regression and user acceptance testing. Performance and load test. Check SEO basics: URLs, canonicals, structured data. Rehearse the deployment and rollback. | The business signs off, and a rehearsal deployment has worked. |
| May 2027 (M-1) | Go-live and hypercare | Go live in the first half of May, outside peak hours. Monitor errors, orders and search for two weeks. Fix issues fast. | Live on 2.4.9 before May 31, 2027, with the old environment retired. |
The step-by-step tasks for each phase, with owners, are in our Magento upgrade checklist.
What usually slows a 2.4.7 upgrade down
Extensions without 2.4.9 support
The longest delays come from third-party modules whose vendors have not released a 2.4.9 and PHP 8.5 compatible version. Check this in month one. For each one, decide whether to wait, replace it, or fix it yourself.
Custom code that relies on removed libraries
2.4.9 replaces Laminas MVC with a native implementation, swaps Zend_Cache for Symfony Cache and moves the Admin editor from TinyMCE to HugeRTE. Custom modules that call these libraries directly need rework.
Hosting lead times
Managed hosts and cloud platforms do not always offer new service versions on day one. Ask your provider early when PHP 8.5, Valkey 9 and OpenSearch 3 will be available on your plan.
Peak season
Many stores freeze deployments in November and December. If that applies to you, finish the audit before the freeze so that development can start in January.
If you cannot finish by May 2027
On Adobe Commerce, extended support gives you a cushion until May 31, 2028, so missing May 2027 is not a crisis. But it is a narrower kind of support, and every month you wait the version gap grows. If you need the extra time:
- Stay on the latest 2.4.7 patch and apply every isolated security patch for it.
- Move to PHP 8.3 before PHP 8.2 leaves security support at the end of 2026.
- Set a new go-live date well before May 31, 2028, and keep it.
Our Magento release tracker lists the current patch level and support dates for each line, so you can check what applies to you.
If you are on Adobe Commerce on Cloud
Cloud projects follow the same support dates, with one extra rule. Adobe's lifecycle policy sets an enforcement date of June 1, 2028 for 2.4.7 on Cloud infrastructure, and says it may take action against environments running unsupported versions, up to suspending traffic. Adobe also points Cloud customers to Adobe Commerce as a Cloud Service as an alternative destination. Either way, the planning steps above still apply: audit, upgrade on a staging branch, test and deploy before your line runs out of support.
FAQ
Is Magento 2.4.7 end of life in 2027?
Standard support ends on May 31, 2027. For Adobe Commerce, extended support continues to May 31, 2028, after which 2.4.7 stops receiving patches. Adobe's policy does not describe extended support for Magento Open Source.
Can I go from 2.4.7 straight to 2.4.9?
Yes. There is no need to install 2.4.8 in between. The work is the same compatibility checking and testing, done once against the target version.
How long does a 2.4.7 to 2.4.9 upgrade take?
It depends on your extensions, custom code and integrations, which is why the plan above starts with an audit. Six months is a comfortable window for a typical store with time for proper testing, not a fixed duration.
Start with the audit
The single most useful thing you can do this month is the extension and integration audit, because it tells you how big the job really is. If you want help with it, or with the full upgrade, see Mistri's Magento upgrade services.
Sources
Adobe Commerce lifecycle policy (Adobe Experience League); System requirements (Adobe Experience League); Supported PHP versions (php.net).
