If you run Adobe Commerce on Cloud and got the end-of-life notice for 2.4.7, here's the short version: the upgrade enforcement date is June 1, 2028. After that, Adobe stops maintaining Cloud environments still on 2.4.7 and reserves the right to decommission them.

Per Adobe's published lifecycle table, the 2.4.7 timeline is:

The notice is real. But it quietly narrows your options to two when there are four.

Why the deadline exists (and it's a good reason)

2.4.7 runs on PHP 8.2. PHP 8.2 reaches end of life on December 31, 2026 — after that the PHP project ships no more security patches for it. Adobe hosts the infrastructure, so Adobe owns its PCI compliance. Running an EOL PHP runtime on a payment-handling store is a PCI DSS problem, not just a hygiene one. That's the actual logic behind enforcement, not pure commercial pressure.

The four paths

Adobe officially lists two:

1. Upgrade to the latest Adobe Commerce on Cloud — 2.4.8 (supported to May 2028) or 2.4.9
2. Migrate to Adobe Commerce as a Cloud Service — SaaS, fully managed, no future enforcement deadlines

Two more exist outside Adobe's scope, fully compatible with the same Magento 2 core, with no license fee:

1. Magento Open Source 2.4.9 — same core, self-hosted, $0 license
2. Mage-OS 3.x — community-governed fork, $0 license, ships security patches on a faster community cadence

Adobe's notice will never mention 3 and 4. That doesn't make them less viable.

What changes with each

All four require the same infrastructure work: 2.4.8/2.4.9 need PHP 8.3+ and OpenSearch 2.19 (Elasticsearch is deprecated). That work happens regardless of path.

The license math

Adobe Commerce is revenue-participation — the bill scales with GMV automatically:

• Under $1M GMV → ~$40K/yr on Cloud
• $1M–$5M GMV → ~$55K–80K/yr on Cloud
• $5M–$25M GMV → up to ~$190K/yr on Cloud

For a $3M GMV store moving to Magento Open Source or Mage-OS, the license line goes to zero. Over three years the difference comfortably exceeds $150K.

(Figures are independent third-party estimates; Adobe doesn't publish official pricing.)

What actually transfers

Because Adobe Commerce and Magento Open Source share the same Magento 2 core, moving between them is not a replatform. The CLI commands are identical, every Marketplace extension installs the same way, and theme/catalog/checkout logic carries over.

What needs planning when you drop the Adobe commercial layer:

• Native B2B suite — company accounts, shared catalogs, quote-to-order need extensions or custom dev
• Live Search / Sensei — replaceable with OpenSearch + best-of-breed tools
• PHP & search engine upgrade — required on all paths anyway

The Mage-OS detail worth knowing

A common stale claim is "Mage-OS only has 2.3 with PHP 8.5." That's already outdated. Mage-OS 3.0 and 3.1 are out, built on Magento Open Source 2.4.9, with PHP 8.5 support alongside 8.3 and 8.4.

One gotcha most write-ups miss: Mage-OS 3 dropped PHP 8.2 support — minimum is now PHP 8.3 (8.4 recommended), and Symfony moved 6.4 → 7.4 LTS, so extensions that extend Symfony CLI command classes may need updates. Worth scoping before you commit.

Fresh install is one command:

composer create-project --repository-url=https://repo.mage-os.org/ \
  mage-os/project-community-edition

For an existing Magento 2.4.8+ store, Mage-OS ships an automated migration script (run it in developer mode on staging first). Mage-OS also publishes security updates within days of Adobe's monthly Patch Tuesday, rather than waiting on Adobe's quarterly cadence.

A worked $4M GMV migration

Typical mid-market project:

• Platform: Adobe Commerce on Cloud 2.4.7 → Magento Open Source 2.4.9 + Hyvä
• Duration: ~6 weeks (audit, migration, QA, staged cutover)
• License savings: ~$72K/year
• Hosting cost reduction: ~38% vs Adobe Cloud
• Checkout downtime: none via staged cutover

The heaviest lift is not the platform swap — it's replacing Adobe-specific features (B2B workflows, Live Search) and modernising the infra stack.

Who should stay on Adobe Commerce

This isn't anti-Adobe. Stay if you're:

• Large enterprise B2B relying on native company accounts, shared catalogs, quote-to-order
• A team that needs Adobe SLAs for procurement or compliance
• Deep in Adobe Experience Cloud — Analytics, Target, Real-Time CDP
• High-GMV where Live Search + managed cloud measurably beat the license fee in conversion lift

For those, Options 1 or 2 are rational. The license only looks expensive when you're not using what it buys.

While the stack is open: AI crawler access

One efficiency note, since a 2.4.7 migration means re-deploying robots.txt, schema, and frontend templates anyway. A default Magento 2 install — any edition — blocks AI crawlers in robots.txt, has no llms.txt, and ships incomplete Product JSON-LD. That means it's effectively invisible to ChatGPT, Gemini, and Perplexity, even if it ranks #1 on Google. The fixes touch the same files you're already editing. There's an open-source CLI to check where a store stands if you want to fold it into the same project. Optional, unrelated to the lifecycle decision — just cheaper to do once.

The clock

June 1, 2028 sounds far away. A properly scoped mid-market migration runs 6–10 weeks. The decision comes down to one question: do you need Adobe's commercial layer enough to justify a fee that scales with revenue? If yes → Option 1 or 2. If no → 3 or 4.

Full breakdown of all four paths with a feature matrix and FAQ: angeo.dev/adobe-commerce-2-4-7-end-of-life-options/

Lifecycle dates from Adobe's published policy. License figures are independent third-party estimates — Adobe doesn't publish official pricing. Verify against the Adobe Commerce lifecycle policy and request a direct quote before budget decisions.