WooCommerce to Shopify Migration Checklist: Complex Catalogs

Why Complex Catalogs Break Standard Migration Guides

Most WooCommerce-to-Shopify migration tutorials assume a relatively simple store structure: a few hundred products, straightforward categories, and a flat URL structure. Complex catalogs operate under entirely different conditions, and the gaps between platform architectures become acute at scale. Understanding where those gaps live is the prerequisite to building a reliable checklist.

The Variant Architecture Gap

WooCommerce handles product variations through a flexible attribute system with no hard ceiling on option counts. A single configurable product in WooCommerce can carry dozens of attributes, generating thousands of variant combinations. Shopify’s architecture imposes strict structural limits: a maximum of 3 option types per product and a hard cap of 100 variants per product. As of 2025, Shopify Plus merchants using the Metafields API and specific app integrations can extend this through workarounds, but the native data model does not exceed those bounds.

For a store migrating products where a single SKU carries color (15 options) times size (8 options) times material (3 options) times finish (3 options), that product generates 1,080 theoretical variants in WooCommerce. That product cannot exist in Shopify as a single listing. Your pre-migration architecture work must decide whether to split such products into grouped listings, use metafields to store suppressed attributes, or restructure the product hierarchy entirely using parent-child bundling. This decision must happen before data export, not after.

Taxonomy to Collection Mapping

WooCommerce uses a hierarchical category and tag taxonomy system with unlimited depth and cross-tagging capabilities. Shopify uses a flat collection system, with smart collections driven by automated rules and manual collections for curated groupings. A WooCommerce store with nested categories four levels deep (for example: Apparel > Outerwear > Jackets > Insulated) cannot map directly into Shopify’s collection model without restructuring.

The migration risk here is twofold. First, breadcrumb trails and internal linking structures that depend on category hierarchy break immediately on launch. Second, collection-based navigation that users rely on for discovery must be recreated manually, which introduces inconsistency if the mapping is not documented in advance. Before you export a single product, your team must produce a written taxonomy-to-collection mapping document that specifies exactly how every WooCommerce category becomes a Shopify collection, smart rule, or tag.

URL Structure Divergence

WooCommerce stores commonly use URL patterns like `/product/product-name/` or `/product-category/category-name/product-name/`. Shopify uses `/products/product-handle` and `/collections/collection-handle` as its default patterns. These structures are fundamentally incompatible, which means every single URL on your WooCommerce store becomes a broken link on launch day unless you have built a redirect map in advance and configured it correctly before DNS cutover.

This is not a minor housekeeping task. For stores with 5,000 products and 15 categories, you are looking at potentially 8,000 to 12,000 individual URLs that need redirect entries, including product pages, category pages, tag pages, pagination URLs, and any custom page structures. Google’s index does not care about your migration timeline. If those redirects are not in place at launch, you lose organic ranking positions for every URL that returns a 404.

The Pre-Migration Audit: What to Capture Before You Export Anything

The most expensive mistake in any complex migration is moving data without first understanding the full scope of what you are moving. A thorough pre-migration audit creates the baseline document that every subsequent checklist item references.

Product Data Audit Checklist

Begin by running a complete product inventory export from WooCommerce that captures not just the product data but the metadata that defines your catalog’s complexity. Your audit document must include:

Total product count (published, draft, private, and pending)
Total SKU count including all variants
Products with more than 3 option types (these require rearchitecting before export)
Products with more than 100 variants (these require splitting or restructuring)
Products using WooCommerce-specific custom field types (composite products, bundle products, grouped products)
Products with embedded shortcodes in descriptions (these must be resolved to plain HTML or Markdown before import)
Products with custom attribute sets not present in WooCommerce’s default schema
Any products using WooCommerce Subscriptions, WooCommerce Bookings, or other plugin-managed data that has no native Shopify equivalent

Run this audit against your live database, not a staging snapshot. The live database is the source of truth. Any discrepancy between your audit numbers and what actually exports from WooCommerce will surface as missing products on your new Shopify store.

URL Inventory Export

Use a crawl tool (Screaming Frog, Sitebulb, or Ahrefs Site Audit) to generate a complete crawl of your WooCommerce store before migration begins. Export every URL that returns a 200 status code, including product pages, category pages, tag pages, blog posts, static pages, and any filterable URLs generated by plugins like WooCommerce’s layered navigation. This crawl export becomes the input for your 301 redirect map.

Cross-reference your crawl export against your Google Search Console index coverage report. Any URL appearing in Search Console but not in your crawl needs a redirect entry, because Google has indexed it regardless of whether it currently receives traffic. The complete guide to WooCommerce to Shopify migration details the full scope of what a thorough URL inventory requires.

Order and Customer Data Scope

Complex stores typically have years of order history and customer records that need to migrate for operational continuity: saved addresses, order status lookups, wholesale account tiers, and loyalty point balances. Shopify’s customer import accepts name, email, phone, and address data. It does not natively accept WooCommerce customer roles, user meta fields, or plugin-stored data like points balances and tier designations.

Document every customer data field that exists in your WooCommerce database and explicitly map each one to either a native Shopify customer field, a customer tag, a metafield, or an external data store. Fields that cannot map cleanly need a migration decision before go-live: either accept the data loss, migrate the data to a third-party system, or implement a Shopify app that reintroduces the capability.

Building the 1:1 Redirect Map

The redirect map is the most operationally critical document in any complex migration. Without it, your organic traffic and paid search quality scores take immediate hits on launch day that can take weeks or months to recover. With a complete redirect map configured before DNS cutover, you protect essentially all of your existing SEO value.

Redirect Map Structure and Tooling

Your redirect map must be a spreadsheet with a minimum of three columns: the legacy WooCommerce URL, the destination Shopify URL, and the redirect type (301 for permanent). For large catalogs, building this manually is not feasible. Use a combination of automated matching and manual review.

Automated matching works well for products that migrated cleanly: map the WooCommerce product slug to the Shopify product handle and generate the redirect entry. For categories, match the WooCommerce category slug to the Shopify collection handle. For products that were split or restructured during migration, the automated match will fail and require a human decision about the best destination URL for each legacy path.

The WooCommerce to Shopify SEO migration guide provides the most detailed coverage of redirect implementation available for complex stores.

Common Redirect Edge Cases

Every large store has URL patterns that fall outside the standard product and category structure. These edge cases are where teams most commonly leave gaps in redirect coverage:

Pagination URLs: /product-category/shoes/page/2/ and similar paginated category URLs that may appear in Search Console
Filter and facet URLs: URLs generated by WooCommerce layered navigation that Google has indexed
Old product URLs that already had redirects in WooCommerce (these become redirect chains that need flattening)
Canonical tag mismatches between WordPress pages and WooCommerce product pages
Attachment pages generated by WordPress media uploads
Author archive pages and search result pages that were inadvertently indexed

For each edge case category, your checklist needs a documented decision: either a specific destination URL for the redirect, or a confirmed 410 (gone) response if the content is truly obsolete and has no equivalent destination.

Configuring Redirects in Shopify

Shopify’s native redirect system accepts individual redirect entries through the admin interface and supports bulk CSV import up to 1,000 rows per file. For stores with tens of thousands of redirect entries, use the Shopify CLI or the Admin API to import in bulk. Plan your import process as part of your pre-launch timeline, not as a post-launch task.

After importing redirects, validate a representative sample: pick 50 to 100 legacy URLs from your most important traffic-generating pages and confirm that each one resolves to the correct Shopify destination with a 301 status code. Use a browser extension or command-line tool to check response codes in bulk rather than testing manually one by one.

Accelerating Your Migration Without Cutting Corners

Complex migrations with large catalogs commonly take 6 to 12 weeks to execute properly when accounting for product data restructuring, redirect mapping, theme development, app configuration, and validation. The teams that try to compress this timeline by skipping audit steps consistently create post-launch problems that require that same time investment plus the cost of remediation.

Presta has managed WooCommerce to Shopify migrations for stores with product catalogs ranging from 500 to 50,000 SKUs, and the pattern holds consistently: thorough pre-launch work is the only reliable path to a clean launch. Contact Presta if you want a structured assessment of your catalog’s migration complexity and a realistic project timeline before committing to a go-live date.

Product Data Migration Validation Checklist

After your product data has been imported into Shopify, validation is not optional. Every item on this list should be confirmed before you consider the data migration phase complete.

SKU and Inventory Accuracy

Run a count comparison between your WooCommerce export and your Shopify import:

Total published product count must match between platforms
Total SKU count including all variant combinations must match
Inventory quantities per SKU must match your WooCommerce snapshot as of export time
Products marked as out of stock in WooCommerce must appear as out of stock in Shopify
Products using backordering in WooCommerce need explicit decisions about Shopify’s “continue selling when out of stock” setting

Any discrepancy in SKU count indicates either a failed import, a variant restructuring error, or a data transformation issue in your migration script. Do not proceed past this validation until counts match.

Product Metadata and Attribute Completeness

Check a representative sample of your products against the original WooCommerce records:

Product titles, descriptions, and short descriptions transferred correctly
All product images transferred with correct alt text and ordering
SEO titles and meta descriptions from Yoast or RankMath have been mapped to Shopify’s SEO fields
Custom attributes that were mapped to metafields exist and contain correct values
Product tags represent the correct WooCommerce attribute and tag combinations
Vendor and brand fields populated correctly

For stores using product bundles or composite products in WooCommerce, verify that the app or custom solution handling these in Shopify is correctly reflecting all component products and pricing logic.

Pricing and Tax Configuration

Pricing errors are particularly damaging because they create customer-facing problems immediately on launch. Validate:

Base prices match WooCommerce records for every product tier
Sale prices and scheduled sale dates transferred correctly or are documented as requiring manual re-entry
Tax class assignments match the correct Shopify tax configurations
Compare prices (crossed-out prices showing savings) display correctly on product pages
Any tiered pricing rules (used in B2B or wholesale scenarios) are implemented in Shopify’s B2B features or a third-party app, not simply dropped

The complete guide to WooCommerce to Shopify benefits covers many of the structural improvements in Shopify’s native pricing model that complex stores gain access to after migration.

SEO Validation Before Launch

Search engine optimization validation is one of the most time-sensitive components of the pre-launch checklist. SEO signals that are not correctly configured on launch day begin degrading immediately, and recovery takes weeks of crawl cycles from search engines.

Canonical Tag and Sitemap Validation

Every Shopify product page has a canonical URL. By default, Shopify sets this to the canonical product URL at `/products/handle`. If your product appears in multiple collections, Shopify generates collection-scoped URLs like `/collections/collection-name/products/handle`, but the canonical always points to the primary product URL. Verify that your theme’s `` tags are correctly rendered on all page types: products, collections, pages, and blog posts.

Your XML sitemap in Shopify is automatically generated at `/sitemap.xml`. Before launch, download the sitemap and verify that it includes all published products, collections, pages, and blog posts. Cross-reference the URL count against your product and collection counts as a basic sanity check.

Meta Title and Description Coverage

Every product, collection, and static page needs a populated SEO title and meta description before launch. For large catalogs, do not assume that migrated SEO data transferred correctly. Run a crawl of your Shopify staging environment and export all meta title and description data. Flag any pages with:

Missing meta titles (Shopify will use the page title as a fallback, which is often not SEO-optimized)
Missing meta descriptions (Shopify leaves these empty if not populated, reducing click-through rate)
Meta titles exceeding 60 characters or meta descriptions exceeding 160 characters
Duplicate meta titles across multiple pages

For stores that used Yoast SEO on WooCommerce, your migration script must explicitly map the `_yoast_wpseo_title` and `_yoast_wpseo_metadesc` custom fields from the WordPress database to Shopify’s metafields or the native SEO fields during product import.

Internal Link Audit on Shopify Staging

Your WooCommerce theme likely contained hardcoded internal links pointing to WooCommerce URL patterns. These links survive the migration and immediately become broken links on your Shopify store because the URL structure has changed. Before launch:

Crawl your Shopify staging environment and export all internal links
Flag any links pointing to WooCommerce-pattern URLs (/product/, /product-category/, /shop/)
Update these links in theme code, page content, and blog post content before launch
Use Shopify’s bulk editor where possible to update product description links at scale

Theme and Storefront Validation

The theme layer introduces a distinct category of pre-launch risks. Complex WooCommerce stores commonly rely on WooCommerce-specific shortcodes, PHP template overrides, and plugin-rendered components that have no equivalent in Shopify’s Liquid templating system.

Feature Parity Checklist

Before launch, confirm that every customer-facing feature from your WooCommerce store is reproduced in Shopify:

Product filtering and faceted navigation (requires Shopify’s Search and Discovery app or a paid solution)
Wishlist or save-for-later functionality
Product comparison tools
Size guides, fit calculators, or configurators
Custom checkout steps or upsell flows
Reviews and ratings display, including imported historical reviews
Loyalty program display and redemption flows
Subscription product management for customers

For each missing feature, your launch decision must be explicit: either the feature is reproduced in the new theme, replaced by a Shopify app, deferred to a post-launch sprint with a known timeline, or deprecated entirely. Undocumented feature gaps discovered after launch create customer service escalations and revenue impact.

Mobile and Performance Validation

Shopify’s hosted infrastructure eliminates most of the server-side performance issues that plague self-hosted WooCommerce stores. However, theme code quality, third-party app scripts, and unoptimized image assets can still produce poor Core Web Vitals scores. Before launch, run Google PageSpeed Insights on at least five representative pages: home, collection listing, product detail, cart, and checkout. Target LCP (Largest Contentful Paint) under 2.5 seconds and CLS (Cumulative Layout Shift) under 0.1. The guide on WooCommerce to Shopify faster page speeds benchmarks the typical performance gains available through this migration.

Payment, Checkout, and Fulfillment Configuration

Checkout configuration errors are the most operationally dangerous category of pre-launch issue because they directly block revenue. A checkout that fails silently for a subset of payment methods or order types can run for hours before it surfaces in support tickets.

Payment Gateway Validation Checklist

Shopify Payments or your third-party gateway is live in production mode (not test mode)
All accepted credit card types have been tested end-to-end with real transactions
PayPal, Apple Pay, and Google Pay are configured and tested on real devices
3D Secure authentication flows complete correctly without errors
Currency settings match your WooCommerce configuration for multi-currency stores
Tax calculation is producing correct results for all shipping zones you serve

For stores that were using WooCommerce with a custom payment gateway integration (particularly common in European markets with local payment methods like iDEAL, Klarna, or Przelewy24), verify that the Shopify equivalent integration produces the exact same behavior before cutover.

Shipping and Fulfillment Rules

Complex catalogs often have product-specific shipping rules: oversize item surcharges, fragile item handling fees, dimensional weight calculations, or location-restricted products. WooCommerce handles these through a combination of shipping classes, plugin rules, and custom code. In Shopify, these map to shipping profiles, third-party rate calculation apps, or Shopify Functions for custom logic.

Before launch, test at least one order for each distinct shipping scenario your store handles: standard ground, expedited, freight, international, local pickup, and any product-specific surcharge scenarios. Confirm that rates display correctly at checkout and that orders route to the correct fulfillment location or third-party logistics partner.

Measuring Migration Success: 30, 60, and 90 Day KPIs

Pre-launch work creates the foundation, but the migration is only complete when your post-launch metrics confirm that the transition succeeded without measurable damage to organic performance or conversion rates.

30-Day Metrics

Within the first 30 days after launch, monitor the following closely:

Organic session volume: compare week-over-week against the equivalent period in the prior year, not just against pre-launch numbers (seasonal adjustment matters)
Ranking positions for your top 50 keywords via Google Search Console or a rank tracking tool
404 error rate from Google Search Console’s Coverage report (any new 404s indicate redirect gaps)
Conversion rate compared to your WooCommerce baseline (expect a brief dip in week one as Google recalibrates, but watch for sustained depression)
Average order value and revenue per session as confirmation that pricing and checkout configuration is correct

60-Day Metrics

By the 60-day mark, crawl recalculation should be largely complete for established stores. At this point:

Google Search Console should show declining 404 coverage errors as redirects process
Organic traffic should be recovering toward or exceeding pre-migration baseline
Core Web Vitals report in Search Console should show all URLs in the “Good” category
Cart abandonment rate should normalize relative to your WooCommerce historical average
Customer account creation rate confirms that customer migration did not create friction at login

90-Day Metrics

At 90 days, you have enough post-launch data to make performance conclusions with statistical confidence:

Full organic traffic comparison to the equivalent prior-year period
Revenue attribution from organic channel compared to pre-migration baseline
Return customer rate confirming that migrated customer data is producing repeat purchases
Review of any customer support volume related to migration artifacts: broken links in emails, old bookmarks, or product URLs shared on social media

The WooCommerce to Shopify migration cost and timeline guide provides context for where these numbers typically land across different store sizes and complexity levels.

The Full Pre-Launch Gate: Your Go/No-Go Criteria

The pre-launch gate is the formal checkpoint where your team signs off that migration is complete enough to flip DNS. For complex catalogs, this gate should be a documented meeting with explicit sign-off from technical, commercial, and operational stakeholders.

Technical Go/No-Go Criteria

Before proceeding to live DNS cutover, confirm all of the following:

Product SKU count in Shopify equals product SKU count from WooCommerce export
301 redirect map is fully imported and 100% of sampled redirects return correct 301 responses
SSL certificate is provisioned and active on the Shopify domain
All payment methods tested end-to-end in production mode
All shipping rate scenarios tested and producing correct output at checkout
Email notification templates reviewed and updated to reflect Shopify branding
Core Web Vitals passing for all major page templates in Google PageSpeed Insights
All meta titles, meta descriptions, and canonical tags confirmed in staging crawl
Google Analytics 4 and any other analytics tools are configured and tracking correctly in Shopify
Sitemap submitted to Google Search Console using the new Shopify URL

Commercial Go/No-Go Criteria

All active discount codes and promotional campaigns have been recreated in Shopify
Gift card balances from WooCommerce have been issued as Shopify gift cards or alternate credit
Loyalty program balances are either migrated or a customer communication plan is ready for launch day
B2B customer accounts with wholesale pricing are configured correctly in Shopify B2B or a wholesale app
Any recurring subscriptions are migrated to a Shopify subscription app with customer notification sent

Operational Go/No-Go Criteria

Customer service team has been trained on Shopify admin and order management workflows
Fulfillment and warehouse teams have confirmed receipt of Shopify integration setup
All third-party integrations (ERP, CRM, 3PL, accounting) have been tested with real order flows
A post-launch monitoring schedule with named owners is documented and distributed
A rollback plan exists and has been reviewed, even if the intention is never to use it

The Rollback Plan: Why You Need One Even If You Never Use It

A rollback plan is not an expression of doubt in your migration execution. It is an engineering discipline that every professional migration team documents. For complex catalogs, the rollback window is typically 24 to 72 hours post-launch, after which the operational cost of reverting to WooCommerce (migrating back any orders placed in Shopify, resetting DNS, restoring customer expectations) becomes prohibitive.

Your rollback plan should specify: what triggers the decision to roll back, who has authority to make that call, what the exact technical steps are to restore DNS to WooCommerce, and how long the rollback procedure takes. If your rollback takes more than two hours to execute, your team needs to know that in advance, because it affects how long you can monitor post-launch metrics before the rollback window closes.

The WooCommerce to Shopify migration zero downtime guide covers the DNS switching strategy and monitoring approach in detail.

Frequently Asked Questions

How long does a complex WooCommerce to Shopify migration actually take?

For stores with 1,000 to 10,000 products and a complex catalog structure, a professionally managed migration with a proper pre-launch checklist typically takes 8 to 12 weeks from project kickoff to go-live. This timeline accounts for the pre-migration audit (1 to 2 weeks), product data restructuring and import (2 to 3 weeks), theme development (3 to 5 weeks), redirect mapping and validation (1 to 2 weeks), and a structured QA period of at least one week. Teams that compress this to 4 to 6 weeks are making a deliberate trade-off between speed and risk, and they experience proportionally higher rates of post-launch remediation work. Stores with 10,000 to 50,000 products should budget 16 to 24 weeks for the same process at scale.

What happens to WooCommerce products with more than 100 variants?

WooCommerce products with variant counts exceeding Shopify’s 100-variant ceiling require restructuring before import. The most common strategies are product splitting (dividing one WooCommerce product into multiple Shopify products based on a primary option like color, each of which stays under 100 variants), metafield storage for suppressed attributes (storing additional option values as metafields that are displayed on the product page through custom theme code but do not generate variant records), and bundle or matrix apps that create a custom UI for complex configuration options without relying on Shopify’s native variant system. The correct strategy depends on your product type, your customers’ shopping behavior, and your inventory management approach.

Will my Google rankings drop after migration?

Some short-term ranking fluctuation is normal and expected when a large site changes its URL structure, even with a complete 301 redirect map. Google typically takes 2 to 6 weeks to fully recrawl and recalculate positions for a large site after a domain change or URL restructure. Stores that complete the pre-launch SEO checklist thoroughly, including complete redirect coverage, correct canonical tags, sitemap resubmission, and Google Search Console property update, generally recover to pre-migration organic traffic levels within 60 to 90 days. Stores that launch with incomplete redirect maps or missing meta tags can take 6 to 12 months to recover, and some ranking positions are permanently lost if 404 errors persist long enough.

Do I need to migrate historical order data?

This depends on your operational and legal requirements. From an operational standpoint, migrating order history allows your customer service team to look up past orders in a single system. From a legal standpoint, depending on your jurisdiction, you may be required to retain order records for 3 to 7 years, though this retention can happen in your WooCommerce database or an archived export rather than in live Shopify. From a customer experience standpoint, customers who previously had accounts and can now see their purchase history in Shopify is a positive. However, migrating order history is technically complex and can introduce data integrity issues if not done carefully. Many teams choose to retain WooCommerce in read-only mode for historical order lookups and migrate only active customer account data to Shopify.

How do I handle WooCommerce product bundles in Shopify?

WooCommerce bundles created with the WooCommerce Bundles plugin or similar tools do not have a native equivalent in Shopify. Shopify’s native subscription to bundles is limited. The most reliable Shopify solutions are apps like Bundles.app, Bundler, or Shopify’s own Bundles feature (currently available to all merchants). For complex bundle configurations with component-level inventory tracking, discount rules, and individual product substitution options, you will likely need a combination of a bundle app and custom theme code. Plan bundle migration as a distinct workstream with dedicated development and QA time separate from your core product migration.

What is the best way to migrate customer passwords?

You cannot migrate WooCommerce passwords to Shopify. WordPress stores passwords as bcrypt hashes, and Shopify uses its own authentication infrastructure. When you import customer data, Shopify creates accounts without passwords. Customers receive an email inviting them to set a new password when they first attempt to log in. The practical effect is that returning customers experience one extra step at login on their first visit after migration. The recommended approach is to send a proactive email to your customer base before launch day explaining the new platform and asking them to use the “forgot password” flow on their first login. Framing this as a security update (which it genuinely is, since they are setting a fresh credential) reduces friction and confusion.

Can I migrate WooCommerce subscriptions to Shopify?

Yes, but this requires careful planning. WooCommerce Subscriptions stores recurring billing data in WooCommerce with payment tokens held by your payment gateway. To migrate active subscriptions to Shopify, you need to: select a Shopify subscription app (ReCharge, Skio, and Bold Subscriptions are the most widely deployed), configure the app with your subscription products and billing cycles, export active subscription records from WooCommerce including next billing dates and amounts, and either migrate payment tokens with your gateway’s cooperation or ask customers to re-enter payment methods. Some gateways support token migration, others do not. This negotiation with your payment gateway needs to happen 4 to 6 weeks before your planned go-live date, not during launch week.

What should I monitor in the first 48 hours after launch?

The first 48 hours after DNS cutover are the highest-risk window. Monitor the following in real time: new order volume and payment success rate (a sudden drop indicates checkout configuration issues), 404 error rate from server logs or a monitoring tool (a spike indicates redirect gaps), cart abandonment rate compared to your WooCommerce baseline, customer service contact volume for migration-related issues, Google Search Console for any new crawl errors, and your analytics real-time report to confirm tracking is firing correctly. Assign a named person to each monitoring responsibility for the first 48 hours. Do not rely on automated alerts alone, because some failure modes produce revenue loss without triggering threshold-based alerts.

WooCommerce to Shopify Migration: A Pre-Launch Checklist for Complex Catalogs