Migrationspillar 13 min

How to Migrate to Shopify: Data, Redirects, SEO and Cutover

A migration is not finished when products import or DNS changes. The real job is moving storefront behavior, search equity, analytics and operations to a new Shopify implementation with enough evidence to know what worked.

By Samuel Noriega · February 27, 2026

1. Start with an inventory, not a platform demo

Before deciding how Shopify should look, document what the current store actually does. That inventory includes storefront templates, products and variants, customer and order data, promotions, subscriptions, search, merchandising, payment methods, tax rules, fulfillment, ERP or PIM connections, feeds, analytics and any custom logic.

The goal is not to reproduce every historical workaround. It is to separate business requirements from platform debt. Some features should move. Some should be replaced with native Shopify behavior. Some should disappear.

2. Choose how the data will move

There are three ways to move a store to Shopify, and many migrations combine them. The choice decides what moves automatically and what someone has to own by hand.

Shopify's own importers

The built-in CSV importers handle products and customers, and the Store Migration app covers some hosted platforms. Pages, blog posts, redirects and order history need separate handling. This route suits small catalogs with simple variants and no integrations.

A bulk migration app

Apps such as Matrixify move products, variants, collections, customers, orders, redirects, metafields and content from spreadsheet templates or source exports. They are reliable record movers. They do not decide which URLs deserve a redirect, which plugins need a replacement, or what has to be true before launch.

A partner-led migration

A Shopify Partner adds data mapping, custom extraction, integration work, theme implementation and launch governance. It is worth the cost when Shopify Plus, B2B, ERP or 3PL integrations, subscriptions or a large legacy URL footprint make a failed cutover more expensive than the project. See how we scope Shopify migrations.

3. Give every valuable legacy URL an owner

Redirect mapping is an ownership exercise. Export the source URLs, combine them with Search Console, analytics and backlink data, then decide whether each meaningful URL maps to an equivalent page, a broader collection, a resource, or a deliberate retirement.

Avoid chains where possible and validate the final destination after deployment. Redirect quantity is not the objective; preserving useful intent is.

4. Shopify's URL rules change the redirect map

Shopify uses fixed URL prefixes, so most legacy URLs cannot be kept exactly as they are. Plan the redirect map around those rules from the first week, before templates and navigation are built.

  • Products live at /products/handle, collections at /collections/handle, pages at /pages/handle and articles at /blogs/blog-handle/article-handle.
  • Magento stores often use .html suffixes, nested category paths and store-view prefixes. Each pattern needs explicit rules, not a single wildcard.
  • WooCommerce typically uses /product/slug/ and /product-category/slug/, and WordPress posts and pages share one flat namespace that has to be split across Shopify pages and blogs.
  • BigCommerce custom URLs can be arbitrary per product and category, so they have to be exported and mapped one by one.
  • Shopify URL redirects only fire when the old path would otherwise return a 404. A redirect cannot override a live page at the same path.
  • Product URLs inside collections, such as /collections/x/products/y, canonicalize to /products/y; link to the canonical form in navigation and sitemaps.

Flatten redirects left by earlier migrations so each legacy URL reaches its final Shopify destination in one hop, and never send unmatched URLs to the homepage in bulk: search engines tend to treat that as a soft 404.

5. Reshape data to Shopify's model before importing

Source platforms rarely store data the way Shopify expects. Decide the target model first, then transform the export, instead of importing and fixing records afterwards.

  • Shopify products support up to three options, such as size, color and material. Configurable products with more dimensions need splitting, Combined Listings on Shopify Plus, or specification data moved into metafields. Variant limits have changed recently, so confirm the current limit for the plan before mapping very large option sets.
  • Structured attributes that customers filter on belong in product metafields, and repeated reference data in metaobjects, so search and filtering can use them.
  • Normalize option names and values before import: "Color", "Colour" and "color" become different options if they arrive inconsistently.
  • Customer groups and price lists map to customer tags and segments, or to companies and catalogs when Shopify Plus B2B is in scope.
  • Drop products that have not sold and carry no search or brand value. A smaller, cleaner catalog is easier to redirect, merchandise and reconcile.

6. Import in dependency order and reconcile the counts

Imports should be tested as datasets, not visually spot-checked. Record source counts before extraction, target counts after import, and the reasons for intentional differences. Products, variants, customer records, orders, metafields and media often fail in different ways.

A migration is safer when exceptions are explicit. If archived products are not moving, say so. If historical orders are accessible through a separate system instead of Shopify, document it. Ambiguity is what creates launch-day surprises.

Order matters: products and collections first, then customers, then historical orders, because orders reference both. Run at least one complete trial import into a development store, compare the counts, fix the mapping and repeat before the final production import.

7. Customer accounts, historical orders and subscriptions

These are the records customers notice first, and they are where most launch-week support tickets come from.

  • Passwords cannot be migrated because source platforms store them as one-way hashes. With Shopify's newer customer accounts, customers sign in with a one-time email code, so there is nothing to reset. With classic accounts, they activate their account from an invitation email. Schedule those invitations after launch and brief support first.
  • Import marketing consent with each customer record so email and SMS permissions survive the move.
  • Imported orders are historical records for the customer's account and for support lookups. Shopify will not refund or fulfill them through its normal flow, so agree how many years of history to import and where older orders stay.
  • Saved cards and subscription billing do not move with a normal data import. Subscriptions need a migration path supported by both the subscription app and the payment provider, planned and tested before cutover.

8. Payments, shipping and tax are launch blockers

A storefront can look finished while the checkout is still wrong. These settings are configured in Shopify, not imported, and each one needs a real test order before DNS changes.

  • Payments: activate Shopify Payments or the chosen gateway, then test every method you offer, including wallets and buy-now-pay-later, plus a refund.
  • Shipping: rebuild zones, rates, free-shipping thresholds and carrier-calculated rates, and connect the 3PL or shipping app before the test orders run.
  • Tax: in the United States, Shopify collects sales tax only for the states where you add registrations, so enter every state where you have nexus. Multi-country stores also need Shopify Markets settings for currencies, duties and languages.
  • Checkout customizations: Shopify Plus checkout changes are rebuilt with Checkout Extensibility and Shopify Functions, not copied from the old platform.

9. Validate analytics before DNS changes

Do not wait until production to discover that sessions, purchase events or campaign attribution changed. Validate the target storefront with representative journeys: landing page, product view, add to cart, checkout start, purchase and lead submission where applicable.

Record the IDs, consent behavior, UTMs and event payloads that matter. If the source and target use different tracking architectures, define the expected difference instead of forcing false parity.

10. Treat cutover as a release with acceptance criteria

The final pre-launch review should cover representative devices and templates, payment methods, shipping, taxes, account flows, transactional email, redirects, robots controls, canonicals, structured data, sitemaps and critical integrations.

Write down who can approve launch and what would stop it. A calendar deadline is not an acceptance criterion.

Pre-launch checklist

  • Redirects uploaded and every high-value legacy URL tested to a 200 destination in one hop
  • robots.txt, canonicals, structured data and the XML sitemap checked on the production domain
  • Test orders placed for each payment method, shipping zone and tax registration
  • Product, customer and order counts reconciled against the source export
  • GA4, ad pixels and consent behavior verified on landing, product, cart and purchase events
  • Apps and integrations confirmed: email flows, reviews, loyalty, subscriptions, ERP and 3PL
  • Customer account messaging and support scripts ready
  • Launch owner, go and no-go criteria and rollback steps written down

11. Common migration failures and how to fix them

A redirect is saved but does not fire

Something still exists at the old path, often an imported page or a product with the same handle. Remove or rename the conflicting resource; Shopify only redirects paths that would return a 404.

Imported products are missing from the storefront

Products imported as drafts or without the Online Store sales channel stay invisible. Filter by status and channel availability, then publish in bulk.

Variants or variant images did not attach

Option names or values differed between rows. Normalize them in the source file and re-import the affected products rather than editing variants one by one.

Purchases are counted twice in analytics

A tag was added in the theme as well as through the Shopify app or customer events. Keep one implementation per platform and confirm a single purchase event per order.

Organic landing pages drop after launch

Check the redirect report first, then canonicals and indexation for the affected templates, then whether titles, headings or content changed on pages that were ranking. Compare against the release log before reverting anything.

12. The first 30 days are still part of the migration

Post-launch monitoring should combine business and technical signals: orders, conversion events, redirect errors, crawl behavior, Search Console coverage, indexation, organic landing pages, app failures and support reports.

Search engines need time to crawl and reprocess the new structure. Early movement is a signal to investigate, not proof that the migration succeeded or failed. Keep a dated release log so changes can be interpreted against what actually shipped.

What our migrations taught us

On Petwell, a Magento to Shopify Plus migration, the destination taxonomy was defined before cutover so that data and SEO continuity could be tested before traffic moved. Deciding the target structure early is what made the redirect map and the data checks testable at all.

8 weeks Magento to Shopify Plus, 10,000+ SKUs, zero downtime

On Llantas Cavazos, a specification-heavy tire catalog, structured tire attributes drove exact-size search and smart collections. Treating catalog architecture, inventory synchronization, Merchant Center feeds and redirects as one program avoided fixing each in isolation after launch.

8,000+ SKUs Moved in under 7.5 weeks, 90%+ of organic traffic kept in week one

On Fashionable Canes, a Shopify Plus theme migration on a live catalog, the theme rebuild and the technical SEO recovery ran as connected workstreams so the store kept selling while search visibility was restored.

60 days Rankings recovered after a 15,000+ SKU Shopify Plus theme migration

On Poker Power, the migration ran as an engineering and SEO project rather than a theme swap: important URLs inventoried, redirects mapped, key templates validated and performance checked after launch.

The common lesson: the work that protects a migration happens before the theme is built. Teams that agree the URL map, the data model and the launch criteria first spend launch week verifying, not repairing.

Native theme or headless after the migration?

Headless is not automatically the more advanced answer. If the current headless layer exists mainly because of historical implementation choices, moving back to a native Shopify theme can reduce operating cost and restore merchant control.

Keep headless when the business genuinely depends on a custom frontend architecture, content model or multi-channel use case that a native theme cannot serve cleanly. The decision should be made from requirements and total operating cost, not fashion.

Migrate without losing rankings

Llantas Cavazos moved 8,000+ SKUs in under 7.5 weeks and kept 90%+ of organic traffic in week one. Read the case study

Most quotes returned within 1 business day

Frequently asked questions

Can I keep my existing URLs when I migrate to Shopify?

Usually not exactly. Shopify uses fixed prefixes such as /products/, /collections/, /pages/ and /blogs/, so most legacy URLs change. Keep the handles where it makes sense and send every valuable old URL to its closest Shopify equivalent with a single 301 redirect.

Do I need a migration app or an agency to move to Shopify?

Small catalogs with simple data can use Shopify's importers. Bulk apps such as Matrixify move larger datasets reliably. An agency adds URL strategy, data mapping, integrations, theme work and launch governance, which matters when search traffic, integrations or custom logic carry revenue.

Will customers need to reset their passwords after migrating to Shopify?

Passwords cannot be migrated. With Shopify's newer customer accounts, customers sign in with a one-time email code, so there is nothing to reset. With classic accounts, customers activate their account from an invitation email sent after launch.

How long does a Shopify migration take?

Migration timelines depend on catalog size, source-platform data quality, theme scope, integrations, B2B requirements, international markets and the amount of custom functionality that must be replaced. A focused store can move in several weeks; complex replatforming programs require a longer release plan.

Can a Shopify migration preserve SEO performance?

A controlled migration can reduce SEO risk by inventorying valuable URLs, mapping redirects, preserving useful metadata and structured data, validating canonicals and sitemaps, and monitoring Search Console after launch. Rankings can still move because search engines control crawling and ranking, so no responsible migration plan should promise zero change.

What data should be reconciled before launch?

At minimum, reconcile product and variant counts, customer records, historical orders when they are in scope, content pages, discounts or gift cards when relevant, inventory ownership, metafields and any records consumed by integrations. The exact checklist should come from the source system, not from a generic migration template.

When should a headless Shopify storefront move back to a native theme?

A native Shopify theme can be a better operating model when the headless layer adds engineering cost without delivering a material content, UX or channel advantage. Compare maintenance overhead, editorial workflow, app compatibility, performance and the actual business requirements before deciding.

What should be monitored after the DNS cutover?

Watch orders, checkout errors, analytics events, redirect behavior, crawl errors, Search Console coverage, payment methods, integrations, transactional email and representative customer journeys. The first days after launch are part of the migration, not a separate support phase.