From 1 June 2027 Adobe can take unsupported Cloud stores offline
Your store runs on Adobe Commerce Cloud. On Cloud, Adobe enforces its support dates. If an environment is on an unsupported version after the deadline, Adobe may suspend access to the Admin, or suspend traffic and take the storefront offline. If it stays out of line after that, Adobe can close the environment and permanently delete its data.
The date that applies to you depends on the version you run today:
| Your current version | Adobe's deadline to upgrade (or move to Cloud Service) |
|---|---|
| 2.4.4 or 2.4.5 | 1 June 2027 |
| 2.4.6 or 2.4.7 | 1 June 2028 |
| 2.4.8 or 2.4.9 | No date announced yet |
Separately, any Cloud environment on PHP 8.1 or lower must move to PHP 8.2 or higher by 31 May 2027, whatever the Magento version.
We don't yet hold a confirmed record of your exact version and PHP level. That is the first thing discovery confirms.
- If you are on 2.4.4 or 2.4.5, this is urgent. With the December and January trading freeze, there are only about four working months to release before 1 June 2027.
- If you are on 2.4.6 or 2.4.7, it is less urgent. We still recommend planning it now and releasing around a year ahead of the deadline.
- If you are on 2.4.8 or 2.4.9, Adobe has set no deadline yet. Discovery confirms the right next step.
Why upgrade
- Your store stays online. Upgrading avoids enforced suspension and the risk of losing the environment.
- You keep what your licence pays for. Staying supported keeps your Adobe support entitlements and patches.
- The longest runway available. 2.4.9 is supported to 31 May 2029.
- Reduced exposure. Supported software keeps getting security patches, which reduces your exposure to newly found weaknesses. The benefit depends on configuration, so we don't present it as a guarantee.
2.4.9 adds few new features for merchants, and we make no promise of speed gains. The reason to move is support.
Two paths, and when to choose
Adobe offers two ways to meet its deadline. You should hear about both from us first.
| Upgrade to 2.4.9 on Adobe Commerce Cloud | Move to Adobe Commerce as a Cloud Service | |
|---|---|---|
| What it is | An upgrade of your current store | A migration to Adobe's software-as-a-service version |
| What changes | Framework and services move to current versions. Your storefront, customisations and integrations carry over, with updates. | Storefront, customisations and integrations may need rebuilding |
| Size | Depends on your current version | Larger, and confirmed only after an assessment |
| Best timed | Before Adobe's deadline for your version | Against your licence renewal date |
Adobe is steering Cloud customers towards the Cloud Service. Our recommendation comes after discovery, once we know your version, your licence renewal date and how much your customisations would need to change.
What 2.4.9 involves
2.4.9 is the largest change to Magento's internal framework in the 2.4 line. Three internal parts are replaced:
- the Laminas framework, replaced by Magento's own framework
- the Zend cache, replaced by Symfony Cache
- the TinyMCE admin editor, replaced by HugeRTE
Extensions and custom code that use the first two directly need updating, so extension upgrades are usually the largest part of the work.
On Cloud, Adobe manages the services underneath your store. Instead of server work, the service changes (PHP, database, search, cache and message queue) are made through configuration files and Adobe support tickets. Licensed Adobe modules, for example B2B or Live Search if you use them, need their own testing.
Size of the job: to be confirmed in discovery. It depends on your current version, your extensions and custom code, and the licensed modules in use.
Step 1: fixed discovery
We start with one fixed discovery step. It makes no changes to your live store.
Discovery confirms:
- your current Adobe Commerce version and patch level
- your PHP level and the versions of your other services (database, search, cache and message queue)
- your Adobe licence renewal date
- the licensed Adobe modules in use
- your extensions and custom code that the 2.4.9 framework changes affect
We also raise the Adobe support tickets for service changes early, so Adobe's own work does not hold up the project.
Discovery ends with a written recommendation on the two paths, a full estimate with a 15% contingency line, and a release date before your deadline. We confirm the cost of discovery with you in writing before it starts.
Service deadlines to check first. Adobe also sets deadlines for the services underneath your store. Some were due on 30 October 2026, for example Elasticsearch, MariaDB 10.5 or lower, and RabbitMQ 3.9 or lower. Others are due on 31 May 2027. If any of yours are affected, discovery raises them with Adobe first.
Estimate
We do not give an estimate yet. Your version, patch level, PHP level, licence renewal date and licensed modules are not confirmed. Figures from Magento Open Source upgrades do not carry over to Cloud. Server hours are lower, while Adobe coordination and licensed-module testing are higher.
The estimate after discovery will carry a 15% contingency line, with its assumptions and exclusions.
Not included
- Licence or renewal fees for third-party extensions.
- Replacing an extension that has no version compatible with 2.4.9. If discovery finds one, we quote the replacement separately.
- Content fixes caused by the change of admin editor, beyond the checks in testing.
- New features.
- A migration to Adobe Commerce as a Cloud Service. If you choose that path, we quote it separately after an assessment.
Timeline
| When | What happens |
|---|---|
| By 30 November 2026 | You approve discovery |
| December 2026 | Discovery. Adobe tickets raised. No live changes during the trading freeze. |
| January 2027 | Recommendation, full estimate and release date. You choose the path. |
| If on 2.4.4 or 2.4.5: February to April 2027 | Upgrade, testing and release by April 2027, ahead of 31 May and 1 June 2027 |
| If on 2.4.6 or 2.4.7: 2027 | Upgrade released by mid-2027, around a year ahead of 1 June 2028 |
| 31 May 2029 | End of support for 2.4.9 |
Risks and how we manage them
| Risk | Likelihood | Impact | How we manage it |
|---|---|---|---|
| Store suspended after Adobe's deadline | Low if planned | Very high | Confirm your version now and schedule the upgrade well ahead of the date |
| You decide between the two paths without the full picture | Medium | High | We set out both paths ourselves, timed against your licence renewal date |
| Adobe's service changes delay the project | Medium | Medium | We raise Adobe tickets early in discovery |
| A licensed module does not work after the upgrade | Low | Medium | We test B2B and search features explicitly |
| Adobe changes its enforcement terms | Low | Medium | We check Adobe's published policy again at discovery and before release |
Appendix: extension list
Discovery produces the full list of your extensions, each with its current version and the version compatible with 2.4.9. We add it here once discovery is complete.
Sources
- Adobe, Required actions and deadlines to secure Commerce environments (last updated 14 October 2026): https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/version-upgrade-enforcement-policy
- Adobe, Lifecycle policy: https://experienceleague.adobe.com/en/docs/commerce-operations/lifecycle-policy