Shopify migration guide

How do you migrate to Shopify without losing SEO or customer data?

You cannot guarantee that every ranking, record, or workflow will transfer unchanged. You can reduce avoidable risk with a complete inventory, field and URL mapping, controlled imports, tested redirects, a deliberate cutover, and post-launch monitoring.

Last reviewed August 3, 2026 · 11 minute read

Protect the business before redesigning the pages.

An established store contains more than products and design. It carries customer records, order history, subscriptions, URLs, search equity, payment relationships, inventory logic, reports, integrations, policies, and routines that employees and customers rely on.

The migration plan must identify what can transfer directly, what needs transformation, what must be recreated, what requires a specialist, and what should not move at all.

The migration sequence

Eight phases from inventory to stabilization.

The safest order separates discovery, build, testing, launch, and monitoring instead of changing the live store as decisions are made.

  1. 01

    Inventory the current business

    List every product, variant, collection, customer record, order type, subscription, discount, gift card, page, article, form, integration, domain, email flow, report, tracking tool, and operational dependency.

  2. 02

    Define the destination

    Decide what should move, improve, merge, retire, or remain elsewhere. Confirm the Shopify plan, markets, payment provider, tax approach, shipping, apps, theme, customer accounts, and ownership model.

  3. 03

    Map data and URLs

    Match source fields to Shopify fields, document transformation rules, and create an old-to-new URL map for valuable pages. Give each important old URL the most relevant destination rather than sending everything to the homepage.

  4. 04

    Build and import safely

    Create the new store away from the live customer journey. Import in a controlled order, preserve stable identifiers where possible, document exceptions, and review samples before treating a bulk migration as complete.

  5. 05

    Rebuild the customer experience

    Recreate navigation, content, merchandising, policies, email notifications, search metadata, structured data, forms, and essential integrations around how the new store will actually operate.

  6. 06

    Test before cutover

    Test priority URLs, redirects, account access, products, checkout, payments, shipping, taxes, discounts, notifications, analytics, mobile behavior, accessibility, and representative orders before moving the domain.

  7. 07

    Control the launch window

    Freeze or track late changes, perform the final data reconciliation, preserve backups, lower DNS timing where appropriate, switch the domain deliberately, and keep decision-makers available during launch.

  8. 08

    Monitor and reconcile

    Watch Search Console, analytics, orders, payments, redirects, crawl errors, customer questions, inventory, subscriptions, email delivery, and third-party tools. Fix evidence-backed problems without changing many variables at once.

Official migration guidance

Redirects, test orders, domains, and data limits are not optional details.

Shopify’s migration checklist addresses products, customers, content, URL redirects, domains, email authentication, taxes, and test orders. Google recommends preparing and testing the new site, mapping old URLs to new URLs, and then using server-side redirects during a site move.

Migration inventory

Six data and operating areas to map.

An item being exportable does not mean it will behave the same way after import.

  1. 01

    Products and variants

    Titles, descriptions, media, options, SKUs, barcodes, cost, price, inventory, weight, categories, collections, status, suppliers, and search metadata.

  2. 02

    Customers

    Names, contact details, addresses, consent status, tags, tax exemptions, notes, account expectations, and privacy obligations. Passwords generally cannot be imported because they are encrypted.

  3. 03

    Orders and financial history

    Historical order depth, fulfillment, refunds, discounts, tax, payment status, reporting needs, and the distinction between reference history and live financial records.

  4. 04

    Subscriptions and saved payments

    Contracts, products, billing cadence, payment tokens, gateway compatibility, customer communication, failed-payment handling, and app-vendor responsibilities.

  5. 05

    Content and search signals

    Pages, articles, images, files, titles, descriptions, headings, canonicals, schema, internal links, backlinks, indexed URLs, and the redirect map.

  6. 06

    Operations and integrations

    Domains, email authentication, shipping, taxes, discounts, gift cards, POS, ERP, CRM, accounting, support, reviews, analytics, feeds, automations, and staff access.

Search continuity

Controls that reduce avoidable SEO loss.

Redirects preserve routes for customers and search engines, but they do not freeze rankings. The new site must still be useful, accessible, internally coherent, and technically understandable.

  • Export current indexed URLs, top landing pages, backlinks, traffic, queries, and conversions before the move
  • Keep the same domain when sensible and avoid changing domain, platform, design, copy, and information architecture without a documented reason
  • Create permanent server-side redirects from old URLs to their closest relevant new URLs
  • Preserve or deliberately improve valuable titles, headings, copy, image context, canonicals, and internal links
  • Remove accidental password, noindex, robots, canonical, redirect-chain, and broken-link barriers
  • Submit the new sitemap and inspect priority pages in Google Search Console after launch
  • Keep redirects active long enough for users, search engines, bookmarks, and external links to adjust
  • Expect temporary fluctuation and investigate with data rather than promising unchanged rankings

Subscription businesses need a separate workstream

Never treat saved payment data like an ordinary customer CSV.

Shopify explains that subscription and saved-payment migration requirements depend on where payment methods are stored, the source gateway, the Shopify plan, and the chosen subscription app. Cardholder data must move only through approved secure processes.

Go-live gate

Do not move the domain until:

  • Migration inventory and exclusions are approved
  • Source exports and backups are stored securely
  • Priority data samples reconcile with the source
  • Critical old URLs have tested new destinations
  • Payments, representative orders, refunds, shipping, taxes, and notifications have been tested
  • Subscriptions, gift cards, loyalty, reviews, and customer accounts have explicit transition plans
  • Analytics, Search Console, consent, email authentication, and operational integrations are ready
  • A launch owner, communication plan, rollback criteria, and post-launch monitoring window are assigned

Migration questions

Plan around the records and relationships that cannot simply be copied.

Can a Shopify migration preserve every ranking?

No one can guarantee unchanged rankings. A disciplined migration can reduce avoidable loss by preserving useful content and signals, mapping URLs, using permanent redirects, testing thoroughly, and monitoring the move. Search engines still reevaluate the new site.

Can customer passwords move to Shopify?

Generally no. Shopify notes that passwords are encrypted, so customer records can be imported but passwords cannot. The launch plan should explain how customers activate or regain access to their accounts.

Can historical orders move to Shopify?

Historical orders can be migrated through supported apps or APIs, but completeness, reporting behavior, payment data, fulfillment history, and source-platform limitations must be evaluated before choosing the method.

What happens to subscriptions during a migration?

Subscription contracts and saved payment methods require a separate technical plan. Requirements depend on the source gateway, how payment methods are stored, the Shopify plan, and the subscription app. Shopify Support and the app vendor may need to participate.

Should every old URL redirect to the homepage?

No. Each valuable old URL should redirect to the closest relevant new page. Sending unrelated URLs to the homepage creates a poor customer experience and weakens the meaning of the redirect.

How long should Shopify redirects remain active?

Treat important redirects as durable infrastructure rather than a short launch task. Customers, bookmarks, links, and search engines may continue using old URLs long after the new store launches.

Migration begins with discovery

Scope the move before promising the launch date.

Answer seven practical questions and receive a recommended starting point before sharing your contact details.

No payment or contact information is required for the free check.