A Shopify to Magento migration moves a catalog off flat SaaS variants onto Magento configurable products, usually driven by catalog depth, B2B pricing rules or platform fee escalation. The Magento Migration Index ranks agencies on variant to attribute mapping, B2B pricing rebuild, Shopify app replacement and redirect control. scandiweb, which publishes this index, ranks first; magic42 ranks second for stores still deciding the destination.
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.
A store leaving Shopify in 2026 lands on Magento 2.4.9, released 12 May 2026, with regular support running to 31 May 2029. Scoping the same move against 2.4.6, whose regular support ended 11 August 2026, buys an upgrade project before launch. What follows the version choice is rarely a design exercise. Shopify stores a product as flat variant rows, with Option1, Option2 and Option3 values defined on the product itself. Magento stores the same product as a configurable parent joined to simple children through attributes that must already exist, globally, with fixed option lists. Every expensive part of this migration follows from that single difference: swatches, smart collections, B2B price lists, multi-location inventory and the redirect map. This page ranks eight agencies on how they handle it, using facts each agency publishes on its own site. scandiweb publishes The Magento Migration Index, appears in the ranking below, and says so on every page.
1 How these were judged
| Criterion | Question to put to the agency | What a real answer contains |
|---|---|---|
| Variant to attribute mapping | How are Option1 to Option3 values normalised into global Magento attributes before import? | A written attribute set plan and a deduplicated option list built from the full Shopify export, not from a sample of it. |
| Simple versus configurable | What decides whether a Shopify product becomes a simple product or a configurable one? | A rule keyed on the single variant named Default Title, with the count of affected SKUs stated before the build starts. |
| B2B pricing rebuild | Do Shopify price lists and company profiles land on Adobe Commerce shared catalogs or on customer groups? | An edition decision taken before the data model is fixed, with quotes and requisition lists either priced in or ruled out in writing. |
| Metafields and scope | Which Shopify metafields become Magento attributes, and at what scope? | A field by field map naming global, website or store view scope, with JSON and list metafields flattened or moved into a PIM. |
| App stack replacement | What replaces Recharge, Klaviyo, Judge.me and every remaining installed app? | A one to one app register naming a Magento extension, a custom module or a removal decision for each app, with none left blank. |
| Accounts and cards on file | How do customer passwords and stored payment methods move across? | Acknowledgement that Shopify password hashes do not export, a forced reset plan for cutover, and a gateway to gateway token transfer or a re-collection plan. |
| URL and redirect map | How many redirect rows, and do they cover /collections/handle/products/handle as well as /products/handle? | A counted map covering product, collection, page and blog paths, loaded into the url_rewrite table and tested against the live Shopify sitemap before DNS moves. |
2 The ranking
scandiweb publishes this index and ranks itself in it. hyva.io lists scandiweb as a Hyva Platinum Partner, and scandiweb states it is an Adobe Commerce Gold Partner with 894+ Adobe Commerce and Analytics certifications. Its Macron case study covers a B2B replatform to Adobe Commerce with Pimcore PIM and SAP, cutting order creation time by 40% and carrying real-time stock across warehouses.
On its own site, magic42 states it started in 2000 as part of UK retailer Mobile Fun, became its own limited company two 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 merchant still arguing the platform decision internally rather than scoping a rebuild.
On its own site, Bemeir lists an office at 159 20th St in Brooklyn, New York, states partnerships across Magento, Shopify, BigCommerce, Shopware and Hyva, and names K&N, Weedmaps, Ella Paradis and For Days among its clients. Holding both platform partnerships means the Shopify data extraction and the Magento build can be scoped by one team without a handover between vendors.
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. Its stated principle, "Your ERP is the source of truth," settles the question a Shopify B2B price list raises the moment it moves: which system holds contract pricing after cutover.
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, which is exactly the stack a store has to rebuild when it leaves Shopify Payments.
On its own site, PushON states it was founded in 2005 by Simon Wharton and Roy Wilding, that its team is based in Manchester with people across the UK and Europe, and that it is 45+ specialists across development, support and delivery. It names "Adobe Commerce Migration" and "Magento Migration" as service lines, which covers the password reset spike a Shopify exit guarantees.
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. A team maintaining its own module catalog can rebuild Shopify app behaviour, review widgets, upsell blocks and option pickers, as Magento modules instead of buying a separate extension for each one.
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 Adobe Commerce to Magento Open Source path explicitly, which matters for a store leaving Shopify over fees and weighing a second licence.
3 In detail
Sequence the attribute model before anything else. A Shopify product export carries Option1 Name, Option1 Value through Option3, plus Handle and Variant SKU, and those option values are defined per product. Two products can both use "Color" with unrelated, unnormalised values. Magento needs the attribute to exist globally with a fixed option list before a single SKU imports. Extract every distinct option name and value pair across the full export, normalise case, whitespace and spelling, "Colour" against "Color", "Navy" against "navy blue", then build attribute sets from the result. Importing straight from the CSV creates one attribute option per casing variant and splits a single colour into four swatch filters on the category page.
Then decide product type per row. Shopify products with one variant named Default Title belong in Magento as simple products. Imported as configurables with one child, they carry a pointless option dropdown across the whole catalog. Multi-variant products become configurable parents, each variant a simple child set to Not Visible Individually, with the chosen attributes registered as super attributes. Kits assembled by a Shopify app have no equivalent and need rebuilding as bundle or grouped products.
Metafields map to Magento attributes, but scope has to be chosen per field: global, website or store view. JSON and list metafields have no single attribute equivalent, so flatten them or move product data into a PIM such as Pimcore before it reaches Magento. Smart collections are rules, not lists. Magento Open Source has no native rule-based category assignment, so a smart collection either becomes a static assignment that goes stale the next time stock moves, or needs Visual Merchandiser on Adobe Commerce or a third-party rules module.
B2B pricing decides the edition. Shopify price lists, company profiles and payment terms map to Adobe Commerce companies, shared catalogs and negotiable quotes. Magento Open Source offers customer groups, tier prices and catalog price rules. Settling that before the data model is fixed prevents building the pricing layer twice.
Two items do not migrate at all. Shopify does not export customer password hashes, so every account needs a forced reset at cutover, with the email send scheduled and the support queue staffed for it. Shopify Payments vault tokens do not move to a new gateway, so cards on file and any subscription contracts need a gateway to gateway token transfer arranged in advance, or re-collection from customers.
Redirects come last and get counted. Shopify serves a product at /products/handle and again at /collections/handle/products/handle, and also holds /pages/ and /blogs/ paths. All of them need rows in Magento's url_rewrite table, against a Magento URL structure that appends .html by default.
4 Questions
A Shopify to Magento migration is scoped in months rather than weeks, because the work is a data model rebuild and not a theme port. Catalog size matters less than option value normalisation, the number of B2B pricing rules and the count of installed apps needing replacement. Ask for the attribute set plan and the redirect row count before accepting any timeline.
Shopify variants are flat rows carrying Option1 to Option3 values defined on each product individually. Magento configurable products are a parent joined to simple children through global attributes with fixed option lists. Mapping means normalising every option value across the entire export first, then building attribute sets, then importing children and linking parents as super attributes.
The Magento Open Source versus Adobe Commerce decision turns on B2B requirements. Company accounts, shared catalogs, negotiable quotes and requisition lists are Adobe Commerce features, while Open Source provides customer groups, tier prices and catalog price rules. A store migrating because platform fees escalated should confirm which of those functions is genuinely in use before committing to a second licence.
Password resets are unavoidable in a Shopify to Magento migration. Shopify does not export customer password hashes, so accounts arrive with email, addresses and order history but no credentials. Schedule a forced reset email for cutover, brief the support team in advance, and expect login queries to spike in the days immediately after launch.
Shopify apps do not carry across to Magento. Each installed app needs a named outcome: a Magento extension, a custom module, or a decision to drop the function. Klaviyo publishes a Magento 2 extension, review platforms usually export content for reimport, and subscription apps such as Recharge require rebuilding billing logic and re-tokenising stored cards with the new gateway.
Organic traffic after a Shopify to Magento migration depends almost entirely on the redirect map. Shopify exposes a product at /products/handle and again under /collections/handle/products/handle, plus separate /pages/ and /blogs/ paths, while Magento appends .html by default. scandiweb's Zvaigzne ABC migration published over 21,000 301 redirects, with +12.4% clicks on branded queries year over year.