Migrating from WooCommerce to Shopify: A Technical Checklist for SEO, Redirects and Data

Author Avatar Digital Bhatti
• November 17, 2026 • Ecommerce

WooCommerce to Shopify migration illustration: store data and URL arrows moving from a WordPress storefront to a Shopify storefront beside a checklist

Replatforming is the highest-risk change a store can make — not because the data is hard to move (it mostly isn't), but because every URL your store owns changes at once. Products, orders and customers are a solved problem. Rankings, bookmarks, shared links and ad campaigns pointing at addresses that stop existing are not.

This checklist is for store owners moving from WooCommerce to Shopify who want the move planned like a migration, not a copy-paste. It assumes you have already decided the move makes sense — if you haven't, start with our Shopify vs WooCommerce comparison, which covers when switching platforms is and isn't the right answer.

Three artifacts decide whether the migration works: a complete inventory of your current URLs, a page-to-page 301 redirect map into Shopify's fixed URL structure, and verified data imports — checked record by record, not assumed. Everything below builds those three, in order.

The short answer: A WooCommerce-to-Shopify migration succeeds or fails on the redirect map. Every Shopify URL is rebuilt under fixed prefixes — /products/, /collections/, /pages/, /blogs/ — so build a full URL inventory first, map each important old URL to its closest new equivalent with a 301, and import the redirects before you switch the domain. For data: products and customers move by CSV or Shopify's free Store Migration app; orders, coupons and blog content need a migration app or manual work; customer passwords never move. Keep the same domain if you can, and judge the result on 30 days of Search Console data against a pre-migration baseline — not on launch-week rankings.

1. What actually changes when you replatform

Owners underestimate this move because the visible parts look simple. A product is a title, a price, some images — what could break? Four structural differences do the damage:

Every URL changes. WooCommerce lets you shape permalinks almost freely — /product/blue-tshirt/, /shop/shirts/blue-tshirt/, category paths, tag archives. Shopify fixes the first segment of every address and the prefixes cannot be removed. The final slug (the handle) can usually be kept; the full address cannot.

The data model differs. WooCommerce categories become Shopify collections plus tags — Shopify's own migration guide notes there is no categories column in its product CSV, so categories are carried as tags and rebuilt as collections from those tags. Attributes become options, capped at three per product. Plugin-added fields (custom checkout fields, product add-ons, bespoke order statuses) have no native destination at all.

Accounts work differently. There are no passwords to migrate — they can't be, on any platform pair, because they're stored as hashes. On Shopify's current customer accounts, imported customers sign in with their email address and a one-time verification code.

Your old store is also your image host. Product imports pull images from their URLs on your WooCommerce store. Take the old store offline too early and the import quietly produces imageless products.

2. Before: the pre-migration audit

Do this while the WooCommerce store is untouched and still earning. Nothing here is optional — each item is either an input to the redirect map or the baseline you measure success against.

Build the URL inventory

Crawl the live store (your usual crawler, exported in full) and merge four sources into one spreadsheet — this becomes the master migration document:

  • Every crawlable URL: products, categories, tags, pages, posts, the shop page, landing pages.
  • Search Console's Pages report: the URLs Google has actually indexed, which is not the same list as the crawl — it includes old, orphaned URLs your navigation forgot years ago.
  • Top pages by traffic and by revenue (analytics, last 90 days): these get hand-checked redirects, not bulk rules.
  • URLs with backlinks: any page another site links to has equity you cannot recreate — it must land somewhere sensible.

Record what already exists

  • Existing redirects on the WordPress side (from your SEO plugin or .htaccess): years of accumulated fixes that must be re-expressed in the new map, pointed at final destinations — never chained through the old intermediate URLs.
  • Structured data currently emitted (product, review, breadcrumb markup): note what your SEO plugin generates today so you can compare against what the Shopify theme generates after the move.
  • Titles and meta descriptions for the top 50 pages by traffic, exported. You will re-enter the ones that matter by hand (section 5), and you need the originals to do it.
  • Baseline metrics: 90 days of Search Console clicks/impressions by page, organic sessions, and conversion rate. Screenshot or export them. Without a baseline, every post-launch argument about whether the move "hurt SEO" is vibes.

Freeze scope here: no new products, no permalink tidy-ups, no theme changes on the old store from this point. A moving source makes the inventory stale. The discipline is the same one a clean WooCommerce technical setup runs on — inventory first, changes second.

3. What moves, what doesn't: the data scope

Shopify's WooCommerce migration guide lists the transfer methods plainly: manual copy-paste, the free Store Migration app (products and customers, from your WooCommerce CSV exports), plain CSV import, third-party migration apps, or a Shopify Partner. What each data type does under those methods:

Data How it moves Watch out for
Products CSV or Store Migration app. Column names must be remapped to Shopify's format (Name → Title, weight converted to grams, one row per variant). Imported products land as drafts. Images download from the WooCommerce URLs during import — keep the old store online until imports finish.
Variants As rows sharing the product's handle, up to 3 options per product. Products using 4+ attributes for variations are imported without variants (Shopify's guide says so explicitly). Restructure those products, or plan on apps/metafields.
Customers CSV or Store Migration app, after remapping to Shopify's customer template. Passwords never migrate. Current customer accounts sign in by email + one-time code; legacy accounts need an invite to set a new password. Import customers before orders so history attaches correctly.
Historical orders Not by CSV. Shopify's guide is explicit: use a third-party migration app. Imported orders are records, not live orders — verify totals, tax and discount lines on a sample before importing the full history.
Coupons → discounts Not in the product/customer exports. Recreate as Shopify discounts, or use a migration app (Shopify's guide names Matrixify for this). Any code currently printed on packaging, ads or partner sites must exist and work on day one — list those codes separately.
Gift cards Manually, via the Gift Card API, or with a third-party gift card migration app — and only right before launch. Shopify gift cards can't be edited or deleted once created, and only the last 4 digits of a number are visible afterwards. Export codes + balances last, keep your own external record, and reconcile immediately.
Blog posts & pages Not included in WooCommerce exports. Recreate in Shopify, or import with a migration app (again, Shopify's guide names Matrixify). Posts land under /blogs/ — every post URL changes too, so content URLs belong in the redirect map, not just product URLs.
Reviews Not included in the product export; they move through your review platform's own export/import route. If reviews power rich results today, confirm the destination setup emits matching structured data before launch, not after.
Subscriptions & saved payment methods Do not ride along with a data import — they have to be re-established with a subscriptions app and your payment gateway. Plan subscriber communication early; a surprise re-billing setup is how migrations churn their best customers.

Method choice, honestly: small, simple catalogs (a few hundred SKUs, no order-history requirement) are fine on CSV plus the Store Migration app. The moment you need orders, coupons or blog content moved intact, you're in migration-app or partner territory — budget for it instead of discovering it mid-cutover.

4. The redirect map: the part that decides your traffic

Shopify's URL grammar is fixed. Every WooCommerce address has to be translated into it, one by one:

WooCommerce (typical permalinks) Shopify equivalent Mapping rule
/product/blue-tshirt/ /products/blue-tshirt Keep the slug as the handle; change only the prefix.
/product-category/shirts/ /collections/shirts One collection per category that earned traffic; empty categories redirect to their parent collection instead.
/shop/ and deep paths like /shop/shirts/blue-tshirt/ /collections/all / /products/blue-tshirt Deep product paths map to the product itself. Note: /shop is on Shopify's blocked-prefix list for redirect sources (below) — expect the bare shop page to be unrecoverable as a redirect and plan internal links accordingly.
/blue-tshirt/ (page) /pages/blue-tshirt Static pages keep their slug under /pages/.
/2026/09/post-name/ (dated post) /blogs/news/post-name The date structure disappears entirely; the handle is all that survives.
/product-tag/cotton/ /collections/all/cotton (tag-filtered collection view) Only map tag URLs with real traffic or links; the long tail of tag archives is usually left to 404 deliberately rather than redirected to thin equivalents.
/cart/, /checkout/, /my-account/ — Cannot be redirected. These paths are system-owned on both sides. Bookmarks to them die; that's acceptable — nobody's SEO depends on a checkout URL.

How Shopify redirects behave — the rules that bite

From Shopify's URL redirect documentation:

  • They're managed under Content > Menus > View URL Redirects, created one at a time or imported in bulk from a two-column CSV (Redirect from, Redirect to). For a migration, the CSV import is the only sane route.
  • A redirect only fires from a broken URL. If the old path still returns a live page on the new store, Shopify serves the page, not the redirect. This is why redirects are imported at cutover, not weeks early against a store that doesn't have the paths yet — and why collisions (an old path that happens to exist on Shopify) silently break individual rules.
  • Some sources are blocked. You can't redirect URLs beginning with /apps, /application, /cart, /carts, /orders, /services or /shop, and you can't redirect the fixed paths /products, /collections or /collections/all themselves.
  • The ceiling is high but real: 100,000 redirects per store (20 million on Plus). A normal WooCommerce catalog fits comfortably; a decade of parameter and tag URLs may not — another reason to map what matters instead of everything.
  • They're exact-path 301s. No wildcards, no pattern rules. /product/* is not a thing. Every row in the map is one literal old path — which is exactly why the inventory in section 2 has to be complete.

Building the map without errors

One row per old URL, with columns: old path, new path, source (crawl / Search Console / backlinks), and a priority flag for the top pages. Then validate before import:

  • Every "new path" returns 200 on the staging Shopify store.
  • No new path is itself the source of another redirect (no chains).
  • No old path collides with a live Shopify path (it would never fire).
  • Top-50 traffic pages are checked by hand, not sampled.

Import in a small test batch first — twenty rows — click through them, then import the rest.

5. SEO preservation during the move

Redirects are the skeleton; these are the details that decide how much equity survives the transfer.

Titles and meta descriptions don't migrate 1:1. Product descriptions travel in the CSV; the SEO title and description fields your WordPress plugin maintained are plugin data, not product data. Shopify has its own search-engine listing fields per product, collection, page and post. Re-enter them for every page where they were deliberately written — your top-50 export from section 2 — and accept platform defaults for the long tail.

Image alt text. Alt text lives with the media library in WordPress and with each product image in Shopify. If your imports arrive with empty alt attributes, that's a bulk-fix project after launch, not a detail. Check the import report on a sample product before the full run, the same check you'd run in any technical SEO for ecommerce audit.

Canonicals take care of themselves — verify anyway. Shopify emits self-referencing canonicals from the theme; your job is confirming the canonical on a sample of products and collections points at the /products/… URL and not at a variant or the myshopify.com subdomain.

Sitemap and Search Console. Shopify generates sitemap.xml automatically; submit it in Search Console on launch day. If the domain is unchanged, that's the whole Search Console story: Google's Change of Address tool is only for moving to a different domain, so don't use it for a same-domain replatform. If you are changing domains at the same time — don't, if you can avoid stacking two moves — then it becomes a domain move with its own procedure.

The dip is real; measure it properly. Google is explicit that ranking fluctuation during a move with URL changes is normal while pages are recrawled and reprocessed. The stores that "lose SEO" in a migration almost always skipped rows in the redirect map or redirected everything to the homepage. Your defence is measurement: weekly Search Console comparison of clicks and impressions per template (products, collections, posts) against the 90-day baseline, and a hard rule that no conclusion gets drawn before 30 days of data exist. Keep every redirect live for at least a year — Google's floor for a domain move is 180 days, and redirects cost nothing to keep.

6. Domain, DNS and email

Connect, don't transfer — at least not yet. Connecting keeps the domain at your registrar, under your DNS control: an A record on the root pointing at the IP Shopify shows during setup, and a CNAME on www pointing to shops.myshopify.com, with Shopify provisioning SSL automatically. A transfer moves the registration itself into Shopify; it consolidates billing and lets Shopify manage DNS for you, but a registrar transfer in launch week adds a propagation variable you don't need. Connect for the launch; transfer later if you still want to. (The full connection sequence, including the Cloudflare proxy warning, is in Setting Up a Shopify Store: A Technical Walkthrough.)

Email is the forgotten migration. Your business email (Google Workspace, Microsoft 365, or registrar mail) lives in DNS records — MX, SPF, DKIM — that must survive the DNS changes untouched. Inventory them in section 2's audit and re-verify them after cutover; a store launch that silently breaks the company inbox is a classic.

Then authenticate Shopify's sending. Order confirmations and notifications send from Shopify's platform, not your mail server. Per Shopify's email setup documentation, you authenticate your sender domain by adding the CNAME records Shopify provides (they configure SPF and DKIM — no separate SPF record needed) plus a DMARC record (minimum v=DMARC1; p=none). Skip this and your sender address is rewritten to a [email protected] address — technically delivered, commercially embarrassing. DNS changes can take up to 48 hours to propagate, so publish these records before cutover day, not during it.

7. Payment continuity — the Pakistan specifics

If you're a PKR store moving to Shopify to sell internationally, payments are where the migration plan meets reality. The platform fact hasn't changed: Shopify Payments is not available in Pakistan, so a Pakistani store runs on third-party and local gateways — which means every gateway relationship has to be re-established on the new platform, with new credentials, new webhook endpoints, and often a fresh review by the provider.

  • Apply early. Gateway approval timelines are the longest pole in most Pakistani migrations. Start the applications when you start the audit, not at cutover. The provider-by-provider picture — 2Checkout (Verifone), Payoneer Checkout, Safepay, bSecure, and what each actually requires — is in Payment Gateways for Pakistani Online Stores.
  • COD is a launch feature, not an afterthought. Cash on delivery is a manual payment method in Shopify and skips the third-party transaction fee — for a COD-heavy store it can carry the launch while gateway approvals finish landing.
  • Freeze the fee math. Third-party gateways on Shopify pay both the gateway's fee and Shopify's transaction fee. Recalculate per-order economics on your real mix (COD vs prepaid vs international cards) before committing to the plan tier.
  • Test money movement, not just checkout. A test order that "works" but settles to the wrong bank account is a failure discovered at the worst moment. Run the Bogus Gateway for flow tests, then one small real transaction per live gateway, and reconcile it to the bank.

8. Cutover day: the sequence

Order matters more than speed. A defensible cutover runs like this:

  1. Finish the destination store completely — theme, collections, legal pages, shipping zones, taxes, notifications — while it sits behind the store password on the myshopify.com address.
  2. Final data delta: re-run product and customer imports to catch everything created since the first pass, then import historical orders (app) against the final customer set.
  3. Gift cards last — export codes and balances from WooCommerce at the freeze moment and create them in Shopify immediately, per the constraint in section 3.
  4. Import the redirect map and click-test the test batch plus every top-50 URL.
  5. Point the domain (A record + www CNAME), confirm SSL is active, set the custom domain as primary.
  6. Submit the sitemap in Search Console and confirm the homepage, a product, a collection and a blog post all return 200 at their new addresses.
  7. Place real test orders — one per payment method — and follow each through confirmation email, admin, and settlement.
  8. Unfreeze: remove the store password, announce, and keep the WooCommerce store intact (hosting paid, admin accessible) but closed to new orders. It is your image host, your records archive, and your rollback option — in that order of likelihood.

9. After launch: integrity checks and the first 30 days

Data integrity — verify, don't trust the import report

  • Counts: products, variants, customers, orders imported vs exported. Investigate every gap; import reports list failures — read them.
  • Money fields on a sample: pick 20 products across simple/variable/sale and compare price, compare-at price, SKU, weight (grams — the classic silent error is kilograms imported as grams), tax status and inventory quantity against the WooCommerce originals.
  • Customers: spot-check addresses, marketing-consent flags (only customers who opted in should arrive subscribed), and that imported order history attaches to the right profiles.
  • Discounts and gift cards: every code on the "must work day one" list gets a live cart test; gift card balances reconciled against the export, to the rupee.
  • Content: internal links inside migrated blog posts still point at WooCommerce URLs unless they were rewritten — crawl the new store for links to its own old paths.

Monitoring — days 1 to 30

  • Search Console, weekly: Page indexing report for a 404 spike (expected small, investigated if growing), coverage of the new templates, and clicks/impressions per template vs the 90-day baseline.
  • 404 hunting: Search Console's "Not found" list is your missed-rows report. Each entry with traffic or links gets a redirect row added — this is normal migration maintenance for the first month, not a failure.
  • Rank sample: track the same template-level sample you tracked before the move (per the measurement approach in Technical SEO for Ecommerce Stores) so before/after is a comparison, not an impression.
  • Revenue sanity: conversion rate and orders/day against the trailing 90 days, adjusted for any launch noise you created yourself (announcements, promotions).
  • Day 30 verdict: write down what the data says — recovered, recovering, or specific templates still down — and what the remaining gap is attributed to. That document is the difference between a migration that taught you something and one that just happened to you.

10. The checklist

The whole guide, condensed. Print it, work it in order.

Before — audit and build

  • ☐ Full crawl + Search Console indexed-URL export merged into one URL inventory
  • ☐ Top pages by traffic, revenue and backlinks flagged in the inventory
  • ☐ Existing WordPress redirects recorded, pointed at final destinations
  • ☐ Titles/meta for top 50 pages exported; structured data setup noted
  • ☐ 90-day Search Console + analytics baseline exported
  • ☐ MX/SPF/DKIM records for business email inventoried
  • ☐ Scope frozen on the old store; full backup taken
  • ☐ Destination store built behind password; gateway applications started (Pakistan: allow weeks)
  • ☐ Products/customers imported as drafts; sample products verified field by field
  • ☐ Products with 4+ variation attributes restructured or assigned an app/metafield plan
  • ☐ Collections rebuilt from category tags; SEO titles/meta re-entered for top pages
  • ☐ Redirect map built (one row per URL) and validated: targets 200, no chains, no collisions
  • ☐ Email domain authentication records published (Shopify CNAMEs + DMARC)

During — cutover

  • ☐ Final product/customer delta import; historical orders imported against final customers
  • ☐ Gift cards exported and recreated last; balances reconciled; external code record kept
  • ☐ Discount codes recreated; "must work day one" codes listed
  • ☐ Redirect CSV imported; test batch + all top-50 URLs click-tested
  • ☐ Domain connected (A + CNAME), SSL active, custom domain set primary
  • ☐ Sitemap submitted in Search Console
  • ☐ Real test order per payment method, reconciled to the bank
  • ☐ Store password removed; old store closed to orders but kept online

After — first 30 days

  • ☐ Record counts reconciled (products, variants, customers, orders); import failure lists cleared
  • ☐ 20-product money-field sample re-verified (price, weight in grams, tax, inventory)
  • ☐ Weekly Search Console review: indexing, 404 list actioned, per-template clicks vs baseline
  • ☐ Migrated content crawled for leftover old-URL internal links
  • ☐ Customer sign-in path tested (email + one-time code) and communicated to customers
  • ☐ Redirects left live — minimum a year, not a month
  • ☐ Day-30 verdict written: recovered / recovering / gaps, with the data attached

Limitations and caveats

This checklist covers a same-domain, standard-plan migration of a typical WooCommerce catalog. Shopify Plus changes some constraints (redirect ceiling, checkout extensibility); very large catalogs may hit the customer CSV file-size limits and need batched imports or an app. Subscription stores, multi-currency price lists and marketplace-synced inventory each add a workstream this guide deliberately treats as a flag, not a chapter. Platform details — import formats, redirect limits, account behaviour — are Shopify's and change; verify the specifics against Shopify's current documentation when you run your migration, not from memory of this page.

Closing

A WooCommerce-to-Shopify migration is three projects wearing one coat: a data import (easy, documented), an email-and-payments re-establishment (slow, bureaucratic), and a URL migration (unforgiving, entirely in your control). Stores lose traffic to the third project while watching the first. Build the inventory, respect the redirect map, measure against a baseline — and the platform change becomes what it should be: a business decision, not an SEO event.

Frequently asked questions

Can I keep the same URLs when I move from WooCommerce to Shopify?

No. Shopify fixes the first part of every URL — products live under /products/, collections under /collections/, pages under /pages/ and articles under /blogs/ — and the prefixes cannot be removed. You can usually keep the final slug (the handle) the same as your WooCommerce permalink, but the full address always changes. Every old URL that matters needs a 301 redirect to its closest new equivalent.

Do customer passwords and order history move to Shopify?

Passwords never move — Shopify states they can't be migrated from another store, and on current customer accounts your customers sign in with their email address and a one-time verification code instead. Order history doesn't move by CSV either: Shopify's migration guide says orders need a third-party migration app. Import customers before orders so the imported history attaches to the right profiles.

Will my search traffic drop after the migration?

Expect a temporary dip, not a disaster — Google warns that ranking fluctuation is normal while it recrawls and reprocesses changed URLs. Stores get hurt when old URLs are left to 404 or are mass-redirected to the homepage. Map every important old URL to its closest new page with a 301, submit the new sitemap in Search Console, keep the redirects in place for at least a year, and judge the move on 30 days of Search Console data against your pre-migration baseline, not on day-three rankings.

Should I transfer my domain to Shopify or just connect it?

Connect it first. Connecting keeps your registrar and DNS control, points the root A record at Shopify and www at shops.myshopify.com, and can be reversed in minutes if the launch goes wrong. Transferring moves the registration itself into Shopify — one less bill, and Shopify manages DNS and email authentication for domains it hosts — but a transfer mid-launch adds propagation risk you don't need. Transfer later, once the store is stable, if you want the consolidation.


Last updated: November 2026. Platform behaviour, import formats and limits change over time — verify specifics against Shopify's and Google's official documentation before running a migration.