The Adobe Commerce Cloud deadline: which versions lose traffic, and when

What Adobe’s policy says

Adobe’s lifecycle policy for Adobe Commerce on cloud infrastructure now has an enforcement clause. In Adobe’s words, starting June 1, 2027, Adobe will no longer maintain Cloud environments running unsupported Commerce versions, and this includes suspending traffic to the affected infrastructure. The page states the outcome plainly: your ecommerce storefront will go offline.

That’s a different kind of deadline from end of support. End of support means patches stop arriving. The Cloud enforcement date means Adobe can act on your environment. The lifecycle page gives you two ways to stay compliant: move to a supported Adobe Commerce version, or migrate to Adobe Commerce as a Cloud Service, Adobe’s SaaS product. Both have to happen before the published end of extended support for your release line.

The policy also has a second step. If an environment stays non-compliant after traffic suspension, Adobe may terminate cloud services, which starts the decommissioning process. Adobe’s security enforcement page says that after decommissioning, the data and assets in the hosted environment are permanently deleted and can’t be restored.

The dates by version

As of October 2026, these are the dates on Adobe’s lifecycle page. We check that page and keep this table in step with it.

Two things stand out. First, 2.4.4 and 2.4.5 are already out of extended support, so Cloud stores on those versions are in the window where Adobe can act from June 1, 2027. Second, 2.4.6 and 2.4.7 share the same enforcement date, June 1, 2028, even though their extended support ends nine months apart. If you’re on 2.4.6, the extended support date of August 31, 2027 is the one that stops your patches. The June 2028 date is the one that stops your traffic.

Extended support is also an Adobe Commerce benefit, not a Magento Open Source one. Adobe offers one extra year at no additional cost for 2.4.6 and 2.4.7, and it includes quality and security patches for the core application. Open Source gets nothing after standard support ends.

What suspension means in practice

Adobe’s security enforcement page describes two levels. In the lighter one, Adobe may suspend Admin access while the storefront stays online. In the heavier one, inbound traffic is suspended, which takes the storefront offline. Customers can’t reach your site, orders stop, and every ad you’re running sends people to a dead page.

The page doesn’t publish a notice period before suspension. It tells customers who expect to miss a deadline to contact their account team or Adobe Support, and says a short extension may be requested. We’d treat that as a safety net, not a plan. An extension buys weeks, and an upgrade or a migration takes months.

Enforcement isn’t only about the Commerce version either. The same page tells you to confirm that PHP, MariaDB, OpenSearch or Elasticsearch, Redis and RabbitMQ are all on vendor-supported versions, and it lists dependency deadlines of its own, one of them as early as October 30, 2026. For dependency upgrades that Adobe performs, it asks you to open a ticket at least 30 days before your enforcement date so the work can be scheduled.

How to check your version

Adobe documents four ways to find the version you’re running.

In the admin, log in and look at the bottom right of any page. The application version is printed there.

On the server, run this from the Commerce root:

bin/magento --version

You can also request /magento_version on your store’s domain, which returns a shorter answer such as the minor version and edition. And if the store was installed with Composer, composer.lock names either magento/product-community-edition or magento/product-enterprise-edition, which tells you whether you’re on Open Source or Adobe Commerce.

If you’d like a quick read without touching the server, paste your store URL into our free Magento version checker. It reads the version from your public storefront when it can, and tells you which date on the table above applies to you.

One detail matters for Cloud: the security patch level. Adobe appends -pN to security patch releases, so 2.4.6-p3 means the third security patch on 2.4.6. The enforcement policy is about the release line, so 2.4.6-p3 is still 2.4.6 and still carries the June 1, 2028 date.

Upgrade or move

If you’re on 2.4.4 or 2.4.5 on Cloud, June 1, 2027 is a hard date and there’s no extended support left to fall back on. If you’re on 2.4.6 or 2.4.7, you have until June 1, 2028, but patches stop earlier, on August 31, 2027 for 2.4.6 and May 31, 2028 for 2.4.7.

Upgrading keeps you on Adobe Commerce. Adobe’s enforcement page names 2.4.8, 2.4.9 or the latest release as fully supported on Cloud, and asks you to upgrade and validate a non-production environment first, then every environment, not production alone. The cost sits in extension compatibility, theme work, and whatever custom code was written against older APIs. A 2.4.8 upgrade also has its own standard support end of May 31, 2028, so plan for the next jump when you plan this one.

Moving to Shopify ends the version cycle. There’s no release line to track, no enforcement date, and no platform patching on your side. The cost sits in rebuilding the storefront, replacing extensions with apps, and moving your catalog, customers and order history across. We cover what that costs and what moves the number on our Magento to Shopify cost page, and the full migration process on the Magento to Shopify hub.

The way we’d frame the decision: if the upgrade means rewriting the theme and replacing a large share of your extensions, you’re paying for a rebuild either way. If your 2.4.x store is close to stock and your extensions already have 2.4.9 releases, an upgrade is the cheaper way to clear this date, and you can revisit the platform question before the next one.

What to do this quarter

Confirm your version using one of the methods above. Find your line in the table and note both dates, the one that stops patches and the one that stops traffic. Then ask your extension vendors for their 2.4.9 compatibility status, because that answer decides the price of an upgrade. With those three facts in hand, you can get an upgrade quote and a migration quote and compare them on the same page.