Home / Insights / Replatforming
Replatforming
Adobe Commerce and Magento support dates: what ends when, and what to do by each date
By DEQIO · October 2026 · 6 min read
In short
Three deadlines matter to most Magento stores over the next 18 months. PHP 8.2 loses security support on 31 December 2026. Adobe Commerce 2.4.7 loses support on 31 May 2027. And any store still on 2.4.6 is already past its date. If a replatform is on the table, the timing means most stores need an upgrade first, whatever they decide.
For the board, in brief
If your store runs on Magento, three dates set your ecommerce spend for the next 18 months: 31 December 2026 (PHP 8.2 loses security support, a PCI risk), 31 May 2027 (Adobe Commerce 2.4.7 support ends) and 31 May 2028 (2.4.8). A replatform takes five to ten months, so most stores need to budget for an upgrade now, even if they plan to move later. This week, ask your agency for the four facts listed below. Everything technical in this article can go straight to them.
The dates, by release line
Adobe gives each Adobe Commerce release three years of support from general availability (Adobe lifecycle policy). After that date, no more security patches or quality fixes ship for that line.
| Release line | Released | End of standard support | Where it stands |
|---|---|---|---|
| 2.4.9 | 12 May 2026 | 31 May 2029 | Current release |
| 2.4.8 | 8 April 2025 | 31 May 2028 | Supported; the safe upgrade target for most |
| 2.4.7 | 9 April 2024 | 31 May 2027 | About seven months left |
| 2.4.6 | 14 March 2023 | 11 August 2026 | Out of standard support |
| 2.4.5 and earlier | 2022 or earlier | Ended in 2025 or before | Out of support |
Adobe has changed some of these dates during 2026: its 2.4.7 date moved from 9 April to 31 May 2027. Always check the live page before committing budget.
Open Source and Adobe Commerce are not the same. Adobe Commerce customers can sometimes buy extended support for up to a year beyond the standard date. Magento Open Source stores cannot (Adobe extended support). If you run Open Source, the standard date is your real deadline.
The two deadlines inside the deadline
Your Magento version is one clock. The software it runs on has its own.
■ PHP 8.2 reaches end of life on 31 December 2026. Both 2.4.6 and 2.4.7 can run on PHP 8.2, so a 2.4.7 store that has never moved to PHP 8.3 hits a security problem five months before its Magento date. Adobe flags running end-of-life PHP as a PCI compliance risk.
■ PHP 8.1 has been out of support since 31 December 2025. Any store still on it is already exposed.
■ MySQL 8.0 reached end of support on 30 April 2026. Adobe advises on-premises stores on 2.4.5 to 2.4.7 to move to MariaDB, and says 2.4.8 and 2.4.9 are the last versions to support MySQL at all (Adobe MySQL notice).
PCI compliance is your responsibility, not your agency’s or Adobe’s. Share these dates with your qualified security assessor.
Find out which dates apply to you (15 minutes)
Ask your agency or developer for four facts, in writing:
1. Edition: Adobe Commerce (licensed) or Magento Open Source?
2. Version and patch level: the exact release, for example 2.4.7-p6. Your developer can read it with bin/magento --version.
3. PHP version in production, not just in the development environment.
4. Database: MySQL or MariaDB, and which version.
Then read across the table. Your deadline is whichever comes first: the Magento date for your line, or the PHP date for the version you run.
Get the Replatform Decision Checklist
The questions to answer before you commit six figures.
Work backwards from the date
The mistake we see most is treating the support date as the day to start. It is the day you need to be finished.
| Route | Typical duration | Start by, to beat 31 May 2027 |
|---|---|---|
| PHP upgrade within 2.4.7 (8.2 to 8.3) | 2–6 weeks, mostly extension testing | Now, to beat 31 December 2026 |
| Upgrade to 2.4.8 | 2–4 months for a store with many extensions | January 2027 at the latest |
| Replatform, mid-market | 5–10 months (Elogic, 2026) | Already late |
The upgrade durations are our planning ranges; your extension count and custom code drive the real figure.
The practical conclusion: if you are on 2.4.7 and thinking about a replatform, you almost certainly cannot finish one before May 2027. Plan to upgrade to 2.4.8 first, which buys you until May 2028, and make the replatform decision properly rather than in a panic. A rushed replatform to beat a deadline is usually more expensive than the upgrade it was meant to avoid.
Upgrade or move: three questions that decide it
1. How much of your store is custom? Count extensions and custom modules. A store with 60+ extensions faces a costly upgrade every three years. That recurring cost belongs in the replatform business case.
2. What do you need that Magento does well? Complex B2B pricing, quotes and approval flows are where Adobe Commerce is strongest. If you are mainly direct-to-consumer, the case for staying is weaker.
3. What does staying cost over three years? Add licence, hosting, the upgrade you need now, the next one in 2028, and your support retainer. Compare that with a replatform’s three-year cost, not its build quote.
If you can’t answer these with evidence, you are not ready to decide. That’s normal, and it’s exactly what a Replatform Decision Review resolves in three to four weeks.
Six questions to ask your agency this month
■ What exact version, patch, PHP and database are we running in production?
■ Which of our extensions are not yet compatible with 2.4.8 and PHP 8.3?
■ What is your estimate, in days, to upgrade to 2.4.8, and what does it assume?
■ When was our last security patch applied?
■ Is our hosting provider ready for MariaDB and PHP 8.3?
■ If we replatformed in 2027, what would you need from us, and would you quote for it?
The last question matters: an agency that builds on Magento is not neutral about whether you leave it. Their answers are still useful. Just weigh them for what they are.
About DEQIO
Independent ecommerce leadership with 20 years on both the client and supplier side. No platforms, no builds, no referral fees. About DEQIO →
Upgrade or replatform?
A vendor-neutral answer before your support date arrives.