Magento end of support: what UK merchants need to do (2026–2028)
Adobe has published fixed end-of-support dates for Magento 2.4 releases. This is a plain-English guide to what they mean, what your options are, and how to choose between keeping the platform, upgrading or moving.
See the datesWhere things stand in October 2026
Support dates verified against Adobe’s lifecycle policy on 4 October 2026.
- Magento 2.4.6 left standard support on 11 August 2026. Adobe Commerce customers get extended support to 31 August 2027. Magento Open Source stores don’t: Adobe says extended support patches “are not available for the Magento Open Source code base” (Adobe release policy).
- Magento 2.4.7 leaves standard support on 31 May 2027. Extended support for Adobe Commerce runs to 31 May 2028.
- 2.4.4 and 2.4.5 are already past standard and extended support. On Adobe Commerce, Adobe lists a security-only period to 31 May 2027.
- Adobe Commerce Cloud has a hard deadline. From 1 June 2027 Adobe says it will stop maintaining Cloud environments on unsupported versions, including suspending traffic: “your ecommerce storefront will go offline” (Adobe lifecycle policy).
- Magento 1 reached end of life on 30 June 2020. If you’re still on it, every option below applies, with more urgency.
Every current 2.4 release
| Version | Standard support ends | Extended support ends (Adobe Commerce only) | Security-only period ends (Adobe Commerce only) |
|---|---|---|---|
| 2.4.4 | 12 Apr 2025 ended | 14 Apr 2026 ended | 31 May 2027 |
| 2.4.5 | 12 Aug 2025 ended | 11 Aug 2026 ended | 31 May 2027 |
| 2.4.6 | 11 Aug 2026 ended | 31 Aug 2027 | 31 May 2028 |
| 2.4.7 | 31 May 2027 | 31 May 2028 | None listed |
| 2.4.8 | 31 May 2028 | Not yet published | None listed |
| 2.4.9 | 31 May 2029 | Not yet published | None listed |
The same verified dataset drives the Magento support checker and platform comparison. Adobe’s Cloud-only deadline is 1 June 2027 for 2.4.4 and 2.4.5, and 1 June 2028 for 2.4.6 and 2.4.7.
The store keeps working. The risk changes.
Nothing switches off on the date itself, except on Adobe Commerce Cloud after the enforcement deadline. What stops is the flow of fixes. Adobe describes standard support as “quality fixes, security patches, and full Adobe Commerce on-call support”. After it ends, new vulnerabilities in your version stay open unless you, or someone you pay, deal with them.
Security. Online stores are a regular target for card-skimming attacks, and a known, unpatched weakness is the easiest way in.
PHP. Older 2.4 releases run on PHP versions that are themselves out of support. Adobe’s policy notes PHP 8.1 reached end of life on 31 December 2025, and PHP 8.2 does on 31 December 2026.
PCI DSS and your payment provider
If you take card payments, you have PCI DSS obligations. Requirement 6.3.3 of PCI DSS v4.0.1 expects critical security patches to be installed within one month of release (PCI Security Standards Council). If your platform no longer receives patches, that is hard to show.
Adobe is direct about who carries this: “PCI compliance is the merchant’s responsibility to assess.” It recommends merchants on affected versions talk to their qualified security assessor and move to a supported version.
Most smaller merchants use a hosted payment page or a payment provider’s fields, which reduces PCI scope. It doesn’t remove the risk of the site itself being compromised. Ask your payment provider what they expect from you.
This is general information, not compliance advice. Your assessor or payment provider has the final word.
Four routes, honestly compared
There’s no right answer for every store. The right one depends on the state of your code, your integrations, how much of the platform you want to own, and what the business needs next. For a full platform comparison, see choosing a platform.
| Compared on | Stay on Magento and upgrade | Move to Shopify | Move to WooCommerce | Something else |
|---|---|---|---|---|
| What it is | Upgrade to a supported 2.4 release (2.4.8 or 2.4.9 today). Often paired with a Hyvä front end. Mage-OS and Adobe Commerce are variants of this route | Rebuild the store on Shopify or Shopify Plus and migrate products, customers and orders | Rebuild on WordPress and WooCommerce, on hosting you control | Another platform, such as a headless or enterprise option, where requirements genuinely call for it |
| Good when | The codebase is healthy, the catalogue or B2B needs are complex, and Magento still fits | Retail is conventional and you want to stop managing servers, patches and upgrades | The store is smaller, content matters, and you want to own the code and data | A specific requirement rules out the other three |
| Watch out for | The next deadline: 2.4.8 standard support ends 31 May 2028. Upgrades are a recurring cost, not a one-off | Monthly app and plan costs, checkout limits, and what you can’t take with you if you leave | B2B, multi-store and very large catalogues get harder. You still own patching and hosting | Higher cost, smaller talent pools, and vendor lock-in |
| What carries over | Almost everything: data, URLs, extensions (if compatible) | Data, with effort. Custom features need apps or rebuilding. URLs change, so redirects matter | Data, with effort. Custom features need plugins or rebuilding. URLs change, so redirects matter | Depends entirely on the platform |
Staying on Magento
Hyvä, the modern Magento front end, became free and open source on 10 November 2025 (summary by Amasty). That removes the licence cost from a front-end rebuild, though some add-ons are still paid.
Mage-OS is a community-run distribution of Magento Open Source (mage-os.org). It keeps you on an owned, open codebase with its own release cycle. The ecosystem is smaller, so check your extensions and your developers before choosing it.
Adobe Commerce brings extended support and Adobe’s own services, at the cost of a licence Adobe prices on revenue.
Leaving Magento
A replatform is a rebuild, not a copy. Products, customers and order history move with effort. Customer passwords usually don’t, so customers reset them. Custom features, B2B pricing rules and integrations are rebuilt or replaced. Every URL needs a redirect, or you lose search traffic you’ve built over years.
Replatforming is the right answer for plenty of stores. It is rarely the cheap answer, and it shouldn’t be chosen just because the support date is close. An upgrade can buy time to replatform properly.
Answer these before you choose
Why quotes vary so much
I won’t quote you a market price for an upgrade or a migration: the range is too wide to be useful, and anyone who gives one without seeing your store is guessing. These are the things that move the number:
- The version gap. Moving from 2.4.4 is more work than from 2.4.7.
- Extensions. Each one has to be updated, replaced or dropped.
- Custom code. Undocumented customisations take the longest to untangle.
- Integrations. Every connected system needs testing, or rebuilding on a new platform.
- Data. Catalogue size, order history and how clean it all is.
- The front end. Keeping the current theme, moving to Hyvä, or a new design.
- Search traffic. Redirect mapping and checks after launch.
- Hosting and running costs. Licences, apps and hosting after go-live, every year.
What to check before you sign
- Is the data migration itemised? Products, customers, orders, reviews, and what’s left behind.
- Is there a redirect plan? Who maps the URLs, and who checks them after launch.
- Are integrations named one by one, or covered by a single line?
- What are the running costs after launch? Apps, plugins, licences and hosting, by year.
- What happens to features nobody wrote down? Ask what’s excluded, not just what’s included.
- Who signs off that it works, and against what?
If you have more than one quote, the proposal comparison shows how three quotes compare once the gaps are costed.
Stay, upgrade or move: a written recommendation
Before you pick a route, I review the available information with you and your developer: the version, extensions, custom code, integrations, hosting and data. You get a written recommendation: which option I’d take and why, the main risks, and what a sound brief for the work looks like. You can take that brief to any agency, or ask me to lead delivery.
I build on WordPress and WooCommerce, with Shopify setup and integrations where they fit. I lead larger Magento and Hyvä programmes with your developers or a specialist agency, managing retainers, roadmaps and delivery. I can take on scoped updates to smaller stores I’ve built and know; inherited stores are assessed before direct work is offered. Deep custom Shopify app work is scoped with specialists too.
Review from £750, with the scope and fee agreed before work starts. The first call is free. Whether we plan work with your agency or agree selected direct updates, implementation and release dates are scoped separately.
Magento advice and delivery All prices
Ask about an assessmentMagento end of support: common questions
Will my Magento store stop working when support ends?
No, not on the date itself. A self-hosted store keeps running. What stops is the supply of security and quality fixes from Adobe. The exception is Adobe Commerce Cloud: Adobe says that from 1 June 2027 it will suspend traffic to Cloud environments on unsupported versions.
When does Magento 2.4.6 support end?
Standard support ended on 11 August 2026. Adobe Commerce customers have extended support to 31 August 2027 and a security-only period to 31 May 2028. Extended support patches aren’t available for Magento Open Source.
When does Magento 2.4.7 support end?
Standard support ends on 31 May 2027. For Adobe Commerce, extended support runs to 31 May 2028.
Do I have to leave Magento?
No. Upgrading to a supported release, 2.4.8 or 2.4.9 today, puts you back in the patch cycle. Replatforming makes sense when Magento no longer fits the business, not just because a date is close.
Is an unsupported Magento version a PCI DSS problem?
It can be. PCI DSS expects critical security patches to be installed promptly, and an unsupported version no longer gets them. Adobe says PCI compliance is the merchant’s responsibility to assess. Check with your payment provider or qualified security assessor.
How do I find out which version I’m running?
Log in to the Magento admin: the version is printed at the bottom right of every page, as “Magento ver. 2.4.x”. Or try the free Magento support checker.
Tell me your version and what the store does. I’ll tell you which option I’d look at first, including when the answer is to leave it alone for now.
Talk through your Magento store