Adobe's upgrade notice for Commerce 2.4.7 lists two options. There are four. Here's the complete technical breakdown — including the two zero-license paths Adobe won't mention in the email.
The timeline
From Adobe's published lifecycle table:
| Milestone | Date |
|---|
| End of standard support | May 31, 2027 |
| End of extended support | May 31, 2028 |
| Cloud upgrade enforcement | June 1, 2028 |
After June 1, 2028, Adobe stops maintenance of Cloud environments on 2.4.7 and reserves the right to decommission them. The driver: 2.4.7 runs on PHP 8.2, which reaches EOL on December 31, 2026. After that the PHP project ships no security patches, which creates a PCI DSS exposure Adobe can't carry on managed infrastructure.
Self-hosted instances don't get auto-decommissioned, but running EOL PHP in production is its own compliance and security problem.
The four paths
Option 1 — Upgrade to Adobe Commerce on Cloud (2.4.8 / 2.4.9)
Keeps your deployment model intact. 2.4.8 is supported until May 2028; 2.4.9 is newer.
- Retains: native B2B suite, Live Search, Page Builder, Adobe support SLA
- Requires: PHP 8.3+, OpenSearch 2.19 (Elasticsearch deprecated)
- Catch: doesn't eliminate future version upgrade obligations — next enforcement date applies
Option 2 — Adobe Commerce as a Cloud Service (SaaS)
Adobe manages all infrastructure, patching, and version upgrades. No future enforcement deadlines.
- Retains: Adobe commercial features
- Trade-off: less stack control, reduced data portability vs self-hosted, customisation constraints
- Suited to: teams that want zero infrastructure responsibility
Option 3 — Magento Open Source 2.4.9
Same PHP runtime, same EAV catalog model, same checkout flow, same Composer extension system. License fee goes to zero. Released May 2026, supported through May 2029.
- What you lose: native B2B suite, Live Search/Sensei, Adobe support contract
- What you gain: zero license, host anywhere, no vendor lock-in
- Works for: teams with in-house PHP capacity or an experienced Magento agency
Option 4 — Mage-OS 3.x
Community-governed nonprofit fork of Magento Open Source. Full extension and theme compatibility with Magento 2. Current line is Mage-OS 3.x, built on Magento Open Source 2.4.9.
Key differences vs Open Source:
- PHP 8.5 support alongside 8.3 and 8.4
- Security updates published within days of Adobe's monthly Patch Tuesday, not on a quarterly cadence
- Independent governance — not subject to Adobe's commercial priorities
Fresh install:
composer create-project --repository-url=https://repo.mage-os.org/ \
mage-os/project-community-edition
Migrate an existing Magento 2.4.8+ store with the official script (developer mode, staging first):
bash <(curl -s https://raw.githubusercontent.com/mage-os-lab/migrate-m2-to-mageos/refs/heads/main/migrate-to-mage-os.sh)
Breaking-change warning for Mage-OS 3: PHP 8.2 is no longer supported (minimum PHP 8.3, 8.4 recommended), and Symfony moved 6.4 → 7.4 LTS. Extensions that extend Symfony classes — particularly CLI commands — will need updates. Adobe analytics modules were also removed. Budget for this in your test pass.
Side-by-side comparison
| Adobe Commerce | Open Source 2.4.9 | Mage-OS 3.x |
|---|
| License | Revenue-based | $0 | $0 |
| Native B2B | Yes | No (extension) | No (extension) |
| Live Search | Yes | No | No |
| PHP 8.5 support | Pending | Pending | Shipped |
| Security patch cadence | Adobe quarterly | Adobe quarterly | Days after Patch Tuesday |
| Min PHP | 8.2/8.3 | 8.3 | 8.3 |
| Extension compat | Full | Full | Full |
| Vendor lock-in | High | None | None |
| Hosting | Adobe | Any | Any |
What requires work regardless of path
All four require the same 2.4.8/2.4.9 infrastructure changes:
- PHP 8.3+ (PHP 8.2 EOL Dec 31, 2026)
- OpenSearch 2.19 (Elasticsearch deprecated in 2.4.x)
- Hyvä theme (optional, but if the stack is already open — Luma is effectively legacy; Hyvä reaches sub-2-second product pages on Tailwind + Alpine.js)
Distinctive work for Options 3 and 4:
- Replace Adobe's native B2B suite with extensions (company accounts, shared catalogs, quote-to-order)
- Replace Live Search with OpenSearch-based tooling
- Drop Adobe support contract — confirm your team or agency has coverage
License cost reality check
Adobe Commerce is a revenue-participation model:
| GMV | Cloud estimate |
|---|
| Under $1M | ~$40K/yr |
| $1M–$5M | ~$55K–80K/yr |
| $5M–$25M | up to ~$190K/yr |
(Independent estimates — Adobe doesn't publish official pricing.)
For a $3M GMV store, three years on Open Source vs Adobe Cloud saves roughly $150K+. That funds the migration and infra modernisation with room to spare.
Quick decision tree
Rely on Adobe's native B2B suite (company accounts, shared catalogs, quote-to-order)?
├── Yes + need Adobe SLA or Experience Cloud integration → Option 1 or 2
└── No / replaceable with extensions
└── Want faster security patches + independence from Adobe's PHP roadmap?
├── Yes → Mage-OS 3.x (Option 4)
└── No / Adobe quarterly cadence is fine → Magento Open Source 2.4.9 (Option 3)
The clock
June 1, 2028 sounds far away. A properly scoped mid-market migration — audit, dependency updates, B2B feature replacement, QA, staged cutover — typically runs 6–10 weeks. At $4M+ GMV with B2B workflows, budget more.
Start the scoping conversation now.
Full breakdown with pricing worked examples and FAQ: angeo.dev/adobe-commerce-2-4-7-end-of-life-options/
Lifecycle dates from Adobe's published policy. License figures are third-party estimates — verify against Adobe's official lifecycle page and request a direct quote before budget decisions.