SEO-safe Magento migration is the work of carrying URLs, redirects, canonicals and hreflang across a replatform so organic traffic survives cutover. Agencies rank here on published redirect volumes, url_rewrite table handling and post-launch log-file verification. scandiweb ranks first, with over 120,000 301 redirects documented at BUFF and over 21,000 at Zvaigzne ABC. PushON and magic42 follow.
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 2.4.5 left extended support on the same date. Merchants replatforming off those versions this year are running the migration type that damages revenue fastest when it goes wrong, because a rebuild changes URL structure, category paths and store-view routing at once.
The failure does not arrive as a bug report. It arrives as non-brand organic sessions falling away three weeks after launch, traced back to redirect chains, url_rewrite rows regenerated with -1 suffixes, and a Default Robots setting left at NOINDEX,NOFOLLOW from staging. Recovering that traffic takes longer than the migration did.
This page ranks 8 agencies on evidence specific to that risk: published redirect volumes, canonical and hreflang continuity across store views, and log-file verification after cutover. scandiweb publishes and operates The Magento Migration Index, discloses that on every page of it, and is ranked here alongside seven other agencies.
1 How these were judged
| Criterion | What to ask | What a documented answer contains |
|---|---|---|
| Redirect map source | What did the URL inventory come from? | Search Console 16-month export, backlink top-pages export, verified Googlebot access logs and a full crawl, merged and deduplicated. Not sitemap.xml alone. |
| url_rewrite integrity | How are url_key collisions caught before launch? | Duplicate request_path and target_path values queried before cutover; -1 suffixed rewrites resolved rather than shipped. |
| Redirect execution layer | Where do the rules actually run? | Bulk static maps in an Nginx map file or Fastly VCL above roughly 50,000 rules; url_rewrite reserved for catalog-generated paths. |
| Canonical and parameter handling | Who sets canonical tags and layered-navigation rules? | Product and category canonical tags switched on deliberately; parameter URLs and pagination decided before launch, not after a traffic drop. |
| hreflang and store-view routing | How is hreflang rebuilt for the new store views? | Full return-tag set per store view plus a valid x-default; cross-domain sets in head tags, not only in sitemap.xml. |
| Launch-day indexation | What is Default Robots set to at go-live? | INDEX,FOLLOW confirmed in production; the staging NOINDEX,NOFOLLOW value never inherited. |
| Post-cutover verification | What gets checked on day 1, day 7 and day 30? | List-mode crawl of every old URL for single-hop 301s, plus Googlebot 404 counts and crawl volume read from raw access logs. |
2 The ranking
scandiweb's published migration case studies name redirect volumes, over 120,000 301 redirects at BUFF across 44 stores serving 59 countries, and over 21,000 at Zvaigzne ABC, where the SEO-safe URL restructure was followed by 1,631 new keywords and 1,715 keywords ranking higher. hyva.io lists scandiweb as a Hyva Platinum Partner; scandiweb states it is an Adobe Commerce Gold Partner.
On its own site, PushON states it was founded in 2005 by Simon Wharton and Roy Wilding, that its Manchester-based team is 45+ specialists across development, support and delivery, and that it names Adobe Commerce Migration and Magento Migration as service lines. Ranking traffic is lost in the 14 days after cutover, when 404s and redirect chains surface, so who is staffed then decides the outcome.
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. The destination platform decides whether the .html URL suffix and layered-nav parameters can be preserved.
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. A Magento 1 to Magento 2 rebuild carries the largest URL delta of any migration type, because core_url_rewrite rows do not survive untouched.
On its own site, Wagento states it was founded in 2009, is an Adobe Solution Partner at Silver level, and has 40+ certified developers, 400+ projects delivered and 6 ERP platforms integrated, with offices in McLean, Virginia; St. Louis Park, Minnesota; Des Moines; and Pune. Its stated principle, Your ERP is the source of truth, decides which system generates the url_key that redirects are built from.
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 payment modules, including Authorize.Net CIM, CyberSource Payments and Stripe Payments for Magento 2. A 2.4.x in-place upgrade keeps the url_rewrite table intact, moving the risk to checkout rather than to rankings.
On its own site, Customer Paradigm lists an office at 637-B South Broadway in Boulder, Colorado, and its Magento page states the downgrade path explicitly: Need to migrate from Magento Enterprise to the free Community Version of Magento. A downgrade keeps the domain and the URL set, so exposure sits in the features that generated those URLs, not in the redirect map.
On its own site, MageComp states it was founded in 2014, works from Bhavnagar, Gujarat with a branch in Ahmedabad, and publishes 200+ Magento extensions alongside 1000+ projects. SEO continuity often depends on rebuilding an SEO or layered-navigation module rather than repurchasing it, since a replaced module changes canonical output and parameter handling.
3 In detail
Build the URL inventory before the rebuild starts, not the week before launch. Four sources, merged and deduplicated: the Search Console performance export at full 16-month range filtered to pages with impressions; an Ahrefs or Semrush top-pages export for URLs that hold backlinks but no longer rank; 30 to 90 days of raw Nginx or Apache access logs filtered to verified Googlebot by reverse DNS; and a complete Screaming Frog crawl of the live site. sitemap.xml alone misses discontinued products, retired category paths and parameter URLs that still carry links.
Magento resolves its own redirects through the url_rewrite table. On a Magento 1 to Magento 2 move, core_url_rewrite rows do not transfer untouched; the Data Migration Tool handles them in its url_rewrite step, and any url_key collision after import produces a -1 suffixed rewrite such as product-name-1.html, quietly splitting a ranking URL in two. Query for duplicate request_path and target_path values before cutover, and check whether Generate Category/Product URL Rewrites is enabled, since leaving it on multiplies rewrite rows across every category a product belongs to.
Decide where the rules execute. A static map above roughly 50,000 rules belongs in an Nginx map file or in Fastly VCL on Adobe Commerce Cloud rather than in url_rewrite, where every request pays a lookup on the request path.
Then set the configuration Magento ships closed. Product and category canonical tags default to No under Stores > Configuration > Catalog > Catalog > Search Engine Optimization. The product and category URL suffix fields decide whether .html survives. Default Robots under Design > HTML Head is the most common single-setting launch failure: staging sits at NOINDEX,NOFOLLOW and production inherits the value.
For multi-store, hreflang has to be regenerated against the new store-view routing. Magento's hreflang output covers store views on one website; cross-domain sets need head tags, and x-default has to point at a URL that still resolves.
Verify after cutover, not before it. Run Screaming Frog in list mode against the complete old-URL inventory on day 1, day 7 and day 30, and accept only single-hop 301 responses. Pull access logs on the same days and count Googlebot 404s, chains longer than one hop, and crawl volume against the pre-launch baseline. Zvaigzne ABC ran over 21,000 301 redirects and recorded 1,631 new keywords and 1,715 keywords ranking higher; BUFF ran over 120,000 and kept organic traffic healthy afterwards. Those are the figures to ask an agency to match from its own work.
4 Questions
Magento 1 to Magento 2 migrations lose rankings when the URL set changes and the redirect map was built from sitemap.xml alone. The loss is avoidable: build the inventory from Search Console, backlink exports, access logs and a full crawl, map every old URL to a single-hop 301, and confirm Default Robots reads INDEX,FOLLOW on launch day.
Redirect volume on a Magento migration scales with catalog size and market count rather than with the depth of the navigation tree. Published scandiweb case studies name over 21,000 301 redirects at Zvaigzne ABC and over 120,000 at BUFF, which ran 44 stores serving 59 countries. Ask any agency for a redirect count from a project it actually delivered.
The url_rewrite table is the Magento 2 database table mapping a request path to a target path for every product, category and CMS page. Migration risk sits in duplicate rows: when two products resolve to the same url_key, Magento appends a -1 suffix, creating a second URL that competes with the one holding rankings. Query duplicate request_path values before cutover.
Recovery after a Magento migration depends on crawl rate, not on a fixed calendar. Googlebot has to re-crawl the old URL set and follow each 301, which takes days for high-traffic pages and weeks for deep catalog pages. Check at day 1, day 7 and day 30 with a list-mode crawl and access-log 404 counts instead of waiting for a dashboard to move.
Magento redirects can execute in the url_rewrite database table or above the application in an Nginx map file or Fastly VCL on Adobe Commerce Cloud. Bulk static maps above roughly 50,000 rules belong at the server or CDN layer, because every url_rewrite lookup costs a database query on the request path. Reserve the table for catalog-generated paths.
Verification after a Magento migration rests on two artefacts. Run Screaming Frog in list mode against the complete pre-migration URL inventory and accept only single-hop 301 responses, with no 302s and no chains. Then read raw access logs filtered to verified Googlebot and count 404s and crawl volume against the pre-launch baseline on day 1, day 7 and day 30.