Magento to Shopify migration for UK retailers who cannot afford to lose a single ranking

What does a Magento to Shopify migration actually move?

A Magento to Shopify migration moves five things: your catalogue, your customers, your order history, your content, and your search equity. The first four are data; the fifth is the value Google has attached to your old URLs over years, and it only survives if every URL is redirected properly.

The catalogue is the biggest job. Magento stores products as a web of entities and attributes (the EAV model), with configurable parents, simple children, attribute sets, tier prices and customer-group prices. Shopify is flatter: a product has up to three options, a set of variants, and metafields for everything else. Getting from one to the other is a translation exercise, not a copy.

Customers come across with names, emails, addresses, tags and marketing consent. Orders follow, linked to those customers and products. CMS pages, blog posts and static blocks are rebuilt as Shopify pages, blog articles and theme sections. Reviews usually move through the review app you choose on Shopify.

What does not move automatically: customer passwords, gift card balances unless handled deliberately, Magento-specific logic in extensions, and any custom checkout behaviour. We list those in the quote so nothing surprises you on launch day.

• Catalogue: products, variants, images, alt text, categories as collections, attributes as metafields or tags
• People: customer records, addresses, consent flags, customer groups as tags
• History: past orders with line items, totals, tax and fulfilment status
• Content: CMS pages, blog, FAQs, size guides, delivery and returns pages
• Search equity: URL redirects, meta titles, meta descriptions, canonical structure

Is moving from Magento to Shopify worth it for a UK retailer?

For most small and mid-sized UK retailers, yes: a Magento to Shopify migration swaps server patching, extension conflicts and developer retainers for a hosted platform where security updates and uptime are someone else’s problem. The trade-off is less control over checkout and a monthly app bill.

Magento still suits merchants with genuinely complex B2B pricing, heavy customisation, or in-house developers who like owning the stack. If that is you, staying put and upgrading may be cheaper than moving. Adobe’s published lifecycle policy shows Adobe Commerce 2.4.6 reached the end of extended support on 11 August 2026, and 2.4.7 leaves standard support on 31 May 2027, so a Magento 2 store on an older release faces an upgrade project either way.

Magento 1 stores are a different conversation. Magento 1 no longer receives official security patches, so anyone still trading on it carries risk every day. For those retailers the question is not whether to move but where to, and Shopify is often the shortest path.

Magento 1 to Shopify vs Magento 2 to Shopify: what is different?

Both paths end in the same place, but Magento 1 migrations tend to need more cleaning. Older stores often carry duplicate attributes, orphaned products, broken images and customer records with invalid emails collected before modern validation.

On Magento 1, we usually pull data straight from a database export because the old API is slow and extensions may have altered tables. On Magento 2, the REST API is reliable enough for most extracts, and we fall back to database reads only for custom tables. Either way, we work from a copy, never from your live database.

URL structure differs too. Magento 1 stores frequently have category paths baked into product URLs (for example, a product appearing under three category paths), which means three old URLs point to one new Shopify product. Magento 2 stores with the “use categories path for product URLs” setting switched on have the same issue. The redirect map has to catch every variation.

Magento 2 stores with Page Builder content need extra time, because that layout markup does not render on Shopify. We rebuild those pages as theme sections so your team can edit them without code.

Whichever version you run, the planning is the same: a full export, a data audit, a mapping document you approve, then scripted imports into a development store you can click through before anything goes live.

How are Magento products, attributes and variants mapped to Shopify?

Magento configurable products become Shopify products with variants; simple products standing alone stay as single-variant products; bundles and grouped products need a decision. That decision is the heart of product mapping, and it is where cheap migrations quietly lose data.

Shopify allows up to three options per product (for example size, colour and material). A Magento configurable product with four configurable attributes has to be split, or one attribute has to move into a metafield or a separate product. We flag every product that breaks the rule before import, so you choose the fix rather than discovering it afterwards.

Custom attributes such as fabric composition, care instructions, dimensions or compatibility lists become metafields, which the theme can display and filters can use. Attribute sets inform which metafield definitions each product type receives. Tier and group pricing usually moves to a pricing app or to Shopify’s B2B features where your plan includes them.

Images keep their filenames where possible and get their alt text copied across, because image search traffic matters to fashion, homeware and gift retailers. SKUs, barcodes, weights and stock levels carry over per variant.

• Configurable product → Shopify product with up to three options and its variants
• Simple product with no parent → single-variant product
• Bundle product → bundle app or a curated kit product with its own SKU
• Grouped product → collection or a product with linked recommendations
• Virtual or downloadable product → digital delivery app or a non-shipping product
• Custom attribute → metafield definition, or a tag where it only drives filtering

Can customer accounts and passwords move from Magento to Shopify?

Customer records move; passwords do not. Shopify’s own help centre states that because passwords are encrypted outside Shopify, you cannot migrate them using a CSV, and that you need to invite customers to create new passwords after import.

That invite is a moment to handle with care. Sent carelessly to your whole list on one morning, it looks like phishing and trips spam filters. We usually recommend a staged invite, or no mass invite at all: customers set a password the next time they log in or check out, with a clear banner explaining the new store.

Marketing consent needs the same care. Shopify’s customer import includes an “Accepts Email Marketing” field, and we populate it only from records where Magento holds a genuine opt-in. Under PECR, which the ICO enforces, marketing emails and texts need consent or a valid soft opt-in, so guessing is not an option. Your privacy notice and consent wording are yours to confirm with your own adviser; our job is to carry the flags across faithfully.

Customer groups (trade, wholesale, VIP) become customer tags, which Shopify discounts, pricing apps and email tools can target. Store credit balances and loyalty points are handled by the app that replaces your Magento loyalty extension, imported from a separate export.

Can you migrate order history from Magento to Shopify?

Yes, historical orders can be imported into Shopify, and Shopify’s migration guidance says to import products first, then customers, then orders, so each order links to the right product and person. We follow that order in every Magento to Shopify migration.

How much history you bring is a business decision. Some retailers want everything so customer service can answer “what did I buy last Christmas?” Others bring two or three years and keep a read-only archive of the rest in a spreadsheet or database export. More history means longer import runs and more testing, so it affects the quote.

Imported orders are records, not live transactions. They will not trigger emails, charge cards or reduce stock, and we make sure notifications are switched off during the run. Tax lines, discounts and shipping totals carry across so reports make sense, though Shopify’s analytics will treat imported orders differently from native ones.

For VAT records, your Magento invoices and credit notes stay the authoritative copy for past periods. Keep a full export somewhere safe before the old store is switched off; HMRC expects business records to be retained, and your accountant will tell you exactly how long for your situation.

How do you keep SEO rankings after a Magento to Shopify migration?

You keep rankings by redirecting every indexed Magento URL to the most relevant Shopify URL with a permanent 301, preserving titles and descriptions, and watching Search Console closely after launch. Google’s site move documentation recommends server-side permanent redirects and advises keeping them “for as long as possible, generally at least 1 year.”

Shopify forces its own URL patterns: products live under /products/, collections under /collections/, pages under /pages/. Almost every Magento URL changes, which is why the redirect map is the single most important document in the project. We build it from a crawl of the live store, your XML sitemap, Search Console’s page report and Google Analytics landing pages, so URLs that earn links but sit outside the sitemap are not missed.

Shopify’s help centre notes two rules that shape the work. Redirects only fire from broken URLs (those returning a 404), and a standard store can hold up to 100,000 redirects, with Plus stores allowed far more. For most UK retailers 100,000 is plenty, but stores with layered-navigation URLs indexed by the thousand need pruning first.

Google also warns that rankings may fluctuate while it recrawls a moved site. A clean map shortens that wobble; it cannot remove it entirely. Anyone promising zero movement is guessing.

• Crawl the live Magento store and export every indexable URL
• Merge with sitemap, Search Console and analytics landing-page data
• Map products, categories, CMS pages and blog posts one to one
• Send discontinued products to the closest collection, not the homepage
• Import redirects in bulk to Shopify and test a sample of each type
• Submit the new sitemap and watch the page indexing report daily for four weeks

Recreating UK VAT and delivery rules on Shopify

UK VAT and delivery rules have to be rebuilt by hand in Shopify; they do not come across in any migration export. GOV.UK lists three VAT rates: the standard 20% for most goods and services, a reduced 5% for items such as children’s car seats and home energy, and 0% for zero-rated goods such as most food and children’s clothes.

Most UK shops price tax-inclusive, so Shopify is set to include VAT in prices. Zero-rated lines (children’s clothing, books, many foods) need a product-level tax override, and mixed baskets must calculate correctly at checkout. We rebuild these overrides from your Magento tax classes and check them against a sample of real past invoices. Your accountant signs off the mapping; we do not advise on which rate applies to a product.

Delivery rules are usually messier than retailers remember. Magento stores often use table-rate shipping with surcharges for the Scottish Highlands and Islands, Northern Ireland, the Channel Islands and the Isle of Man. On Shopify these become shipping zones, weight or price-based rates, and sometimes a carrier-calculated rates app. Click and collect and local delivery are native features we configure if you use them.

If you sell to the EU or further afield, duties and import taxes add another layer. We set up Shopify Markets for currencies and duty display, and your adviser confirms the tax registrations behind it.

Replacing Magento extensions with Shopify apps

Every Magento extension gets one of four outcomes: replaced by a native Shopify feature, replaced by an app, rebuilt as a small custom app, or retired. We make that list in the first week, because extensions are where migration budgets drift.

Start with an honest audit. Stores that have run Magento for years often carry extensions nobody uses any more, left installed because removing them felt risky. Those simply disappear. Features that are now native on Shopify (discount codes, gift cards, basic product reviews on some plans, abandoned checkout emails, multi-currency through Markets) need no app at all.

The rest are matched to apps. Common Magento modules for layered navigation, one-step checkout, advanced search, product feeds, email capture and loyalty all have Shopify equivalents. We check each candidate app for UK support, GBP billing, how it stores data, and what happens to your data if you uninstall it later.

Occasionally nothing fits: a trade-price calculator, a made-to-measure configurator, or a nightly stock sync with a supplier’s portal. Those become small custom apps or automations. We quote them separately so you can decide whether the feature earns its cost.

A tip from the planning side: every app adds a monthly fee and some script weight to the storefront. We aim for the fewest apps that cover your real needs, and measure page speed with and without each one.

How long does a Magento to Shopify migration take?

A typical Magento to Shopify migration takes 4–8 weeks from signed quote to cutover. A catalogue of a few hundred simple products with a stock theme sits at the short end; thousands of configurable products, a custom theme and several integrations push towards eight weeks or beyond.

The calendar is shaped less by coding than by decisions and testing. Mapping sign-off, extension choices and content approval depend on your team’s availability. Test imports need to run more than once, because the first run always reveals data issues nobody knew about.

We plan backwards from a cutover date you choose, then add slack. If a hard deadline exists (a lease ending on your Magento hosting, a busy season approaching) tell us on the first call and we will say honestly whether it is realistic.

• Week 1: export, data audit, extension list, redirect crawl
• Week 2: mapping document approved, Shopify development store set up
• Weeks 2–4: theme build or refresh, first full test import
• Weeks 4–6: VAT, delivery, apps, integrations, second import, redirect import
• Final week: content freeze, delta import of new orders and customers, DNS switch, launch checks

How much does a Magento to Shopify migration cost in the UK?

With BtechWaleTech, a full Magento to Shopify migration starts at US$750, covering data mapping, scripted imports, redirects, UK VAT and delivery setup, and launch support. Quotes from UK agencies and freelancers vary widely, and the gap usually comes down to scope and who does the work, not magic.

The drivers are predictable. Catalogue complexity matters more than raw product count: 5,000 simple products migrate faster than 800 configurable products with four attributes each. Custom attributes, bundles, multi-store views and customer-group pricing add mapping time. Order history adds import and testing time. A custom theme costs more than adapting a good paid theme.

Running costs change shape too. You stop paying for Magento hosting, security patching and extension licences, and start paying Shopify’s subscription, app fees and payment processing. We list the apps we propose with their current published pricing links so you can model the monthly difference yourself.

If you only need the data moved and your theme is already chosen, say so; the quote shrinks. For stock or ERP connections, our automation plan from US$600 often fits better than bundling them into the migration.

When should a UK retailer switch from Magento to Shopify?

Switch in your quietest trading weeks, never in the run-up to a peak. For most UK retailers that rules out mid-October to the end of December, the January sale window if you rely on it, and the fortnight before any sector-specific peak such as Mother’s Day for gifting shops or back-to-school for uniform suppliers.

Look at your own sales data rather than general wisdom. We ask for weekly revenue for the last two years and pick a launch window with the lowest order volume and at least two calm weeks after it, so any post-launch issues are fixed before traffic climbs.

Mid-week launches beat Friday launches. A Tuesday or Wednesday morning switch (UK time) gives a full working week to watch orders, payment captures, emails and redirects, and it overlaps with our working day in India.

The last few days before launch run a content freeze on Magento: no new products, no price changes. On launch day we run a delta import of orders and customers created since the last full import, lower the DNS TTL beforehand, switch the domain, and keep the old Magento admin available read-only for reference.

Magento to Shopify migration risks and red flags to watch for

The biggest risks in any Magento to Shopify migration are a thin redirect map, silently dropped product data, broken tax settings and an untested launch. Each one is avoidable with process, and each one shows up in the quote if you know where to look.

Red flags in a proposal: redirects described as “the top pages”, no mention of variants over three options, no plan for customer passwords, no test import before launch, and no named person responsible for Search Console after go-live. Be wary too of anyone promising rankings will not move; Google itself says they may fluctuate.

Red flags in your own data: thousands of indexed filter URLs, products with no SKU, duplicate customer emails, and categories that exist only to hold one product. We surface these in the audit so you decide what to clean before rather than after.

One more risk people underestimate: email deliverability. A new platform sends order emails from new servers. We set up the sending domain’s DNS records in Shopify so confirmations land in the inbox, and if your old store had deliverability problems, we check those records while we are there.

Working with a remote team in India on your Magento to Shopify migration

India runs four and a half hours ahead of the UK during British Summer Time and five and a half hours ahead in winter, so our working day overlaps with yours from UK late morning into the evening. Imports and heavy test runs happen during your night, and results are waiting in the morning.

Calls happen on Google Meet, Zoom or Teams, whichever you already use. Day-to-day questions go through WhatsApp, which we answer seven days a week, and larger decisions are written up so there is a record. We do not make site visits and have no UK office; everything runs remotely, which for a migration is no handicap, because the work lives in your Magento and Shopify admins anyway.

Payment is in USD against a written, itemised quote, payable from GBP by Wise, bank wire or PayPal. Invoices come from India; your accountant can advise on how to treat them. Your Shopify store, domain, apps and any migration scripts are created in or transferred to your accounts. You add us as collaborators and can remove access the day the project ends.

Worked example: a hypothetical Magento 2 homeware shop in Harrogate

Say a homeware retailer in Harrogate runs Magento 2.4.6 with about 2,400 products, 700 of them configurable (colour and size), 38,000 customer records, eight years of orders, and eleven extensions. Organic search brings in a large share of revenue, so rankings are the owner’s main worry. This is an illustration, not a client story.

The audit finds 190 products with four configurable attributes (colour, size, finish, pack quantity). The owner decides pack quantity becomes separate products, keeping each under Shopify’s three-option limit. Four extensions are unused and retired, three map to native Shopify features, three to apps, and one (a trade-price calculator for interior designers) becomes a customer-tag discount instead of custom code.

The crawl finds 14,500 indexable URLs, including 6,000 filter URLs that should never have been indexed. Those are pruned; the remaining 8,500 get one-to-one redirects. Five years of orders are migrated; the rest go into an archived export. Customers receive no mass invite; a banner explains the new login.

Launch is booked for the second Tuesday of February, after the January sale and well before Mother’s Day. The timeline lands at about seven weeks, and the quote sits above the ecommerce plan’s starting price of US$750 because of the catalogue work and redirect volume.

Magento to Shopify migration checklist

Use this checklist before you sign with anyone, and again in the week before cutover. Each item is something we have seen skipped in migrations planned in a hurry.

• Full Magento database and media export stored somewhere you control
• Crawl of every indexable URL, merged with Search Console and analytics data
• Mapping document approved: products, variants, attributes, customers, orders
• Products with more than three options identified and resolved
• Customer marketing consent carried only where a genuine opt-in exists
• Extension list with each one marked native, app, custom or retired
• VAT overrides and delivery zones tested with sample baskets
• Order, shipping and refund emails branded and tested for inbox delivery
• Redirects imported and a sample of every URL type tested
• Content freeze agreed and delta import planned for launch day
• Launch booked in a quiet trading week, mid-week, UK morning
• Search Console, sitemap and analytics tracking verified on the new store

If you would rather have someone else own that list, send us your store URL and a rough product count, and we will reply with questions before we quote.