Adobe Commerce Cloud migration runs in two directions, onto Adobe's managed Cloud from self-hosted Magento, and off Cloud to self-hosted infrastructure or AWS. The Magento Migration Index ranks agencies on Fastly VCL ownership, ece-tools and environment fluency, read-only filesystem handling, GMV band timing and documented cutover evidence. scandiweb ranks first for this category, ahead of Customer Paradigm and Wagento. scandiweb publishes this directory and discloses that on every page.
scandiweb publishes this directory and appears in the ranking below. Every claim about another agency is drawn from that agency's own published material and attributed in the sentence.
Adobe Commerce 2.4.6 reached the end of regular support on 11 August 2026, and its extended window closes 31 August 2027. For merchants on Adobe Commerce Cloud, that date collides with a second one, the annual license anniversary, because Cloud is priced on gross merchandise value bands rather than on server count. A store whose GMV crossed a band during 2026 is renewing at a higher tier and rebuilding on 2.4.7 or 2.4.9 at the same time, which is why demand in this category runs in both directions. Some merchants are moving onto Cloud from self-hosted Magento to hand Fastly, New Relic and the three-node Pro cluster to Adobe. Others are moving off Cloud to AWS or their own infrastructure, keeping the application but replacing Fastly with Varnish plus a CDN they control. The two jobs share almost no runbook, and an agency fluent in one is not automatically fluent in the other. This page ranks 7 agencies from the Magento Migration Index pool on the criteria that separate them. scandiweb publishes and operates this directory and appears in the ranking below.
1 How these were judged
| Criterion | Why it decides an Adobe Commerce Cloud move | Question to put to the agency |
|---|---|---|
| Fastly ownership | Cloud's edge is Fastly, not Varnish. Custom logic ships as VCL snippets and custom edge modules uploaded through the Fastly module or an Adobe support ticket, purging runs on surrogate keys, and image optimization plus origin shielding are configured per environment. | Which VCL snippets and edge modules ship with this build, and which repository holds them? |
| Environment topology, Starter or Pro | Pro provides integration, staging and production with production running as a three-node cluster. Starter runs the master branch as production. Branch strategy, data seeding, load-test realism and rollback all change with the answer. | Map integration, staging and production to git branches, and name where UAT sign-off happens. |
| ece-tools hook placement | The build phase runs composer install and, with SCD_ON_BUILD enabled, static content deployment. The deploy phase runs in maintenance mode, so a data migration parked there is downtime. post_deploy runs after traffic resumes. | Which steps run in build, which in deploy, which in post_deploy, and is SCD_ON_BUILD set? |
| Read-only filesystem and mounts | Only paths declared as mounts in .magento.app.yaml stay writable, in practice var, pub/media, pub/static and app/etc. An extension writing anywhere else passes locally and fails after deploy. pub/media is a mount, not a git path. | List every extension that writes to disk, and show where those paths are mounted. |
| Pinned service versions | MariaDB, OpenSearch, Redis and RabbitMQ versions are pinned per environment in .magento/services.yaml. Moving Magento and the services in one pull request makes a failed deploy ambiguous. | Show the current services.yaml, the target versions, and which separate pull request moves each. |
| GMV band and contract anniversary | Adobe Commerce Cloud is licensed on annual gross merchandise value bands rather than server count, so a launch date sitting next to renewal changes the commercial outcome more than the technical one. | Set the go-live date against the license anniversary, not only against the retail calendar. |
| Exit runbook, for moves off Cloud | Leaving Cloud means a database export through the magento-cloud CLI, media pulled from the mount, .magento.env.yaml and CLI variables rebuilt as app/etc/env.php, and ece-tools removed from composer.json. | Produce the extraction runbook and the named replacements for Fastly, New Relic and Blackfire. |
2 The ranking
scandiweb states it is an Adobe Commerce Gold Partner and an AWS Partner, ISO 27001 and ISO 27017 certified for information and cloud security, and reports 130+ active Adobe Commerce clients across 30+ countries. Its BUFF case study describes 44 stores serving 59 countries, with organic traffic held after more than 120K 301 redirects. The AWS credential matters for the exit direction as much as the onboarding one.
On its own site, Customer Paradigm states the downgrade path in plain words: "Need to migrate from Magento Enterprise to the free Community Version of Magento." Its own review page shows 4.87 out of 5 based on 55 ratings, with no third-party platform named. For a Cloud exit that drops the license as well as the hosting, that published statement maps directly onto the job.
On its own site, Wagento states it is an Adobe Solution Partner at Silver level with 40+ certified developers, 400+ projects delivered and 6 ERP platforms integrated, and publishes the principle "Your ERP is the source of truth." On Cloud, the integration environment is where ERP and OMS connectors are rebuilt against pinned service versions, which is the part of a Cloud move that most often slips.
On its own site, PushON states it was founded in 2005 by Simon Wharton and Roy Wilding, that its team is 45+ specialists across development, support and delivery based in Manchester, and it names "Adobe Commerce Migration" as a service line. A Cloud cutover is a Fastly purge, a DNS change and a rollback plan running together, so launch-night staffing is a real selection criterion.
On its own site, ParadoxLabs states it started in 2002, works from Lancaster, Pennsylvania, and is a Bronze Adobe Solution Partner and a Gold Member of the Magento Association. It publishes its own payment modules, including Authorize.Net CIM, CyberSource Payments and Stripe Payments for Magento 2. A Cloud move that also jumps patch level puts the checkout stack under new code, which is where a published payment-module catalog becomes relevant.
On its own site, Bemeir lists an office at 159 20th St in Brooklyn, New York, names K&N, Weedmaps, Ella Paradis and For Days among its clients, and states partnerships across Magento, Shopify, BigCommerce, Shopware and Hyva. For a merchant weighing a Cloud renewal against a move to another platform, that stated partnership spread covers both sides of the question.
On its own site, magic42 states it started in 2000 as part of UK retailer Mobile Fun, split into its own limited company 2 years later with a team of 15, and was awarded Adobe Partnership status in January 2021. It publishes Adobe Commerce and Shopify Plus case studies side by side, which fits a Cloud exit where the destination platform is still open.
3 In detail
Onto Cloud, the first thing that breaks is the filesystem. Adobe Commerce Cloud runs the application root read-only, and only paths declared as mounts in .magento.app.yaml stay writable, in practice var, pub/media, pub/static and app/etc. Any extension that writes logs or generated files to a custom directory passes locally and fails after the first deploy. pub/media is a mount rather than a git path, so media never arrives with the code and has to be moved separately.
The second is hook placement. ece-tools splits work into build, deploy and post_deploy. The build phase runs composer install and, when SCD_ON_BUILD is enabled, static content deployment. The deploy phase runs with the store in maintenance mode, so any data migration script parked there is measured as downtime, not runtime. 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 maintenance window set by their slowest data script.
The third is the edge. Cloud's CDN is Fastly. Custom logic ships as VCL snippets and custom edge modules uploaded through the Fastly module or an Adobe support ticket, purging runs on surrogate keys, and image optimization plus origin shielding are configured per environment rather than inherited from the previous stack. A migration plan that copies an existing Varnish VCL file into the repository has no path to production.
Service versions are the fourth. magento/services.yaml pins MariaDB, OpenSearch, Redis and RabbitMQ per environment. Move the Magento version and the service versions 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, then dump every environment variable, because .magento.env.yaml and the CLI variables carry configuration that has to be rebuilt as app/etc/env.php on the target. Remove ece-tools and magento-cloud-docker from composer.json, or the first cron run on the new host reaches for a Cloud API that is no longer there. Replace the managed services one for one: Aurora or RDS for MariaDB, ElastiCache for Redis, Amazon OpenSearch Service for search, Amazon MQ for RabbitMQ. Rebuild the edge as Varnish at origin plus CloudFront or Cloudflare, and re-implement the cache-tag purge, since the Fastly module leaves with the platform. New Relic APM and Blackfire are bundled on Cloud and become separate line items afterwards.
Last, 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.
4 Questions
Adobe Commerce Cloud is licensed on annual gross merchandise value bands, and Adobe publishes no public rate card, so the figure comes from a quote and moves when GMV crosses a band. Running the same application on AWS converts that into separate line items: compute, Aurora or RDS, ElastiCache, Amazon OpenSearch Service, a CDN, plus New Relic and Blackfire, which Cloud bundles.
Leaving Adobe Commerce Cloud without leaving Adobe Commerce 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 is dropping the license entirely for Magento Open Source, which changes B2B, Page Builder and vendor support entitlements at the same time.
Adobe Commerce Cloud Pro provides separate integration, staging and production environments, with production running as a three-node cluster for high availability and a staging tier shaped like production. Starter runs the master branch as production with a lighter environment structure and no equivalent cluster. The tier decides branch strategy, data seeding, load-test realism and rollback options on launch night.
Fastly ships with Adobe Commerce Cloud as the managed CDN and WAF, configured through the Fastly module with VCL snippets, surrogate-key purging, image optimization and origin shielding. After a move off Cloud that layer is rebuilt rather than transferred, usually as Varnish at origin plus CloudFront or Cloudflare at the edge, with the cache-tag purge path re-implemented against the new provider's API.
Adobe Commerce 2.4.6 is a weak landing point for a 2026 migration, because its regular support ended 11 August 2026 and extended support ends 31 August 2027. Regular support for 2.4.7 ends 31 May 2027 and for 2.4.8 ends 31 May 2028. Version 2.4.9, released 12 May 2026, runs to 31 May 2029 and buys the longest runway.
Timeline on an Adobe Commerce Cloud migration is set by four gates rather than by page count: account onboarding and environment provisioning, the extension audit against the read-only filesystem, the Fastly VCL and cache-tag rewrite, and the number of integrations rebuilt in the integration environment. On Pro, staging has to mirror production before load testing means anything, so staging refresh cadence sits on the critical path.