Based in Kingsteignton, DevonIn person across the South West · video calls UK-wideIndependent perspective. Practical delivery.
V2Vision2Advise · Build · Improve Let’s talk
Choosing a platform

Is your Magento store still supported?

Magento and Adobe Commerce versions have fixed end-of-support dates, and most merchants haven’t been told theirs. Enter your store’s address to see what it runs and where that version stands.

One visit to the homepage and one to Magento’s public version address, from an identified checker. Nothing else on the site is touched. The address you enter is recorded so I can follow up only if you ask me to.

Most stores don’t publish their version, so the check often can’t give you a date. You can see the exact version yourself: in the Magento admin it’s printed at the bottom right of every page, as “Magento ver. 2.4.x”. The patch level after it (-p1, -p2 and so on) doesn’t change the date.

Support ends on a fixed date

VersionStandard support endsExtended support ends
2.4.4 12 Apr 2025 ended 14 Apr 2026 ended
2.4.5 12 Aug 2025 ended 11 Aug 2026 ended
2.4.6 11 Aug 2026 ended 31 Aug 2027
2.4.7 31 May 2027 31 May 2028
2.4.8 31 May 2028 Not yet published
2.4.9 31 May 2029 Not yet published

Support dates verified against Adobe’s lifecycle policy on 4 October 2026. Automatic patch metadata updates do not change these verified deadlines. Extended and security-only support apply to Adobe Commerce; on Magento Open Source, use the standard deadline. The end-of-support guide lists the security-only periods and Cloud deadlines separately. Magento 1 reached end of life on 30 June 2020.

1 June 2027

Adobe’s policy says that from 1 June 2027 it will stop maintaining Cloud environments running unsupported versions, including suspending traffic to them. For a store, suspended traffic means customers can’t reach it.

Adobe’s table sets that Cloud deadline at 1 June 2027 for 2.4.4 and 2.4.5, and 1 June 2028 for 2.4.6 and 2.4.7. These deadlines apply only to Adobe Commerce on Cloud and do not extend Magento Open Source support.

The four options

  1. Upgrade to a supported 2.4 release. Back into the patch cycle; cheapest if the codebase is healthy.
  2. Move to Adobe Commerce. Solves support and adds a substantial licence.
  3. Replatform to WooCommerce or Shopify, depending on complexity and how much of the platform you want to own.
  4. Mage-OS with Hyvä. The community fork: faster patching, and you keep ownership, with a smaller ecosystem.

Which is right depends on the state of the code, the integrations and what the store needs to do next. Working that out starts with a version and health check of the store, a fixed fee from £750, and a written view on whether to stay, upgrade or move. Send me the address and I’ll tell you what I’d look at first.

Ask about a health check

For the dates, the options and their trade-offs in plain English, read the Magento end of support guide.

Already have an agency retainer? See how I help Magento teams with roadmaps, budgets and delivery

Already have a replatform quote? See how three quotes compare once the gaps are costed

What are you trying to get moving?

Tell me where things stand, what needs to change and any date you are working towards.

You might have a project to scope, systems that aren’t joining up, or a task that keeps taking too much time. You don’t need a finished brief to start a conversation.

Start with what’s getting in the way.

A few lines about the situation, the people involved and what a useful result would look like are enough. I’ll come back to you personally with a practical next step.

The privacy policy explains how I handle your enquiry and personal information.

Let’s talk