WooCommerce to Shopify migration checklist

A WooCommerce to Shopify migration is not a checklist.

It is a controlled transfer of search equity.

Most migrations fail because decisions are made before the old store is fully understood. URLs are changed before they are mapped. collections are built before intent is checked. redirects are created under time pressure instead of from evidence.

That leads to avoidable traffic loss.

This checklist works differently. It forces the migration to start with evidence, then move through page types, then into implementation.

Why migrations fail

Most WooCommerce to Shopify migrations fail for predictable reasons:

• the old site is not fully captured before changes begin
• page types are mixed together
• redirects are created too late
• collections are rebuilt without matching intent
• product data is imported but weakened
• internal links are not updated
• tracking is treated as a post-launch task

The result is a successful launch and a broken SEO foundation.

What you are actually moving

A migration moves three things at the same time:

• store data (products, categories, URLs)
• customer journeys (navigation, collections, internal links)
• search history (rankings, links, indexed pages, traffic)

If these are not handled together, the migration may work technically but fail commercially.

Before anything moves: capture the old store

Do this before theme changes, plugin cleanup, URL changes or product pruning.

This is the most important step in the migration.

Create a migration workbook with one row per important old URL. At minimum, include:

• old URL
• page type
• current status code
• canonical target
• title tag
• meta description
• H1
• indexability
• organic clicks
• organic impressions
• revenue or assisted revenue if available
• backlinks or referring domains if known
• Shopify destination URL
• migration decision
• redirect status
• owner
• notes

This is the evidence set you will come back to when someone asks why traffic changed after launch.

If you do not capture this now, you will end up trying to reconstruct the old site after it has already disappeared.

What a successful migration produces

A successful migration produces:

• a complete URL inventory
• a clear map of important pages
• a tested redirect structure
• collections that match real search intent
• products with preserved or improved evidence
• internal links that support key pages
• tracking that can be trusted from day one

If these are missing, the migration is incomplete.

Step 1: separate the migration into page types

Do not treat all WooCommerce URLs the same.

Sort the old site into:

• products
• product categories
• product tags
• filtered or parameter URLs
• WordPress pages
• blog posts
• buying guides
• media attachment URLs
• account, cart and checkout URLs
• search result pages
• legacy redirected URLs

Each group needs a different decision.

A high-value category may need a carefully built Shopify collection. A thin product tag may need to be retired. A blog post may need to move into Shopify’s blog system, stay outside Shopify, or be consolidated into a guide. A filtered URL may not deserve a new indexable page at all.

The checklist only works when page type comes before redirect mapping.

Where to focus first

Do not treat all URLs equally.

Prioritise in this order:

1. High-value URLs (traffic, revenue, backlinks)
2. Core categories and collections
3. Products that support those categories
4. Content that supports discovery
5. Everything else

A store with thousands of URLs usually has a small number that actually matter.

Step 2: identify the URLs that cannot be allowed to fail

Mark priority URLs before the Shopify build begins.

Use four levels:

This prevents the migration being run by page count instead of commercial risk.

A store with 8,000 URLs may only have 300 that really need close SEO protection. Those 300 should drive the launch checklist.

If a URL has backlinks, prioritise its destination carefully.

Step 3: translate WooCommerce categories into Shopify collections

WooCommerce categories and Shopify collections are not the same thing in practice.

A WooCommerce category may have accumulated years of internal links, backlinks, rankings and content. If it becomes a thin Shopify collection with no buying context, no internal support and weak product ordering, the redirect technically worked but the page may still lose value.

For each important category, decide:

• should it become a Shopify collection?
• should it become a parent collection, child collection or buying guide?
• does it represent real search demand?
• does it have enough matching products?
• does it need introductory copy, buying guidance or FAQs?
• which products should support it internally?

Do not let the import tool decide the collection structure by default.

If an old category has traffic, rebuild the intent before mapping the redirect.

If collections are weaker than old categories, fix structure before launch.

Step 4: map products with evidence, not just SKUs

Product import success does not mean product SEO survived.

For important products, check:

• product title quality
• handle/URL destination
• description completeness
• variant structure
• image transfer
• alt text
• reviews
• specifications
• stock status
• schema output after launch
• collection membership
• internal links from collections and guides

A product can import correctly and still become weaker after migration if the supporting evidence is reduced.

If a product imports without evidence, improve the page before relying on redirects.

Step 5: make redirect decisions before launch week

Redirect mapping is not a launch-day job.

Each old URL needs one of these decisions:

• keep equivalent page and redirect one-to-one
• merge into a stronger destination
• redirect to a parent collection
• redirect to a relevant guide
• retire with no redirect if there is no useful equivalent
• investigate before deciding

Avoid lazy bulk rules such as every missing product going to the homepage. That hides problems from launch reports and creates poor user journeys.

For P1 and P2 URLs, every redirect should be checked manually or by crawl before launch.

If redirect decisions are unclear, delay launch rather than guess.

What a risky redirect sheet looks like

The danger usually shows up before launch if the sheet is honest enough.

Watch for patterns like these:

• dozens of old product URLs pointing to one parent collection
• old categories being redirected to the homepage because the Shopify collection is not ready
• blog posts being left blank because nobody owns the content move
• filtered URLs being carried over without a decision about indexation
• discontinued products being redirected to the nearest category without checking whether the intent still matches

A safer sheet makes the problem visible instead of hiding it inside one bulk rule.

For example:

• old URL: /mens-trail-running-shoes/wide-fit/
• proposed destination: /collections/mens-trail-running-shoes/
• real question: does the destination still help someone looking for wide-fit products?

If the answer is no, the redirect is technically valid but commercially weak.

Step 6: protect WordPress content that supports revenue

Many WooCommerce stores rely on WordPress content even when the store owner thinks the content is secondary.

Before deciding what to migrate, identify:

• blog posts that rank
• guides that assist product discovery
• comparison pages
• sizing guides
• care guides
• FAQ pages
• brand/category education pages

Some content should be rebuilt in Shopify. Some may be better consolidated. Some may support collections through internal links rather than existing as isolated posts.

The mistake is treating content as “non-store pages” and moving it after launch.

Step 7: prepare tracking before the switch

Migration reporting fails when analytics is treated as a marketing task rather than a launch dependency.

Before launch, confirm:

• GA4 is receiving test traffic
• ecommerce events work in test orders where possible
• Search Console property access exists
• old and new domains/properties are documented
• Shopify analytics access is available
• paid media pixels are checked
• form/resource conversion events are checked
• launch date annotation is prepared

A broken tracking setup can make a successful migration look like an SEO failure.

If tracking is not ready before launch, diagnosis becomes guesswork.

Step 8: run pre-launch QA on a sample set

Build a sample set that reflects real risk, not just random pages.

Include:

• top 20 organic landing pages
• top 20 revenue-driving products
• top 10 categories or collections
• top blog/guide pages
• backlink target URLs
• discontinued products
• out-of-stock products
• old redirected URLs
• parameter/filter examples

Check each sample against:

• destination URL
• redirect status
• title/H1
• canonical
• indexability
• internal links
• collection membership
• schema output
• tracking event visibility

This is where migration issues should be found, not after launch.

Step 9: launch with a command centre, not a memory

On launch day, keep one shared log with:

• issue found
• affected URL
• severity
• owner
• decision
• fix status
• retest result
• time found
• time resolved

Use severity levels:

• P1: blocks revenue, indexing or major redirect paths
• P2: affects important SEO pages but has a workaround
• P3: should be fixed soon but is not blocking launch
• P4: cosmetic or backlog issue

Without a shared log, launch day becomes a series of private messages and forgotten fixes.

Step 10: monitor the first 14 days by page type

Do not look only at total organic traffic.

Monitor:

• collection clicks and impressions
• product clicks and impressions
• blog/guide clicks and impressions
• top old URLs and their destinations
• redirect errors
• 404s
• indexed pages
• submitted sitemap URLs
• revenue and conversion tracking

A small total traffic drop can hide a serious category problem. A large tracking drop may not be an SEO drop at all.

If internal links are not updated, expect traffic loss even if redirects are correct.

Two failure patterns worth recognising early

Pattern 1: the redirects work but the replacement pages are weaker

This is common when an old WooCommerce category had years of supporting copy, links and product depth, then becomes a thin Shopify collection with little context.

The launch report may show:

• redirects passing
• no major crawl errors
• collections indexed
• lower clicks on category terms

That usually points to replacement-page quality, not redirect failure.

Pattern 2: the products survived but discovery collapsed

Sometimes product URLs recover while collections and guides do not. Revenue may look stable for branded traffic, but non-brand search softens because discovery pages lost their job.

The launch report may show:

• products still indexed
• fewer collection queries
• weaker internal links into key categories
• old supporting content missing or reduced

That usually means the information architecture changed more than the team realised.

The minimum migration checklist

If time is limited, do these before launch:

1. export old URL inventory
2. identify P1 and P2 URLs
3. map important categories to Shopify collections
4. map important products to Shopify destinations
5. preserve or rebuild revenue-supporting content
6. create redirect map
7. test P1 redirects
8. test crawl/index basics
9. test analytics and ecommerce events
10. monitor by page type after launch

This is the minimum standard for a migration where organic traffic matters.

What to use next

If you want a printable review sheet before launch week gets noisy, download the Migration Redirect Risk Review.

If you are still planning the move, start with the full WooCommerce to Shopify migration guide.

If you are building the redirect sheet, use the Shopify redirect mapping guide.

If you are close to launch, move to the Shopify migration QA checklist.

If traffic has already dropped, use the Shopify SEO traffic drop after migration runbook before changing more pages.

A WooCommerce to Shopify migration is not successful because the store launches.

It is successful when the important pages survive.

The checklist is not there to slow the process down.

It is there to stop irreversible mistakes.