Migrate WooCommerce Data to New Site: 2026 HPOS Guide

TL;DR

Migrating WooCommerce data to a new site means moving your products, orders, customers, SEO metadata, and store configurations from one WordPress installation to another (or to a different platform entirely). The process sounds straightforward but hides serious traps: customer passwords won’t transfer across platforms, 42% of sites lose organic traffic from botched redirects, and WooCommerce’s newer HPOS order storage changes the database structure in ways most migration guides ignore. This article covers every data type, method, tool, and pitfall so you can move your store without losing sales or customers.

Planning a migration and want expert guidance before you start? Request a free brand audit to identify risks in your current setup.

What Does “Migrate WooCommerce Data to New Site” Mean?

Migrating WooCommerce data to a new site is the structured process of transferring your entire store, including its products, orders, customer records, payment configurations, and SEO equity, from one environment to another while keeping everything functional.

That definition is simple. The execution is not.

A standard WordPress migration already involves databases, themes, plugins, and media files. A WooCommerce migration adds layers of complexity because you’re also moving transactional data (orders, refunds, subscriptions), payment gateway credentials, tax configurations, and shipping rules that must work correctly the moment the new site goes live. A broken product page is annoying. A broken checkout costs real money.

Three Migration Scenarios

Not every WooCommerce migration is the same. The scope, risk, and tooling differ based on what you’re actually changing:

Host-to-host migration. Same WooCommerce installation, same domain, new server. This is the simplest scenario. Your URLs stay the same, so SEO risk is minimal. The main concern is downtime during DNS propagation.

Domain change migration. You’re keeping WooCommerce but switching your domain name (or restructuring your URL paths). This introduces major SEO risk because every URL changes. You’ll need a comprehensive 301 redirect map, and even with one, expect a temporary traffic dip.

Platform migration. Moving from WooCommerce to Shopify (or vice versa). This is the most complex scenario because data structures differ between platforms, certain data types simply can’t transfer, and payment integrations need complete reconfiguration.

Understanding which scenario you’re facing determines everything else: which tools to use, what data you can preserve, and whether you should handle it yourself or bring in help.

What Data Actually Migrates (and What Doesn’t)

The phrase “migrate WooCommerce data” sounds like a single operation. In reality, a WooCommerce store contains at least nine distinct data types, each with its own export method, formatting quirks, and failure modes.

Products

What’s included: Title, description, SKU, price, sale price, images, variations, categories, tags, custom fields, stock levels, weight, and dimensions.

Common gotcha: Variable products sometimes import as simple products if the variation structure isn’t mapped correctly. If you use product feed tools or custom attributes heavily, expect manual cleanup after import.

Orders

What’s included: Order status, line items, payment method, totals, shipping and billing addresses, order notes, tracking numbers, refund records.

Common gotcha: Order IDs may not be preserved when migrating between platforms. If your customer service team references order numbers in emails or your accounting software ties to specific order IDs, this creates confusion. On WooCommerce-to-WooCommerce moves, ID preservation is possible but requires careful database handling.

Customers

What’s included: Email addresses, names, shipping and billing addresses, order history, account metadata.

Common gotcha: Customer passwords are the single biggest pain point in any cross-platform migration. More on this below, because it deserves its own section.

Coupons and Discount Codes

What’s included: Coupon code, discount amount or percentage, usage limits, expiry dates, minimum spend rules, product restrictions.

Common gotcha: Complex conditional rules (like “buy 3 of category X, get 15% off category Y”) rarely map cleanly between platforms. These typically need manual recreation.

Product Reviews

What’s included: Star rating, review text, customer name, date posted.

Common gotcha: Reviews are frequently forgotten during migration because they live in WordPress comments rather than WooCommerce-specific tables. Losing reviews means losing social proof, which directly affects conversion rates.

SEO Metadata

What’s included: Meta titles, meta descriptions, URL slugs, canonical tags, structured data configurations.

Common gotcha: If your URL structure changes at all, every indexed page needs a 301 redirect. Miss this step and you’ll join the 42% of websites that lose traffic after migration due to improper redirects, according to Search Engine Journal data.

Blog Posts, Pages, and Media

What’s included: All WordPress posts, pages, categories, tags, and uploaded media files.

Common gotcha: Media file paths must be updated post-migration. Broken image links won’t just hurt your store’s appearance; they damage SEO through poor user experience signals.

Subscriptions

What’s included: Billing cycles, renewal schedules, payment gateway tokens, subscriber status.

Common gotcha: Subscriptions are the highest-risk data type to migrate. Gateway tokens are often tied to your specific domain and merchant account. If tokens break, recurring billing stops, and customers churn without you realizing it immediately.

Digital Downloads

What’s included: File paths, download permissions, purchase records.

Common gotcha: File paths must be updated to point to the new server’s directory structure. Customers who purchased before migration may lose access to their downloads if permissions aren’t remapped.

What Generally Does NOT Migrate Cleanly

Three things consistently break across nearly every WooCommerce migration scenario:

Customer passwords (cross-platform)
Payment gateway OAuth tokens (domain-bound)
Theme settings and plugin configurations (platform-dependent)

Knowing what breaks is just as important as knowing what transfers.

Migration Methods: Five Approaches Explained

The right method for migrating WooCommerce data to a new site depends on your store’s size, complexity, and destination platform. Here’s what each approach actually involves.

Method 1: WooCommerce Built-in CSV Export/Import (Free)

WooCommerce includes native export and import tools for products, orders, and coupons. You export to a CSV file, then import that CSV on the target site.

Best for: Small stores with fewer than 500 products and simple catalog structures.

Limitation: This method does not handle media files, plugin settings, theme configurations, or customer accounts. It’s a data-only transfer, not a full site migration.

Method 2: Full-Site Migration Plugins

For WooCommerce-to-WooCommerce moves where you want everything transferred (database, plugins, themes, media, configurations), tools like All-in-One WP Migration, Duplicator Pro, and Migrate Guru handle the entire package.

A critical detail from ServMask (the maker of All-in-One WP Migration): do not install WooCommerce or any other plugins on the new site before running the migration. The plugin brings everything over from your existing store, including all plugin files, themes, and configurations. Installing plugins first creates conflicts.

Best for: Host-to-host moves where you want an exact copy of your current store.

Method 3: Data-Specific Plugins

When you need granular control over what migrates and how fields map between source and destination, plugins like WP All Import/Export ($199/year) and Store Exporter/Importer Deluxe offer drag-and-drop field mapping.

Practitioners report strong results with this approach for complex catalogs. In testing on a staging store, a 14,000-product export with Store Exporter Deluxe completed in roughly 40 minutes, and because the output was already mapped to WooCommerce field names, the import required zero manual column mapping.

Best for: Stores with complex product data, custom fields, or catalog structures that need transformation during migration.

Method 4: Automated Cross-Platform Services

For platform-to-platform moves (WooCommerce to Shopify or the reverse), Cart2Cart and LitExtension automate much of the data mapping between different systems.

Cost benchmark: a store with 10,000 products and 50,000 orders typically runs $300 to $600 through Cart2Cart. However, these services don’t handle metafields, custom attributes, or complex variant structures elegantly. Plan for manual cleanup afterward.

Best for: Cross-platform migrations where speed matters more than perfect data fidelity.

Method 5: Manual Database Migration (phpMyAdmin/WP-CLI)

The most granular approach. You export and import specific database tables directly through phpMyAdmin or use WP-CLI commands to handle the transfer programmatically.

Best for: Developers who need precise control, particularly when dealing with HPOS table structures (covered below) or custom database modifications. Not recommended for non-technical store owners.

Quick Decision Framework

Store Profile	Recommended Method
Under 500 products, same platform, simple catalog	Built-in CSV or full-site plugin
500 to 5,000 products, custom fields, same platform	Data-specific plugin (WP All Import)
Any size, host-to-host, exact copy needed	Full-site plugin (Duplicator, All-in-One)
Any size, cross-platform move	Cart2Cart or LitExtension + manual cleanup
Complex integrations, HPOS concerns, subscriptions	Manual database migration or professional help

The HPOS Factor: Why 2026 Migrations Are Different

This is something almost no migration guide addresses, yet it directly affects how your order data is structured and transferred.

What HPOS Is

HPOS (High-Performance Order Storage) is WooCommerce’s modern order storage system. Instead of storing orders as custom post types in the wp_posts and wp_postmeta tables (the “legacy” approach), HPOS uses dedicated custom tables: wp_wc_orders, wp_wc_order_addresses, wp_wc_order_operational_data, and wp_wc_orders_meta.

WooCommerce made HPOS the default for new stores starting with version 8.2, released in October 2023. The performance gains are substantial: 5x faster order creation and 40x faster backend filtering speeds.

Why HPOS Matters When You Migrate WooCommerce Data

If you’re moving a store built on HPOS to a target site still running legacy storage (or vice versa), the underlying table structures don’t match. Importing orders into a site where orders with matching IDs already exist can cause overwrites or conflicts.

Before migrating, check which storage mode both your source and destination stores use:

Go to WooCommerce > Settings > Advanced > Features
Look for the “Order data storage” option
Note whether it says “High-performance order storage” or “WordPress posts storage”

If both stores use the same mode, standard migration tools work as expected. If they differ, you’ll either need to sync the storage mode before migrating or use tools that account for the table structure differences.

This is a 2026-specific concern that will only become more relevant as WooCommerce continues phasing out legacy storage.

What Breaks During Migration: The Five Biggest Pitfalls

1. Customer Passwords Won’t Transfer Across Platforms

WooCommerce passwords are hashed using WordPress’s encryption algorithm. Shopify uses a completely different system. You cannot migrate hashed passwords between platforms, and no responsible platform stores plain-text passwords that could be copied over.

The business impact is real. A merchant on the Shopify community forum who migrated 3,941 customers discovered that imported customers couldn’t even use the standard password reset function. Instead, customers had to contact the store owner to receive an “account invite” manually.

Agency practitioners warn that without proactive customer emails before launch explaining the password reset process, stores should expect a 20 to 40% spike in support tickets and a measurable drop in returning-customer conversion rates during the first two weeks after migration.

For WooCommerce-to-WooCommerce moves, passwords can transfer. Migration plugins like WebToffee handle both plain text and WordPress hashed passwords, identifying the encryption type and performing the import securely.

2. SEO Traffic Loss From Missing Redirects

This is the most common and most damaging migration failure. According to industry data, stores without proper 301 redirects typically experience 40% traffic drops within three weeks of launch.

A real-world example: a store owner in Texas migrated her WooCommerce store to a new host without a backup, redirect map, or staging test. Within 48 hours, her organic traffic dropped 70%, not because Google penalized her for moving, but because 400+ product URLs silently returned 404 errors.

Even WooCommerce’s own parent company failed at this. They switched from WooCommerce.com to Woo.com, and the migration disaster caused such severe traffic losses that they completely reversed course in April 2024.

The good news: implementing proper redirects and resubmitting sitemaps can help sites retain 85 to 90% of their organic traffic within 30 days. For a deeper look at protecting your search visibility, see our ecommerce SEO strategies playbook.

3. Payment Gateway Tokens Get Invalidated

Most OAuth-based payment gateways (Stripe, PayPal, Square) bind their authentication tokens to your domain. When your domain changes, those tokens stop working.

After migration, go to WooCommerce > Settings > Payments and reconnect each gateway. For Square specifically, you’ll need to disconnect and reconnect your Square account since the OAuth token is domain-bound. Test a real transaction (even a $1 charge that you refund) before going live.

4. Subscription Renewal Failures

If your store runs WooCommerce Subscriptions, the payment gateway tokens that power automatic renewals are tied to your original domain and merchant credentials. A migration can silently break these tokens, meaning renewals fail and subscribers churn without any immediate alert.

Test subscription renewals in staging before going live. This is non-negotiable for stores where recurring revenue represents a significant portion of income.

5. Broken Internal Links and Orphaned Images

Media file paths, internal links between products, and cross-references in blog content all contain hard-coded URLs. If those URLs change and aren’t updated, you end up with broken images, dead links, and a poor user experience that hurts both conversions and SEO.

Tools and Plugins Comparison (2026)

Tool	Best For	Starting Price	Key Strength
WooCommerce Built-in	Simple product export	Free	Native, no plugin needed
All-in-One WP Migration	Full-site host moves	Free / $69 pro	One-click, includes everything
Duplicator Pro	Host-to-host	$49.50/yr	Full site backup + restore
WP All Import/Export	Complex catalog moves	$199/yr	Drag-and-drop field mapping
Store Exporter Deluxe	WooCommerce-to-WooCommerce	Premium	125+ plugin integrations
Cart2Cart	Cross-platform automation	$69+	85+ platform support
LitExtension	Managed migration	$69+	Password migration support
Matrixify	Large Shopify imports	Subscription	Handles metafields, bulk operations

Practitioners on Reddit and WooCommerce forums consistently recommend running any automated tool on a staging site first. The cost of a staging environment is negligible compared to the cost of corrupted production data.

Pre-Migration and Post-Migration Checklists

Before You Migrate

Full backup. Database, files, media, everything. Store it somewhere outside both the source and destination servers.
Data inventory. Document every data type you need to transfer. Use the list from Section 2 as your starting template.
Staging setup. Build the target site on a staging domain. Never migrate directly to production.
SEO audit. Export all current URLs, meta titles, and meta descriptions. This becomes your redirect map baseline.
Redirect map. Create a spreadsheet mapping every old URL to its new equivalent. Every single one.
Plugin and theme compatibility check. Verify that every plugin on your source site has a compatible version for your target environment.
Payment gateway documentation. Record every gateway’s API keys, webhook URLs, and OAuth configuration.
Customer communication plan. Draft the email you’ll send to customers about any changes, especially password resets.

After You Migrate

URL verification. Crawl the new site with Screaming Frog or a similar tool. Check for 404s, redirect chains, and broken internal links.
Payment testing. Process a real test transaction through every active payment gateway. Refund it afterward.
Order workflow test. Place a test order, verify the confirmation email fires, check that inventory decrements, and confirm the order appears correctly in your dashboard.
Customer notification. Send the password reset email (for cross-platform moves) or the “we’ve moved” communication.
Search Console resubmission. Submit your updated sitemap to Google Search Console. If you changed domains, use the Change of Address tool.
Monitor for 30 and 90 days. Track organic traffic, indexing status, conversion rates, and customer support ticket volume. Sites with pre-migration audits recover 95% of traffic within 30 days versus 90+ days without one.

After the migration dust settles, turn your attention to growth. If you moved to Shopify, these revenue-boosting strategies help you capitalize on a fresh platform. For broader post-migration optimization, our guide to optimizing website conversion rates covers what to prioritize first.

When to DIY vs. When to Hire an Expert

Not every WooCommerce migration needs professional help. But some absolutely do.

DIY Makes Sense When:

Your catalog has fewer than 500 products with simple structures
You’re doing a host-to-host move on the same platform
You have no subscriptions or recurring billing
Your organic traffic is minimal (low SEO risk)
You’re comfortable with WordPress admin and basic database concepts

Professional Help Makes Sense When:

You’re migrating cross-platform (WooCommerce to Shopify or the reverse)
Your catalog exceeds 1,000 products with variations and custom fields
You have active subscriptions that generate recurring revenue
Your store has significant organic traffic and SEO equity to protect
You run complex integrations (ERPs, multi-channel inventory, custom APIs)
Your LTV and CAC metrics show that even a brief disruption to returning-customer revenue would be costly

A practitioner on a WooCommerce forum summed it up: “Most store owners worry about moving products, but the real damage often comes from lost customer data, broken redirects, failed subscriptions, payment issues, and disconnected integrations after launch.” The obvious data transfers are the easy part. It’s the invisible dependencies that cause expensive failures.

If your migration involves meaningful complexity, an experienced ecommerce team can run the entire process, from pre-migration audit through post-launch monitoring, while you keep selling.

Get a free brand audit to assess your store’s migration readiness and build a 90-day action plan.

Frequently Asked Questions

Can I migrate WooCommerce to Shopify without losing data?

You can transfer most data: products, customers, orders, and reviews. But you will lose customer passwords (they must reset), complex coupon logic (needs manual recreation), and some custom field data that doesn’t have a Shopify equivalent. Automated tools like Cart2Cart handle the bulk transfer, but budget time for manual cleanup and testing.

Do customer passwords transfer during migration?

Between two WooCommerce sites, yes. WordPress-hashed passwords can be imported by plugins that recognize the hash format. Between WooCommerce and Shopify (or any other platform), no. The encryption methods are incompatible. Plan to send customers a password reset email before or immediately after launch to avoid a flood of support tickets.

How long does a WooCommerce migration take?

A small store (under 500 products) with a host-to-host move can complete in a few hours. A mid-size store (1,000 to 10,000 products) with cross-platform migration typically takes 1 to 3 weeks including staging, testing, and post-launch monitoring. Enterprise stores with subscriptions and complex integrations may need 4 to 8 weeks.

Will I lose my Google rankings if I migrate?

Not if you handle redirects properly. Implementing 301 redirects for every changed URL and resubmitting your sitemap to Search Console can preserve 85 to 90% of your organic traffic within 30 days. Skip this step and you risk the kind of 70% traffic drop that takes months to recover from.

What is HPOS and does it affect my migration?

HPOS (High-Performance Order Storage) is WooCommerce’s modern database architecture for storing orders in dedicated tables rather than the generic WordPress posts table. It became the default in October 2023. If your source store uses HPOS but your target store uses legacy storage (or the reverse), order data won’t align cleanly during import. Check both stores’ settings before starting.

How much does it cost to migrate WooCommerce data to a new site?

Free if you use WooCommerce’s built-in CSV tools for a simple move. $50 to $200 for plugin-based full-site migrations. $300 to $600 for automated cross-platform services handling 10,000+ products. Professional agency migrations for complex stores typically start in the low four figures depending on scope.

Should I keep my old site running during migration?

Yes. Keep the old site live until the new site is fully tested and DNS has propagated. This ensures zero downtime for customers and gives you a fallback if something goes wrong. Only take the old site offline after you’ve verified every page, tested every payment gateway, and confirmed that redirects are working correctly.

What’s the most commonly forgotten data type during migration?

Product reviews. They live in WordPress’s comments table rather than WooCommerce-specific tables, so they’re easy to overlook. Losing reviews means losing the social proof that drives purchase decisions, an especially painful loss for stores that spent years building review counts.

Migrating WooCommerce data to a new site is a business operation, not just a technical task. The stores that come through it cleanly are the ones that plan for what breaks, not just what transfers. Whether you’re switching hosts, changing domains, or moving platforms entirely, the checklists and decision frameworks above give you a clear path forward.

If your migration involves significant revenue at stake, talk to the D2C growth team at EZCommerce before you start.