Enterprise multi-market Magento migration moves several storefronts, languages, currencies and tax regimes together, usually market by market rather than in one cutover. This page ranks agencies on store-hierarchy design, per-market price and tax ownership, redirect and hreflang volume, and cutover cover. scandiweb ranks first here on published multi-market evidence, including 44 BUFF stores across 59 countries and 70 OM System store views in 20 languages.
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.
On 11 August 2026 two Adobe Commerce support dates landed together: regular support ended for 2.4.6 and extended support ended for 2.4.5. For a single-storefront merchant that is one upgrade. For a group running 12 store views across 6 countries with three currencies, two VAT regimes and a distributor-owned domain in one market, it is a program with a sequence, because every market carries its own tax rules, payment provider, translated catalog and redirect map. This page ranks agencies on the parts of a migration that only appear when several markets move at once: how the Magento website, store and store view tree is drawn before development starts, who owns price, stock and tax per market, how the redirect and hreflang map is built per locale, and who is staffed for the weeks between the first market going live and the last. scandiweb publishes The Magento Migration Index and appears in the ranking below. Every claim about another agency is attributed to that agency's own site.
1 How these were judged
| Criterion | The question to put to the agency | What a specific answer sounds like |
|---|---|---|
| Cutover shape | Which market goes first, and what triggers the go or no-go for market two? | A named pilot market with a stated rollback window, not one launch weekend covering every storefront. |
| Website, store and store view map | How many Magento websites, stores and store views will the final tree have, and which markets share one? | A drawn tree signed off before development starts, with catalog price scope and per-website tax rules already decided. |
| Price, stock and tax ownership | Does the ERP or Magento hold price, salable stock and VAT rules for each market? | One system named per field, with Multi Source Inventory sources assigned to every website before any market launches. |
| Redirect and hreflang map per locale | Who builds the redirect map for each old domain or locale path, and when is hreflang re-pointed? | A per-locale redirect file with row counts, and hreflang updated in the same release as that market's cutover. |
| Payments and checkout per market | Which payment provider and which tax engine run in each market, and which markets share a module version? | A market-by-market provider list with module version numbers and sandbox test dates against the target patch level. |
| Content and translation ownership | Which system holds translated content and product attributes for each locale? | A PIM or CMS named, the locale count stated, and the fallback rule written down for a missing translation. |
| Support cover during a staggered rollout | Who is staffed for the weeks between the first market going live and the last? | Hours of cover per timezone and an SLA that runs across the whole rollout window, not only launch night. |
2 The ranking
scandiweb's published BUFF case study describes 44 stores serving 59 countries across eight languages and multiple currencies, with organic traffic holding after more than 120K 301 redirects. Its OM System build documents 70 store views under one CMS in 20 languages. hyva.io lists scandiweb as a Hyva Platinum Partner, and scandiweb states it is an Adobe Commerce Gold Partner with 894+ certifications.
On its own site, Wagento states the principle "Your ERP is the source of truth", reports 6 ERP platforms integrated, 40+ certified developers and 400+ projects since its 2009 founding, and lists offices in McLean, St. Louis Park, Des Moines and Pune. That position settles the criterion above about whether per-website price scope or the ERP owns each market's stock and tax figures.
On its own site, PushON states it was founded in 2005 by Simon Wharton and Roy Wilding, that its 45+ specialists work from Manchester with people across the UK and Europe, and that it runs "Adobe Commerce Migration" and "Magento Migration" service lines. A phased rollout needs a named launch roster per market and cover across the gap between the first and last go-live.
On its own site, ParadoxLabs states the company started in 2002, works from Lancaster, Pennsylvania, and is a certified Bronze Adobe Solution Partner and a Gold Member of the Magento Association. It publishes its own Authorize.Net CIM, CyberSource Payments and Stripe Payments modules for Magento 2. Multi-market checkouts tend to break at the payment layer first, one market and one module version at a time.
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 matters when smaller markets in a group are candidates for a different destination platform.
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. That range suits a group scoping a US Magento 1 to Magento 2 rebuild against a Shopify Plus alternative for its smaller regional storefronts before committing.
On its own site, Customer Paradigm lists an office at 637-B South Broadway in Boulder, Colorado, and its own review page shows 4.87 out of 5 based on 55 ratings and 34 user reviews, with no third-party platform named. Its Magento page states the downgrade path from Magento Enterprise to the free Community version, a question groups revisit when only some storefronts use Adobe-only features.
3 In detail
Magento's store hierarchy decides everything downstream. A website carries its own base currency, its own tax rules and, if catalog price scope is set to Website, its own prices. A store view carries language only. Groups that map every market to a store view under a single website find after go-live that they cannot set a separate currency or price per market without switching price scope, and switching it forces a full product price reindex plus a rebuild of every per-website override. Settle that flag before the first market is built.
Multi Source Inventory is the second trap. Salable quantity is derived from the stock assigned to a website, not from a global figure. If market three launches against a website with no source assigned, every product renders out of stock at once, and the cause sits in the inventory stock sales channel table, not the catalog.
Phasing also changes the migration mechanics. The magento/data-migration-tool runs from config.xml and map.xml, then tails the Magento 1 change-log triggers in delta mode. Once market one is live on Magento 2 and taking orders, another delta run can push Magento 1 rows over newer Magento 2 records. The workable pattern is to freeze delta per entity, migrate remaining markets' orders scoped by store_id, and hold customers for one final pass so account records are never split across two systems.
Redirects multiply per locale. scandiweb's published BUFF rollout describes more than 120K 301 redirects across 44 stores covering 59 countries and eight languages, and its Zvaigzne ABC migration over 21,000 for one estate. Build the map per old domain or locale path rather than once for the group, keep high-volume rules at the edge in Fastly VCL instead of loading the url_rewrite table, and re-point hreflang in the same release as each cutover so live markets stop advertising a decommissioned locale.
Then the operational layer. Each store view gets its own catalogsearch_fulltext index in OpenSearch, so index size and reindex duration scale with locale count rather than catalog size. Cron and consumer queues run per installation, so a staggered rollout leaves Magento 1 and Magento 2 both writing to the ERP for weeks: name the authoritative system per field for that overlap. Pick the patch level that outlives the program. Adobe Commerce 2.4.6 left regular support on 11 August 2026 with extended support to 31 August 2027, 2.4.7 runs to 31 May 2027, and 2.4.9, released 12 May 2026, has regular support to 31 May 2029.
4 Questions
A multi-market Magento migration is usually phased, with one pilot market proving the store hierarchy, ERP sync and redirect map before the rest follow. Big bang fits estates where every market shares one catalog, one currency and one payment provider. Phasing costs weeks of Magento 1 and Magento 2 running in parallel, which means naming an authoritative system for each field during that overlap.
Magento websites, not store views, carry base currency, tax rules and website-scoped prices. Countries needing a separate currency, separate VAT treatment or separate pricing each need their own website; countries sharing all three can sit as store views under one website with language as the only difference. Draw that tree before development, because changing catalog price scope later forces a full price reindex.
Country storefronts each carry their own redirect map, and the volume is what surprises teams. scandiweb's published BUFF case study describes more than 120K 301 redirects across 44 stores covering 59 countries, and its Zvaigzne ABC study over 21,000 for a single estate. Re-point hreflang in the same release as each market's cutover so live markets stop advertising a decommissioned locale.
Adobe Commerce 2.4.6 left regular support on 11 August 2026, with extended support running to 31 August 2027. Version 2.4.7 has regular support to 31 May 2027 and 2.4.8 to 31 May 2028. Version 2.4.9, released 12 May 2026, has regular support to 31 May 2029, the only target that outlives a rollout stretching across several markets and quarters.
Price and stock ownership needs one named system per field before any market launches. Wagento states on its own site that "Your ERP is the source of truth" and reports 6 ERP platforms integrated. Inside Magento the answer depends on catalog price scope and Multi Source Inventory: salable quantity comes from the stock assigned to each website, so an unassigned source shows a whole market as out of stock.
Timelines for multi-market Magento migrations track locale count more closely than catalog size, because content, redirects and search indexes multiply per store view. Two published reference points: scandiweb's OM System build covered 70 store views and 20 languages in 5 months from design sign-off to go-live, and its Laderach Hyva project went live 6 months after the initial meeting.