A Shopify migration runs in three phases. Before migration, define the scope, audit the existing store, identify your highest value pages, build a complete redirect map, set up Shopify as a development store, choose a theme and apps, and migrate products, customers, orders and content. During migration, complete the final data transfer, configure shipping and payments, test every integration end to end, implement and check the 301 redirects, and prepare a launch plan. After launch, switch the domain, remove any indexing blocks, submit the sitemap, and monitor rankings, revenue, 404s and Search Console daily for two weeks and regularly for 90 days. The 30 steps below cover each in order.
This checklist is based on our experience migrating stores from WooCommerce, Magento, Squarespace and BigCommerce. Not every item applies to every store, but working through it in order means nothing important is missed. For budgeting, see how much a Shopify migration costs, and for platform specific detail see our Magento and WooCommerce migration guides.
Phase 1 covers everything before the switch to Shopify, including a first import of your products, customers and content into the new store, so you can build and test on real data. Phase 2 completes that migration and prepares the launch.
Decide whether you are migrating the store as it is or migrating and redesigning at once. These are different projects. A straight migration moves data, recreates essential functions and protects SEO. A redesign adds UX, design, development, content and far more testing. The scope you set here largely decides the cost.
Crawl the current site with a tool such as Screaming Frog or Sitebulb and record, for each important URL, the address, status code, title, meta description, H1, canonical, internal links, organic traffic, organic revenue, backlinks and page type. Export 12 months of Search Console data, find the landing pages earning organic revenue in GA4, and list every plugin, extension and integration with what it does. This becomes both your blueprint and your baseline for checking the new store.
Sort Search Console by clicks and impressions, sort Analytics by organic revenue, and use a backlink tool or Search Console's Links report to find pages with valuable links. These pages need the most careful redirects, preserved content and checked metadata, so flag them in the redirect map.
This is the most important document in the migration and the one merchants are least likely to arrive with: of the last 80 stores we migrated, 75 had none. Every valuable old URL needs a destination. Build a spreadsheet with the old URL, new Shopify URL, page type, priority and check status.
Expect structural changes: WooCommerce's /product/ becomes Shopify's /products/, categories become /collections/, and blog paths differ. Pages without an exact equivalent should go to the closest relevant page, never to the homepage by default. In Shopify, URL redirects now sit under Content, then Menus, then URL redirects, with CSV import for large batches.
The main differences are transaction fees, reporting, staff accounts, international features and how far checkout can be customised, which goes deepest on Plus. Plan choice barely affects the migration itself but decides what is available afterwards, and B2B now runs on every plan from Basic up. Check Shopify's UK pricing for current details.
Treat the new store as a development environment while the old site keeps trading. Configure the basics early: store details, currencies, Markets, tax, shipping zones, payments, notifications and staff permissions. Do not point the live domain at it just because it looks ready; that belongs in the launch plan.
Decide between a configured Shopify theme and a custom build based on what the store needs, not on the most expensive option. Resist reproducing the old site pixel for pixel, since a migration is a chance to fix what does not work, but avoid changing everything at once, because every design change is another variable to test. Our Shopify developers can help you choose.
Do not assume every old plugin needs a Shopify equivalent. For each one, ask what it does, whether it is still needed, and whether Shopify handles it natively. This usually cuts the app count, which matters because every app adds cost, weight and another dependency. Subscription businesses may be moving to Recharge, which we are a partner of, or another Shopify compatible platform. Document every app with its purpose and cost.
Account for titles, descriptions, images, SKUs, barcodes, prices, compare at prices, stock, variants, options, collections, tags, types, vendors and SEO fields. An automated import is not a correct import: formatting breaks, variants restructure and collection relationships need recreating. Sample across categories, including your best sellers and most complex variants, and compare source and destination programmatically for missing or duplicated records.
Customer data is commercially important and covered by data protection law. Decide deliberately how much order history to bring, since customers look for past orders and the business needs them for service and reporting. Passwords usually cannot be transferred, so plan how customers will regain access and test account behaviour after import.
Blog posts, guides, landing pages and help content can carry significant traffic and links. Decide for each whether to migrate, update, merge or retire it, and make sure the redirect map covers anything removed. A migration that keeps product pages but quietly drops established articles still causes serious SEO damage.
Check titles, meta descriptions, H1s, canonicals, URLs, alt text, internal links, sitemap, robots.txt, structured data and indexing settings. Update internal links to point at new URLs rather than relying on redirects, and make sure development URLs, duplicates and filtered pages are not indexed. Structured data deserves its own check: 90% of the migrations we take on arrive with it broken or missing.
ERP, CRM, email, accounting, fulfilment, warehouse, payments, support, subscriptions, loyalty and marketplaces each need recreating, replacing or deliberately retiring, with their own test plan. If orders go to an ERP, test from checkout to the ERP receiving the order. If stock syncs, test changes in both directions.
Set up GA4, Search Console, Tag Manager, advertising pixels and Klaviyo or your email platform. Record a baseline first: organic traffic and revenue, conversion rate, average order value, paid conversions and email revenue. Then place test orders and confirm each purchase reaches every platform, because tracking failures are invisible on a store that otherwise works.
Test functions and the customer experience together:
| Area | What to test |
|---|---|
| Navigation and search | Menus, breadcrumbs, internal links, search results, filters and empty results |
| Products | Variants, prices, stock, images and options |
| Cart and checkout | Adding and updating items, shipping, payment, discounts and order completion |
| Mobile | Navigation, product pages, cart and checkout on real devices |
| Forms and emails | Contact and newsletter forms, order and shipping notifications |
| Integrations | ERP, CRM, fulfilment, marketing and analytics, end to end |
| Redirects and SEO | Old URLs, indexing, canonicals, metadata and structured data |
Use real scenarios rather than clicking around: test orders, discount codes, new accounts, out of stock items, failed payments, several shipping options and international orders. The more important the function, the harder you test it.
Before the domain switch, crawl the new store and compare it with the original. Confirm important pages return 200, redirects are in place, metadata and H1s are present, the sitemap and robots.txt are correct, internal links point to new URLs, structured data works, and nothing important is blocked. The aim is no known critical issues, not perfection.
Run a test migration first on larger stores to catch mapping and formatting problems safely. Then set a cut off on the old platform and run a final incremental migration just before launch, so there is a clear moment when Shopify becomes the source of truth.
A store can look finished with a broken checkout. Test the full journey with different payment methods, real basket combinations, free shipping thresholds, international markets and subscription checkouts, from a customer's point of view.
One order may need to reach fulfilment, update stock, send a confirmation, reach your email platform, change a customer's segments and record revenue. Each part can pass alone while the chain fails. Subscription businesses should also test creating, skipping, pausing, swapping, updating payment, cancelling and renewing.
Load the redirect map once URLs are final and crawl your old URL list against it. Each old URL should return a 301 to the right, relevant page, which returns 200, with no chains or loops. Check old campaign pages and discontinued products too, since they can still carry links.
Someone who knows the business should use the store as a customer would, on desktop and mobile, then as staff would: finding orders, updating products, processing refunds and handling service queries.
The domain switch should follow a written plan:
| Launch task | Purpose |
|---|---|
| Final data migration | Orders, customers and changes since the first migration |
| Redirects and robots.txt | Critical redirects ready, live store open to crawling |
| Analytics and payments | Tracking on the live domain, live payment settings confirmed |
| Domain and Search Console | DNS records correct, sitemap ready to submit |
| Team and rollback | Everyone knows the timing, and what happens if something critical breaks |
Launch when trading is quiet, never just before a campaign or seasonal peak, so there is time to fix surprises before demand arrives.
Once connected, retest the key journeys straight away, and test several old URLs directly, because a working homepage tells you nothing about your redirects.
Remove password protection and any indexing restrictions, check robots.txt, and submit the sitemap in Search Console. Do not try to force indexing of every page by hand; good internal links and a valid sitemap are enough.
Watch organic traffic, rankings, revenue, conversion, 404s, redirects, indexing, speed, payment failures and support tickets against your baseline. Some fluctuation is normal while search engines process the new URLs. A sharp fall across many pages, a cluster of 404s or a drop in checkout conversion needs investigating immediately, and if orders vanish from analytics, check tracking before assuming sales have fallen.
Crawl again and compare with the pre migration crawl for broken links, missing pages, chains, wrong canonicals, duplicate titles and internal links still pointing at old URLs.
Check indexing, 404s, redirect errors, sitemap processing and Core Web Vitals, paying most attention to the high value pages from Step 3. Segment by page type and category, because a stable total can hide a serious fall in one important section.
Rankings matter, but organic sessions, transactions, revenue and conversion matter more. Stable traffic with falling organic revenue means the pages attracting visitors have changed. Done well, the gains are measurable: across our migrations, PageSpeed typically improves by around 68%.
Some issues only appear after launch. Prioritise them:
| Priority | Example | Response |
|---|---|---|
| Critical | Checkout or payment failure, site outage | Investigate immediately |
| High | Redirect failures, widespread 404s, indexing problems | Fix as fast as possible |
| Medium | Broken internal links, isolated page issues | Fix during remediation |
| Low | Minor formatting or metadata gaps | Add to the backlog |
The first 90 days show how the new store really performs. It is also when to tackle what did not belong in the migration: conversion work, navigation, collection and product page improvements, and trimming unnecessary apps.
Most ranking losses after a migration come from a short list of causes, and every one of them is preventable. Google's own guidance on site moves with URL changes asks for the same things this checklist does: map every old URL to its new equivalent, use permanent redirects, update internal links and sitemaps, monitor both old and new URLs after the move, and keep the redirects in place for at least a year.
If rankings dip in the first fortnight, check these five before assuming anything else.
The migrations that go wrong are almost never the ones where something technical failed. They are the ones where something was never planned: a redirect nobody mapped, an integration nobody tested end to end, a content page nobody realised was earning traffic. The redirect map is the clearest example, and it is not a criticism that almost nobody arrives with one, because no migration tool asks for it. But it does mean the document that decides how much organic revenue survives is usually created late, under pressure, or not at all.
That is why this checklist is front loaded: sixteen of thirty steps happen before the final switch to Shopify. The other pattern worth naming is that merchants overestimate the data import and underestimate testing. Importing products is largely automated. Confirming that an order placed on a phone with a discount code reaches fulfilment, triggers the right email and records correctly in analytics is not, and that is where problems hide.
Our migrations average about one month from kick off to launch, and our Shopify developers handle them end to end with a 3 month guarantee on development projects. If you are planning a move and want a second pair of eyes on the scope, email us.
How long does a Shopify migration take from start to finish?
Our migrations average about one month from kick off to launch. A small store moving as it is can be quicker, while a redesign, a custom theme or several integrations such as an ERP can take considerably longer. Scope, catalogue size and integrations decide the timeline.
Do I need a URL redirect map to migrate to Shopify?
Yes, if you want to keep your organic traffic. Every valuable old URL needs a deliberate destination on the new store. Of the last 80 stores we migrated, 75 arrived without one, which is the most common reason rankings fall after a migration.
Can I keep my domain name when migrating to Shopify?
Yes, and most merchants do. You point your domain at Shopify. Keeping the same domain means only the paths change, which makes the move simpler for search engines than changing domain and URLs at the same time.
Will my customers need to create new accounts after migration?
Customer records can be imported, but passwords cannot be transferred from most platforms. Plan how customers will access their accounts, such as Shopify's account invitations or passwordless sign in, and brief customer service before launch.
Will I lose my SEO rankings when I migrate to Shopify?
Not if SEO is its own workstream. A complete redirect map, preserved content and metadata, working structured data and close monitoring after launch protect most of your visibility. Some movement in the first weeks is normal while search engines process the new URLs.
Do I need to close my old store before launching on Shopify?
No. Build and test the Shopify store while the old one stays live, set a data cut off point, run a final migration, then switch the domain. Keep the old platform accessible for a few weeks afterwards for reconciliation.
What if I find problems after launch?
Monitor Search Console, analytics and customer feedback daily for the first two weeks. Most issues after launch involve redirects, tracking or integrations, and all can be fixed quickly if spotted early. Prioritise anything affecting checkout or payments first.
Thirty steps looks daunting written out, but most are decisions rather than work, and most happen before anything is built. A migration that fails usually does so because something was never considered, not because a step was done badly. Work through Phase 1 properly and the rest becomes execution. Skip it and you will spend the 90 days after launch discovering what you missed, usually through Search Console and at greater cost than the planning would have taken.
Tell us a little about your store and we'll get back to you within 24 hours.