Magento 2 end of life: what the dates mean and what to do next

Magento 2 as a product is not being switched off. What ends is support for a particular release line, such as 2.4.5 or 2.4.6. Adobe gives each version three years of standard support from its General Availability date: quality fixes, security patches and help from Adobe support. When those three years are up, that line is out of standard support, whatever the newer lines are doing.

Some older lines get more time on top, in two forms. Extended support is one extra year, at no cost, for Adobe Commerce customers on 2.4.6 and 2.4.7. A security-only period is a one-time exception for 2.4.4, 2.4.5 and 2.4.6: isolated security fixes only, no quality fixes, and Adobe says it will not be extended and should be treated as time to migrate. Both are set out in Adobe's lifecycle policy.

If you run Magento Open Source, the free edition, the extra time does not apply to you. Adobe's release policy says extended support security patches are available to Adobe Commerce customers only and not for the Magento Open Source code base. In practice the end of standard support is your end date.

These are Adobe's dates for Adobe Commerce as of its policy page updated on 18 September 2026. The last column is where each line stands today, 1 October 2026.

The shop does not stop working the day support ends. It keeps taking orders. What changes is that the problems found after that day stay unfixed, and the gap grows every month.

• No more security patches. New vulnerabilities in Magento's own code are fixed only in supported lines. Online shops handle customer accounts and payments, so they are a common target.
• PHP runs out too. Adobe does not fix third-party dependencies such as PHP, MySQL or OpenSearch. PHP 8.1 reached its end of life on 31 December 2025 and PHP 8.2 reaches it on 31 December 2026, according to PHP's supported versions page. An old Magento line often cannot move to a newer PHP without being upgraded itself.
• PCI compliance is at risk. Adobe says that running an end-of-life PHP puts PCI compliance at risk. That matters to anyone who takes card payments. This is general information, not legal advice: confirm what it means for you with your payment provider.
• Extensions move on. Extension vendors build for supported releases, so updates and fixes for older lines dry up, and a store with many extensions can get stuck between versions.
• On Adobe's cloud, the storefront itself. From 1 June 2027 Adobe will no longer maintain Adobe Commerce on Cloud environments running unsupported versions and may suspend traffic, which takes the storefront offline.

1. 1

   Find your exact version and PHP

   Check the Magento release line (for example 2.4.6-p something) and the PHP version the server runs. Compare both with the table above and with PHP's own end of life dates. That tells you how much time you really have.

2. 2

   List your extensions and customisations

   Write down every extension, its vendor and whether it still gets updates, plus any custom modules and theme changes. This list is the biggest cost of an upgrade, and it is also the list of things you would need to replace elsewhere.

3. 3

   Choose upgrade or replatform

   Price both honestly. An upgrade buys three more years on a supported line but repeats in three years. A replatform costs more effort once but can remove the upgrade cycle altogether. The comparison below helps.

4. 4

   Plan the migration

   Decide what data has to move: catalogue, customers, order history, promotions, content. Run it on a copy first, check it, and pick a quiet week to switch over.

5. 5

   Keep your URLs and redirects

   Search rankings live on your product and category addresses. Keep the same URLs where you can, redirect the rest, and export any custom redirects you added over the years, so nothing falls through.

For a side-by-side look at what Magento does and what a hosted platform does, see Magento compared.

WhizzyCommerce is a hosted platform built in Portugal for European merchants, in open beta. Its one-file Magento 2 importer brings across categories, products with variants and images, customers, order history and promotions. For the first 100 shops moving from Magento 1 or 2, a person on our side runs the move for free and keeps your URLs working. The full process is on switching from Magento.

What stays behind, plainly: Magento CMS pages, reviews, newsletter consent and custom redirects do not come across, and blog posts only from Magefan, with the Blog plugin on. If you rely on any of these, plan to rebuild or re-collect them, and export your custom redirects before you switch.