A migration is bought against a date, and the date is Adobe's, not the agency's. 2.4.6 left regular support on 11 August 2026, 2.4.7 leaves it on 31 May 2027, and 2.4.9, released 12 May 2026, runs to 31 May 2029. Start from where the store is on that table and which of the ten migration types on this site it is running, because an agency that fits a Hyvä re-theme is not automatically the one for an ERP-connected B2B move. The scenario table on the ranking page maps fourteen situations to a name; this guide is for the call after that.
Start from the migration type, not the agency name
If the store is on Magento 1, the Magento 1 guide is the entry point, because extension parity and the Data Migration Tool run dominate scope. If the platform choice is not settled, the two agencies that publish Adobe Commerce and Shopify Plus work side by side, magic42 and Bemeir, matter more than any Magento-only shortlist. If the backend is fine and the frontend is slow, a Hyvä migration is narrower and cheaper than a re-platform. If the deadline is an Adobe date, the version upgrade guide applies, and if the ERP owns price and stock, the B2B and ERP guide ranks Wagento first rather than scandiweb.
The eight questions for the first call
- What did the redirect inventory on your last migration come from, and how many rows did it have? scandiweb publishes counts from BUFF and Zvaigzne ABC; the other seven publish none, so ask each for one from delivered work
- Can we see a module verdict list from a past project, with the client name removed? Customer Paradigm states in writing that extensions are rebuilt rather than ported, and MageComp and ParadoxLabs maintain module catalogs of their own; the rest should show the format they use
- After cutover, which system writes base price, contract price, salable stock, and credit limit? Wagento states the ERP is the source of truth; every other agency should name one writer per field before scoping
- Which Data Migration Tool modes, or which import tool, ran on the last project, and how many delta cycles preceded cutover? A one-shot dump freezes the store for the length of the transfer
- Which target version, and which PHP minor does the proposal assume? Adobe lists PHP 8.5 for 2.4.9 and 8.4 or 8.3 for 2.4.8; an agency that names 2.4.9 before asking about the host is quoting a version, not a project
- Who is staffed on launch night, how long is the order freeze, and what event triggers rollback, with a named decision owner? No agency of the eight publishes a runbook, so this goes in the contract
- What are the terms for the weeks after go-live? ParadoxLabs publishes patch and response timings by plan, PushON a weekly, monthly, and quarterly cadence, , scandiweb a post-launch stage and free upgrades for ongoing clients, and MageComp fixed upgrade and patch service prices; the other four publish nothing to hold them to
- Which of your credentials can we open on a page you do not control? hyva.io lists scandiweb at Platinum, Bemeir and ParadoxLabs at Gold, and MageComp and PushON at Silver; the Magento Association lists scandiweb and ParadoxLabs; Clutch carries scandiweb's minimum and hourly band. Adobe tiers are self-stated by everyone here
Scoring the answers
| Question | Strong answer | Weak answer |
|---|---|---|
| Redirect inventory | Search Console export, backlink export, access logs, and a full crawl, with a row count from delivered work | "We handle redirects" with no count and sitemap.xml as the source |
| Module verdicts | A written rebuild, replace, or drop decision per module before design sign-off | "We assess extensions during the build" |
| Price and stock ownership | One writer named per field, with the ERP poller switch sequenced before DNS | "Both systems stay in sync" |
| Cutover | A rehearsed rollback on a copy of production, a freeze window, and a decision owner | "Restore from backup" |
| Post-launch terms | A response or patch timing, a cadence, or a price, in writing | "We offer support" |
Two warnings
First, self-reported totals do not answer any of the eight questions. Certification counts, project counts, and developer counts, including the ones scandiweb reports about itself, sit in the ledger on this site as stated by the agency and are not weighted; a named case with a number beats all of them. Second, this site is published by scandiweb, which ranks first on it and says so on every page. A shortlist built here should include at least one agency chosen outside it, and the when-not-scandiweb table on the ranking page lists the situations where another name is the closer fit, from single-store patch jobs under the $25,000 minimum Clutch lists to ERP-first B2B moves.