Digital Transformation

Replatforming to Shopify Plus Without Losing Revenue: A Migration Checklist

A phase-by-phase checklist for moving from WooCommerce or Magento to Shopify Plus: data, redirects, SEO, tracking, apps, QA and launch monitoring.

TL;DR
  • Most revenue lost in a replatform comes from a few avoidable gaps: missing 301 redirects, broken tracking, disconnected email flows, and customers who cannot log in.
  • Baseline your KPIs before you start, map every URL that earns traffic or links, and rebuild tracking and integrations on Shopify Plus before launch, not after.
  • Freeze changes before go-live, then monitor search, conversion and retention for 30 to 90 days, with clear owners for every fix.

A replatform can quietly cut revenue for months: organic traffic slips, ad platforms lose conversion data, the welcome flow stops firing. It happens when the migration is run as a design project instead of a revenue project. This checklist covers a move from WooCommerce or Magento / Adobe Commerce to Shopify Plus.

Why do Shopify Plus migrations lose revenue?

Here is an illustrative example of what is at stake. A store doing $5,000,000 a year gets 30% of revenue from organic search. If a migration drops organic revenue by 20% for three months, the store gives up about $75,000 in sales, before counting lost email revenue or worse ad performance from missing conversion data.

The common causes:

  • Old URLs that return 404 instead of redirecting to the new equivalent.
  • Tracking that fires twice, not at all, or without consent signals.
  • Email and SMS flows still listening for events from the old platform.
  • App features nobody listed, such as a gift-with-purchase rule or a wholesale price list.
  • Customers who cannot sign in and give up.

What should you do before the migration starts?

Discovery and baseline KPIs

You cannot prove a migration worked without a “before” picture. Capture 12 months where possible, so seasonality does not fool you.

  • [ ] Revenue, orders, conversion rate and AOV, by device and channel.
  • [ ] Organic sessions and revenue by landing page, from GA4 and Search Console.
  • [ ] Top URLs by organic clicks, revenue and backlinks.
  • [ ] Core Web Vitals for key templates: home, collection, product, cart.
  • [ ] Email and SMS revenue by flow and campaign.
  • [ ] Repeat purchase rate and first-to-second order rate.
  • [ ] A full list of plugins, extensions, custom code and integrations, with what each one does.

A Free Profit Audit gives you a quick pre-migration baseline of profit leaks to compare against after launch.

Scope and timeline

A typical plan, with illustrative durations that depend on catalog size and custom features:

Phase Illustrative duration Main output
Discovery and baseline 2 to 3 weeks KPI baseline, app inventory, scope
Build and data migration 6 to 10 weeks Theme, apps, test imports
SEO, tracking and integrations Runs alongside build Redirect map, tracking plan, connected ESP
QA and user testing 2 to 3 weeks Signed-off test scripts
Launch freeze and go-live 1 to 2 weeks Final data delta, DNS switch
Post-launch monitoring 30 to 90 days Weekly KPI reviews and fixes

How do you migrate products, customers and orders?

Products

  • [ ] Export products with variants, SKUs, barcodes, weights, images and alt text.
  • [ ] Map attributes to Shopify options (up to three per product) and metafields for everything else.
  • [ ] Keep product handles close to the old URL slugs where it makes sense.
  • [ ] Map categories to collections, deciding which should be manual and which automated.

Customers

  • [ ] Import customer profiles, addresses, tags and marketing consent status.
  • [ ] Plan account re-activation. Customer passwords generally cannot be migrated, because they are stored as one-way hashes that Shopify cannot import. Send account invites, or use Shopify’s newer customer accounts, which sign people in with a one-time email code instead of a password.

Orders, subscriptions, reviews and gift cards

  • [ ] Import historical orders so customers see their order history and your LTV reports stay intact. Make sure imports do not trigger notifications to customers.
  • [ ] Plan subscriptions early. Moving active subscriptions usually means migrating payment tokens between processors, coordinated with your subscription app and payment provider. Have a fallback for customers who need to re-enter a card.
  • [ ] Export reviews and import them into your Shopify review app, matched by SKU or handle.
  • [ ] Migrate gift card balances and store credit. Shopify Plus supports importing gift cards.

Tools such as Shopify’s Store Importer app or Matrixify handle most of this. Always run a full test import first.

How do you protect SEO during the move?

URL mapping and 301 redirects

Shopify uses fixed URL patterns. You cannot keep WooCommerce or Magento paths as they are, so every page that earns traffic or links needs a 301 redirect.

Old URL (example) New Shopify URL
WooCommerce /product/merino-crew-sock/ /products/merino-crew-sock
WooCommerce /product-category/socks/ /collections/socks
Magento /socks/merino-crew-sock.html /products/merino-crew-sock
Magento /socks.html /collections/socks
/blog/how-to-wash-merino/ /blogs/news/how-to-wash-merino
/about-us/ /pages/about-us
  • [ ] Crawl the old site and combine the crawl with GA4, Search Console and backlink data.
  • [ ] Map one-to-one wherever possible. Redirect retired products to the closest collection, not the homepage.
  • [ ] Import redirects in bulk through Shopify’s URL redirects (CSV import).
  • [ ] Note that Shopify only applies a redirect when the old path does not exist on the new store.
  • [ ] Test URLs with query strings, trailing slashes and uppercase letters, since old platforms often have all three.
  • [ ] Avoid redirect chains. Old redirects from the previous platform should point straight to the final Shopify URL.

Technical SEO checks

  • [ ] Canonical tags point to the clean /products/ URL, not collection-scoped versions such as /collections/socks/products/merino-crew-sock.
  • [ ] Titles, meta descriptions and H1s migrated for top pages.
  • [ ] Structured data for Product and Organization validated, with no duplicate blocks from theme and apps. See our guide to product schema for eCommerce.
  • [ ] The XML sitemap Shopify generates at /sitemap.xml is submitted in Search Console.
  • [ ] Internal links in navigation, content and footers updated to new URLs, not left to redirects.
  • [ ] robots.txt reviewed (editable through the robots.txt.liquid template) and the staging store password-protected until launch.

How do you rebuild tracking, email and apps?

Tracking and consent

On Shopify Plus, checkout customization runs through Checkout Extensibility. You cannot paste scripts into the checkout pages, so tracking there runs through Shopify’s Customer Events (web pixels) instead.

  • [ ] Write a tracking plan: every event, its parameters and its destination.
  • [ ] Set up GA4 through Shopify’s Google app or through Google Tag Manager on the storefront, plus a custom pixel for checkout events. Pick one path, not both.
  • [ ] Reconnect Meta, Google Ads, TikTok and Pinterest pixels and their server-side connections, and check for duplicate purchase events.
  • [ ] Connect your consent management platform to Shopify’s Customer Privacy API so tags respect consent choices. Confirm consent requirements with counsel.
  • [ ] Reconcile test orders: Shopify, GA4 and ad platforms should report the same transactions.

Email and SMS

  • [ ] Install the Klaviyo (or other ESP) Shopify integration and sync the catalog.
  • [ ] Rebuild flow triggers on the new Shopify events: welcome, abandoned checkout, browse abandonment, post-purchase, back in stock, winback.
  • [ ] Reconnect signup forms and check consent fields map correctly. SMS consent rules are strict, so confirm with counsel.
  • [ ] Send a test of every flow and check links point to new URLs.

App replacements

  • [ ] Map every plugin or extension to a native Shopify feature, an app, or custom work.
  • [ ] Use Shopify Flow for back-office automation and Shopify Functions for custom discount, shipping and payment logic.

How should you run QA and launch?

QA

  • [ ] Test scripts for every customer journey: browse, search, filter, add to cart, discount codes, checkout, account sign-in, returns.
  • [ ] Test on real phones, not only desktop browser emulators.
  • [ ] Place real orders with each payment method and refund them.
  • [ ] Check tax, shipping rates and Markets settings for every region you sell to.

Launch freeze and go-live

  • [ ] Freeze content, product and code changes on the old store one to two weeks before launch.
  • [ ] Lower DNS TTL a few days ahead so the switch propagates quickly.
  • [ ] Run the final delta import of new orders, customers and reviews.
  • [ ] Launch on a low-traffic day with the whole team available, not before a holiday or a big campaign.

What should you monitor after launch?

Plan for 30 to 90 days of active monitoring, with a named owner for each area.

  • [ ] Day 1: spot-check the top redirects, test orders, tracking and flows.
  • [ ] Week 1: daily checks of Search Console coverage, 404s, conversion rate and checkout completion.
  • [ ] Weeks 2 to 4: compare organic landing-page revenue and email flow revenue to the baseline.
  • [ ] Days 30 to 90: review rankings for top pages, Merchant Center disapprovals, repeat purchase rate and Core Web Vitals.

Some ranking movement early on is common. A steady decline on specific pages usually means a missing redirect or changed content.

How do you bring the team along?

A migration can fail on people as easily as on code. Treat change management as part of the project:

  • [ ] Name one decision owner and one owner per workstream: data, SEO, tracking, retention, operations.
  • [ ] Train customer service, fulfillment and merchandising on the Shopify admin before launch.
  • [ ] Rewrite SOPs for daily tasks such as refunds, product uploads and promotions.
  • [ ] Keep a shared launch log of issues, owners and status.

If you want an independent plan and QA for your replatform, our Commerce Advisory team runs migrations as revenue projects from discovery to the 90-day review.

FAQ

How long does a Shopify Plus migration take?

It depends on catalog size, custom features and integrations. Many mid-size stores plan for a few months from discovery to launch, plus 30 to 90 days of monitoring.

Will we lose SEO rankings when we migrate to Shopify?

Some movement is normal while redirects are processed. With a complete redirect map, consistent content and clean technical SEO, you give yourself the best chance of avoiding lasting losses.

Can customers keep their passwords?

Generally no, because passwords are stored as one-way hashes that Shopify cannot import. Send account invites or use Shopify’s customer accounts with one-time email codes.

Turn this into a plan for your store

The Free Profit Audit scans your store, sizes your biggest profit leaks and builds a 90-day plan.

Free Profit Audit