Shopify migration
Magento to Shopify, without losing what you have earned.
Adobe Commerce and Magento Open Source. Attribute sets, configurable products, customer history and SEO redirects planned before DNS moves.
Magento and Adobe Commerce stores often carry years of catalogue complexity, custom modules and URL patterns that Google already knows. A Magento to Shopify migration has to protect those assets while giving your team a store they can actually run.
We map attribute sets and configurable products into Shopify variants and metafields, move customers and order history, and build one-to-one 301 redirects before cutover. The new storefront and any ERP links sit in the same plan.
Magento to Shopify migration checklist
Why people leave Magento
Magento 1 is long past end of life. Security patches stopped. Hosting it now means carrying a platform Adobe no longer supports, with plugins that break when PHP moves on.
Adobe Commerce licence renewals are the other push. The fee rises, and the store still needs a developer for changes a merchandiser should make alone. Teams leave when the renewal no longer matches what the store earns.
Hyvä is the third path people consider. It makes the Magento front end faster, and it is a real option if you are staying. It does not remove the licence, the upgrade cycle or the cost of keeping custom modules alive. If the plan is a store the team can run, Shopify is usually the cleaner exit.
The move is rarely about the theme. It is about attribute sets nobody trusts, checkout code only one agency understands, and a release process that makes a banner change feel like a project.
What breaks in the data
Attribute sets
Magento's EAV model stores attributes per product type. Shopify wants options, variants and metafields. A blind export either drops detail or creates a variant explosion. We redesign the model before products move.
Configurable products
Colour and size that lived as separate simple products have to become one Shopify product, or stay as listings if that is how customers search. The choice is made per range, not as a single rule.
Customer passwords
Hashes from Magento do not become Shopify passwords. Order history and addresses can move. Returning buyers need an activation path so they are not locked out on day one.
URLs and .html suffixes
Nested Magento paths and .html endings already rank. Each important URL needs a one-to-one 301. A blanket redirect to the homepage throws away the equity you paid for.
Timeline and cost
Weeks 1 to 2
Audit the catalogue, the modules that actually run the business, and the URLs that earn traffic. You get a written map before we move a product.
Weeks 3 to 6
Products, customers and orders land in a staging store. Metafields, collections and the theme are built against that data, not against a guess.
Weeks 6 to 8
Redirects, account activation and checkout are rehearsed. ERP or warehouse links are tested with real orders.
Cutover
A quiet trading window. DNS moves after the redirect file is live. We watch Search Console and 404s through the first days.
Migrations and builds typically run £20,000 to £35,000, plus a monthly retainer. A smaller catalogue with a clean export sits at the lower end. Wholesale, an ERP and years of messy data sit at the higher end. We confirm the range after we have seen the store.
How the project runs
We start on the licence and the version, not the theme. Magento 1, Magento 2 and Adobe Commerce do not export the same way. Hyvä, if it is in flight, is a decision about budget. It is not a reason to skip the data map.
Attribute sets are redesigned in a sheet the merchandiser can read. Configurable products are split or combined per range. Customer passwords are called out as something that will not move, so the activation email is written before launch week.
Redirects are built from a crawl, including .html paths that still have impressions. The ERP or warehouse feed is tested with an order, not with a diagram. Cutover is a quiet window, and Search Console is watched for the first days rather than the first hour.
Fáilte Foods is the wholesale example we publish. Magento to Shopify Plus, with Business Central. We do not paste that result onto a different catalogue. Your range gets its own map.
Checklist
- List Magento 1, Magento 2 or Adobe Commerce, and the licence renewal date.
- Export attribute sets and decide what becomes a variant, a metafield or a collection.
- Crawl every URL that has impressions, including .html paths.
- Plan account activation, because passwords will not move.
- Name the ERP or warehouse system and what must stay in sync on day one.
- Decide whether Hyvä work stops, or whether that budget moves into the Shopify theme.
- Rehearse checkout, tax and the top ten landing pages before DNS changes.
What makes a Magento migration different
Attribute sets and configurables
Magento's EAV model does not map one-to-one to Shopify. We redesign options, metafields and listing rules so the catalogue stays clear.
URL structure and SEO
Nested Magento paths and .html suffixes need explicit redirects to Shopify product and collection URLs. We crawl, map and test before launch.
Customer continuity
Passwords often cannot move. We plan account activation so returning buyers keep their history and can order again without friction.
How it runs
01
Audit
We inspect the current platform, catalogue health, traffic URLs, integrations and what regular customers rely on.
02
Map
Data fields, URL redirects and cutover risks get written down. You see the plan before we move a product.
03
Migrate
Catalogue and customers move into staging. Structure is cleaned. Integrations and the storefront come together.
04
Rehearse
Redirects, accounts, checkout and the top landing pages are tested. Cutover is practised, not hoped for.
05
Launch and watch
Go live on the agreed window. We monitor Search Console, 404s and the first trading days with you.
Also in the move
Design and build
The new storefront, product structure and content templates that make the migration worth doing.
Apps and integrations
ERP, 3PL and the tools around the store, connected so stock and orders stay true after cutover.
Ongoing support
Monitoring and improvements once the new platform is live. Month to month, no lock-in.
Magento to Shopify questions
Can you migrate Magento 1 and Magento 2?
Yes. Magento Open Source, Magento 2 and Adobe Commerce. The data shape changes, but the standard stays the same: clean catalogue, protected URLs, continuous customers.
Will Magento SEO rankings survive?
They can, when redirects are one-to-one and live before DNS changes. We inventory the important URLs, map them, and watch Search Console after go live.
Other platforms
Talk about your Magento move
Send the store URL and what you are most worried about losing. We will tell you what to protect first.
Prefer a call? Book a call.