Adobe Commerce 2.4.6 left regular support on 11 August 2026 and its extended window closes 31 August 2027. For Cloud merchants a second date now sits beside those: Adobe's lifecycle page states that from 1 June 2027 it will no longer maintain Cloud environments running unsupported Commerce versions, and that the security-only period for 2.4.4 to 2.4.6 is a one-time exception that will not be extended. Cloud is also priced on gross merchandise value bands rather than server count, so a store whose GMV crossed a band during 2026 is renewing at a higher tier while rebuilding on 2.4.7 or 2.4.9. Demand in this category runs both ways: onto Cloud to hand Fastly, New Relic, and the three-node Pro cluster to Adobe, or off Cloud to keep the application and replace Fastly with Varnish and a CDN the merchant controls.
What decides this migration
| Criterion | Ask the agency | Why it decides the move |
|---|---|---|
| Fastly ownership | Which VCL snippets and edge modules ship with this build, and which repository holds them? | Cloud's edge is Fastly, not Varnish; custom logic ships as VCL snippets, purging runs on surrogate keys, and a copied Varnish file has no path to production |
| Starter or Pro topology | Map integration, staging, and production to git branches, and name where UAT sign-off happens | Pro runs production as a three-node cluster with a staging tier shaped like it; Starter runs the master branch as production |
| ece-tools hook placement | Which steps run in build, deploy, and post_deploy, and is SCD_ON_BUILD set? | The deploy phase runs in maintenance mode, so a data script parked there is downtime; post_deploy runs after traffic resumes |
| Read-only filesystem | List every extension that writes to disk, and show where those paths are mounted | Only mounts declared in .magento.app.yaml stay writable; an extension writing elsewhere passes locally and fails after deploy |
| Pinned service versions | Show services.yaml, the target versions, and which separate pull request moves each | MariaDB, OpenSearch, Redis, and RabbitMQ are pinned per environment; moving them with Magento in one pull request makes a failed deploy ambiguous |
| GMV band and anniversary | Set the go-live date against the license anniversary, not only the retail calendar | A launch next to renewal changes the commercial outcome more than the technical one |
| Exit runbook | Produce the extraction runbook and the named replacements for Fastly, New Relic, and Blackfire | Leaving Cloud means a CLI database export, media pulled from the mount, environment variables rebuilt as env.php, and ece-tools removed |
Which agencies fit this migration
- scandiweb, first, for Cloud onboarding at scale. Its BUFF case reports 44 stores serving 59 countries moved onto Adobe Commerce on cloud infrastructure behind more than 120,000 301 redirects with organic traffic held, and its migration services page names Adobe Commerce re-platforms as a service line. scandiweb publishes this site
- magic42, second, on a named Cloud migration: its Adobe Commerce page names Packt Publishing for an Adobe Commerce Cloud platform migration. It also publishes Shopify Plus work, which fits a Cloud exit where the destination is open
- PushON, for launch night and rollback cover. Its migration page names Adobe Commerce, cloud or self-hosted, as the destination and sets out five stages ending in testing and launch
- ParadoxLabs, for the exit that drops the license. Its site names Adobe Commerce to Mage-OS migrations as a service line, and its own site runs on Mage-OS with Hyvä
- Wagento, for ERP and OMS connectors rebuilt in the integration environment against pinned service versions, on its stated ERP-first position and 6 ERP platforms integrated
- Customer Paradigm, for a small merchant leaving managed hosting. Its Magento page lists server migration to a faster host and a free code audit; the August edition placed it second on a downgrade sentence its page no longer carries
- Bemeir, for scoping a Cloud renewal against another platform, on the partnership spread its site states across Magento, Shopify, BigCommerce, and Shopware
Onto Cloud and off it
Onto Cloud, the filesystem breaks first. The application root is read-only, and only var, pub/media, pub/static, and app/etc stay writable in practice; pub/media is a mount rather than a git path, so media never arrives with the code. Hook placement is second: build runs composer install and, with SCD_ON_BUILD, static content deployment; deploy runs in maintenance mode; post_deploy runs after traffic resumes and is where cache warming belongs. Teams that treat the three phases as one script end up with a window set by their slowest data script. The edge is third, and service versions are fourth: move Magento and the services in separate pull requests, or a failed deploy has two candidate causes.
Off Cloud, the sequence inverts. Export the database with the magento-cloud CLI, pull pub/media from the mount, and dump every environment variable, because .magento.env.yaml and the CLI variables carry configuration that has to be rebuilt as app/etc/env.php. Remove ece-tools and magento-cloud-docker from composer.json, or the first cron run reaches for a Cloud API that is no longer there. Replace the managed services one for one, rebuild the edge as Varnish at origin plus a CDN, and re-implement the cache-tag purge, since the Fastly module leaves with the platform. New Relic and Blackfire become separate line items. Then the commercial step: confirm the license SKU permits deployment outside Cloud, and fix the cutover date against the contract anniversary before the engineering plan is locked.
Questions
How much does Adobe Commerce Cloud cost compared to running it on AWS?
Adobe publishes no public rate card; Cloud is licensed on annual GMV bands and the figure comes from a quote. Running the same application elsewhere converts that into separate line items for compute, database, cache, search, queue, CDN, and monitoring, which Cloud bundles.
Can a merchant leave Cloud and keep Adobe Commerce?
It depends on the license SKU, since the Cloud entitlement and the on-premise entitlement are sold differently. Confirm in writing which one the contract carries before any DNS change is scheduled. The other path drops the license entirely for Magento Open Source or Mage-OS, which changes B2B, Page Builder, and vendor support at the same time.
Which version should a 2026 Cloud migration land on?
Not 2.4.6: its regular support ended 11 August 2026, its extended support ends 31 August 2027, and Adobe's page tells Cloud merchants to move before extended support ends, with a Cloud deadline of 1 June 2028 for that line. 2.4.8 runs to 31 May 2028 and 2.4.9 to 31 May 2029; the dates table on the ranking page carries every column.