RLB Packaging: Adobe Commerce Cloud upgrade proposal, to 2.4.9

Adobe will enforce upgrades on Cloud from 1 June 2027

From 1 June 2027, Adobe stops maintaining Adobe Commerce on Cloud environments that run unsupported versions. If your store is on 2.4.4 or 2.4.5 by then, Adobe can suspend traffic, which takes your storefront offline. If the environment stays out of date after that, Adobe can decommission it, which permanently deletes its data. Stores on 2.4.6 or 2.4.7 face the same enforcement from 1 June 2028.

There's a second date too. Any Cloud environment on PHP 8.1 or lower must move to PHP 8.2 or higher by 31 May 2027.

We don't yet have your current version, patch level or PHP version on record, so we can't say today which of these dates applies to you. That's the first thing we'd like to confirm, and it's why this proposal starts with a short discovery step rather than an estimate.

What it means for you, by version

Adobe's current terms also set 30 October 2026 for some older services on Cloud environments, for example Elasticsearch, MariaDB 10.5 or older, and RabbitMQ 3.9 or older. If any of those still run on your environment, that date has already passed. Discovery checks this first.

Adobe's enforcement terms can change, so we'll check them again at the start of discovery.

Why upgrade to 2.4.9

• It avoids enforced suspension and decommissioning of your store.
• It keeps the Adobe support and patches your licence fee already pays for. Staying on a supported version reduces security and compliance exposure.
• It reaches the longest supported runway available. 2.4.9 is supported until 31 May 2029.

2.4.9 is a foundations release with few new merchant-facing features. We aren't selling it on new features or speed gains. The case for it is staying supported and online, and the benefits depend on how the store and its environment are configured.

What changes in 2.4.9

2.4.9 is the largest architectural change in the 2.4.x line. Three parts of the framework are replaced:

1. Laminas MVC is replaced by Magento's own MVC.
2. Zend Cache is replaced by Symfony Cache.
3. The TinyMCE admin editor is replaced by HugeRTE.

Extensions and custom code that use Laminas or Zend Cache directly will break, so extension upgrades are usually the largest part of the work.

On Cloud, Adobe manages the services underneath the store. So instead of server work, the service changes (PHP, database, search, cache and queue versions) are made through configuration files and support tickets with Adobe. Any licensed Adobe modules you use, for example B2B or Live Search, need their own testing.

The second path: Adobe Commerce as a Cloud Service

Adobe also offers Adobe Commerce as a Cloud Service, its software as a service version, and is steering Cloud customers towards it. It's a real option, but it's a migration, not an upgrade: your storefront, customisations and integrations may need rebuilding.

We'd rather you hear about it from us first, with the facts laid out side by side. The right time to decide between the two paths is ahead of your licence renewal date, so we'll confirm that date in discovery and set out both paths against it.

Step 1: discovery

Discovery is a short, fixed piece of work: [Discovery: N hours, about N working days. Josh to confirm]. It makes no changes to your live store. It confirms:

1. Your current Adobe Commerce version and patch level.
2. Your PHP version, and the versions of the other services on your Cloud environment.
3. Your Adobe Commerce licence renewal date.
4. The licensed Adobe modules your store uses, for example B2B or Live Search.
5. Your third-party extensions and custom code, and which ones need work for 2.4.9.

At the end of discovery you get a written estimate for the upgrade with a 15% contingency line, plus a target release date, and a side by side of the upgrade and Cloud Service paths. We'll raise any tickets Adobe needs during discovery, so their scheduling doesn't hold up the project.

Assumptions

• The upgrade estimate comes after discovery. We aren't quoting hours before we know your version, because the work for a 2.4.4 store and a 2.4.7 store is very different.
• The work covers the upgrade only, with no new features. Any feature request found during discovery is quoted separately.
• Adobe makes the service changes on your Cloud environment through its support process. Its scheduling is outside our control, which is why we raise those tickets early.

Exclusions

• Licence or renewal fees for third-party extensions.
• Replacing any extension that has no version compatible with 2.4.9. Discovery flags these early, and we quote each replacement as a variation.
• Fixing admin content that renders differently after the editor change, beyond the checks in testing.
• New features.
• A migration to Adobe Commerce as a Cloud Service. If you choose that path, we'll quote it separately.

Risks

Next step

Approve discovery ([Discovery: N hours, about N working days. Josh to confirm]) and we'll start straight away, so you know which date applies to you, and what the upgrade involves, before Christmas.

Kind regards,

Josh Camp
Chief Executive Officer
PH +64-09-9722636
Email josh@magebinary.com
Web www.MageBinary.co.nz
11/145 Kitchener Rd, Milford, Auckland 0620

Appendix A: Extension list

In discovery we record each third-party extension your store runs in the table below, with the version you run today, the version that supports 2.4.9, and what it needs.

Any extension with no 2.4.9 version is flagged here, and its replacement is quoted separately.