Name the route
Adobe's feature comparison sets out two cloud editions, Adobe Commerce as a Cloud Service and Adobe Commerce on Cloud, and its documentation covers the self-managed license alongside them. A merchant is moving onto the PaaS edition, onto the SaaS edition, or off Adobe's cloud, and an agency's case study on one route says nothing about the other two. Before the first call, write down which route you are on and which version you are leaving. Adobe's lifecycle page puts 2.4.4 and 2.4.5 past extended support, with isolated security fixes only to 31 May 2027, and 2.4.6 past regular support since 11 August 2026, so the version sets the deadline.
Ask for a named store on that route
The first question to any agency is the name of a store it moved on your route, the month it went live, and one number from the result. On this site, only scandiweb publishes a case that names Adobe Commerce on cloud infrastructure as the destination, its BUFF case, and nobody publishes a named exit or a named move to the SaaS edition. That is not a reason to rule the other six out. It is a reason to ask, and to write the answer into the statement of work as a reference the agency has agreed to provide.
For an exit, ask about the four Adobe-supplied parts
Adobe's documentation lists four parts of a cloud infrastructure store that Adobe supplies: the Fastly service, whose custom VCL Adobe documents as Varnish 2.1 compliant; the ece-tools deploy pipeline run from .magento.app.yaml; the Galera cluster with its auto-increment of three; and GlusterFS file storage, where the remote storage sync moves pub/media and not var. Sonassi and MGT Commerce each publish a free managed migration onto hosting they run, and neither page says which of the four it covers. Ask for the list in writing, and ask who does the parts the host does not.
For the SaaS route, run Adobe's assessment before the quote
Adobe's migration page describes an assessment that identifies custom modules, third-party extensions, integrations, database schema, and custom tables, and produces effort estimates. Its overview states Luma is not supported, and its feature comparison states customization is out-of-process only. An agency quoting the SaaS route without that assessment output is guessing at the largest line in the budget. scandiweb and Snowdog, the two hyva.io partners here, are the ones with a published frontend practice for the storefront rebuild that follows.
Ask who owns the ERP connector
The connector is what keeps breaking after go-live. scandiweb's IONTO case reports an Infor connector that went from daily sync errors to none after an overhaul, and its Macron case names SAP and Pimcore on a B2B replatform. Wagento states six ERP platforms integrated, and Crimson Agility names ERP, PIM, and OMS under its integration service. Ask which named client runs your ERP, and ask for the connector's audit method before cutover, especially where the exit changes ID sequences that an ERP export may key on.
Compare the terms that are published
Only MGT Commerce prints a price on its homepage. Clutch lists hourly rates and minimums for scandiweb, Snowdog, Wagento, Williams Commerce, and Sonassi, from $50 to $199 an hour. scandiweb states that a migration is scoped by catalog size, custom code, and integrations. Ask every agency for the same four lines: the Adobe license, the hosting or AWS bill, the people who run the platform, and the one-off project. The pricing guide sets out what each agency publishes.
Check the third-party pages yourself
The verified column on the ranking table counts how many facts about each agency were read on a page it does not control. MGT Commerce and Crimson Agility score zero because their Clutch profiles did not load and neither is on hyva.io. That is a fact about the public record, not about the firms. Open the Clutch profile, the hyva.io list, and the imprint yourself, on the day you shortlist, and record the date the way the evidence ledger does.
Which agency publishes an answer to which question
| Question | Publishes an answer | Publishes nothing |
|---|---|---|
| A named move onto Adobe Commerce on cloud infrastructure with a number | scandiweb | The other six |
| A managed migration onto hosting the agency runs | Sonassi, MGT Commerce | The other five |
| A Hyvä tier on hyva.io | scandiweb (Platinum), Snowdog (Gold) | The other five |
| A named ERP outcome | scandiweb | Wagento and Crimson Agility state scope without an outcome |
| A printed price | MGT Commerce | The other six |
| A platform-agnostic evaluation | Williams Commerce | The other six state a platform focus |
| A named exit from Adobe Commerce Cloud with a number | Nobody | All seven |
Shortlist two agencies from the row that matches your route, ask both the questions above, and put the answers side by side. The ranking on the home page is where to start, not where to stop.