How to Migrate WooCommerce to a New Site Without Losing Data or Sales

We have helped enough store owners through a WooCommerce migration to know how it usually starts: a late night, a new hosting account, and the quiet, creeping fear that one wrong move will wipe out years of orders. That fear is not irrational. Move things in the wrong order and you can corrupt your database, break product URLs, or hand Google a 404-fest that tanks your rankings overnight. The good news? A migrate WooCommerce to new site project follows a clear, repeatable sequence. Get the sequence right and your store lands on the other side with every product, order, customer record, and ranking intact. This guide walks you through exactly that sequence, step by step.

What a WooCommerce Migration Actually Involves

A WooCommerce migration is not just copying files from one server to another. It is moving four interconnected layers at once: your WordPress core and theme files, your WooCommerce plugin and its extensions, your MySQL database (which holds every order, customer record, product, and setting), and your uploaded media.

All four layers must arrive at the new destination in the correct state and pointed at the correct URLs. Miss one layer and you get a store that looks fine on the surface but throws PHP errors, loses checkout functionality, or silently drops order data.

There is also a fifth layer most people forget: your DNS. The moment you point your domain to the new server, traffic shifts. If the new site is not fully ready, real customers hit a broken store. That is why we treat DNS propagation as a step to plan around, not a step to trigger and hope for the best.

If you are coming from a completely different platform rather than just moving hosts, the scope changes. Switching from Magento, for example, requires a full platform conversion before you can even think about hosting. We cover that process in detail in our guide on how to migrate from Magento to a WooCommerce store. Similarly, if you are moving from BigCommerce, our BigCommerce to WooCommerce migration walkthrough covers the platform-specific steps you need.

For this guide, we assume you already run WooCommerce and you are moving it to a new server, domain, or hosting environment.

Before You Touch Any Tools: Pre-Migration Checklist

Speed is not a virtue here. Rushing into a migration without preparation is how stores go down for hours, or days. Run through this checklist before you open a single plugin or FTP client.

Back Up Your Entire Site First

This is non-negotiable. Take a full backup of your live site: files and database together, not just one or the other. A database backup without files is useless if your theme breaks. A files backup without the database loses every order since launch.

Use a plugin like UpdraftPlus or Duplicator and verify the backup actually downloaded by spot-checking the zip file size. A 2 MB backup for a store with 5,000 products is a bad sign. Store the backup somewhere off-server, whether that is Google Drive, Dropbox, or an S3 bucket on AWS.

If you want a tool purpose-built for moving WordPress content across domains, Doubly’s cross-domain copy-paste approach is worth reviewing before you commit to a method. It handles Elementor layouts and WooCommerce products in a way that standard migration plugins often fumble.

Audit Your Current WooCommerce Setup

Before you move anything, document what you have:

• PHP version on the current host (check your hosting dashboard or use phpinfo())
• Active plugins and their version numbers
• WooCommerce version
• Payment gateway settings (Stripe, PayPal, etc., these need reconfiguring on the new site)
• Permalink structure (Settings > Permalinks in WordPress)
• Any custom wp-config.php entries like WP_DEBUG, FORCE_SSL, or custom database prefixes

Also note your current PHP memory limit and max execution time. If the new server runs a lower limit, large order exports will time out. Match or exceed the current environment’s settings before you migrate.

For a side-by-side comparison of migration tools and which ones suit different scenarios, our breakdown of Doubly, Duplicator, WP Staging, and All-in-One WP Migration covers the trade-offs honestly.

How to Transfer Your WooCommerce Store Step by Step

With your backup confirmed and your audit complete, you are ready to move the actual store. Work through these steps in order.

Export Products, Orders, and Customer Data

WooCommerce has a built-in CSV exporter for products (Products > All Products > Export). Use it. Export everything: all columns, all product types. Save the file locally.

For orders, go to WooCommerce > Orders and use the built-in export, or install the free “Order Export & Order Import for WooCommerce” plugin for more granular control. Export all order statuses, not just completed orders. Pending and processing orders represent real revenue.

Customer data lives in your WordPress user table, so it travels with the database rather than a CSV. You do not need to export it separately, but note that customer passwords are hashed. They will work fine on the new site as long as the database arrives intact.

Developers who want to verify data integrity after the move often post their SQL queries on Stack Overflow or cross-reference WooCommerce’s database schema, which is publicly documented on GitHub. Both are useful if you need to audit order counts before and after.

If your product catalog is large, consider using WP All Import or a similar tool to batch the import on the new server rather than running one giant import and waiting for a timeout.

Move Files, the Database, and Your WordPress Install

Here is the sequence we follow on every migration:

1. Set up the new server environment. Install PHP (match the version from your audit), MySQL, and configure a new empty database. Most managed WordPress hosts (Kinsta, WP Engine, Cloudways) handle this through their dashboards without needing command-line access.
2. Transfer files via FTP or SFTP. Upload your entire WordPress directory to the new server’s public root. This includes /wp-content/uploads/, your active theme, and all plugins. FileZilla is the standard free option: most hosts also offer a file manager in cPanel.
3. Import the database. Use phpMyAdmin or the mysql command-line tool to import your .sql dump into the new database you created. Make sure the database name, username, and password match what you put in wp-config.php.
4. Update wp-config.php. Edit the file on the new server to reflect the new database credentials. If the new domain differs from the old one, do not manually edit the database URLs yet.
5. Run a search-and-replace on URLs. Use WP-CLI (wp search-replace 'https://oldsite.com' 'https://newsite.com' --all-tables) or the Better Search Replace plugin to swap the old domain for the new one throughout the database. This step catches serialized data that a simple SQL find-and-replace would break.
6. Test on a temporary URL or hosts file. Before pointing DNS, confirm the store loads, checkout works, and products display correctly. Most hosts provide a temporary staging URL for this.

If you are also planning a platform switch rather than a same-platform move, our guide on moving a Magento store to WooCommerce and our BigCommerce to WooCommerce guide cover the additional data-mapping steps those transitions require.

Post-Migration Tasks That Protect Your Store and SEO

The migration is not done when the site loads on the new server. These post-migration steps are what separate a clean move from one that quietly bleeds traffic and revenue over the following weeks.

Verify all redirects are in place. If your domain or URL structure changed, set up 301 redirects from old URLs to new ones. Use the Redirection plugin or add rules directly to .htaccess. Google Search Console will flag 404 errors if you miss any.

Resubmit your sitemap. Log into Google Search Console and Bing Webmaster Tools. Remove the old property if the domain changed and verify the new one. Submit your XML sitemap immediately so crawlers index the new location fast.

Reconnect payment gateways. Stripe, PayPal, and most other gateways tie API keys to a domain or webhook URL. Update these in your WooCommerce payment settings and run a test transaction with a real card or sandbox account.

Check SSL. Confirm the new server has a valid SSL certificate and that WordPress is set to force HTTPS. A broken SSL on a checkout page will drop conversion rates immediately and trigger browser security warnings.

Test WooCommerce functionality end to end. Add a product to the cart, go through checkout, confirm the order appears in WooCommerce > Orders, and verify the confirmation email sends. Do this with multiple product types if your store carries variable or bundled products.

Monitor server logs for PHP errors. Even if the site looks fine visually, background errors can affect order processing. Check your hosting error log for the first 48 hours after the DNS switch. Most managed hosts surface these in their dashboards.

Update any hardcoded URLs in your theme or plugins. Some older themes or custom code hardcodes the site URL as a string rather than using WordPress constants. Search your theme files for the old domain and replace any instances.

For stores with significant organic traffic, keeping a close eye on Google Search Central’s crawl guidance during the first 30 days is worth the time. Search rankings can dip briefly after a domain migration: that is normal. Sustained drops signal a technical issue that needs investigation.

If you want professional support handling any part of this process, our team at Zuleika LLC offers WordPress development and migration services for stores of all sizes, and our transparent pricing page lays out exactly what is included.

Conclusion

A WooCommerce migration done right is invisible to your customers. Orders keep flowing, URLs keep ranking, and the store just works, now on better infrastructure or a new domain. The difference between a clean migration and a chaotic one almost always comes down to preparation and sequence: backup first, audit before you move, test before DNS, verify after.

If any part of this process feels outside your comfort zone, that is a reasonable place to draw the line and bring in help. Our team at Zuleika LLC has run this process for stores across every industry. Reach out through our contact page and we will scope the work, tell you what the risk points are, and give you a straight answer on what it takes to get your store moved safely.

Frequently Asked Questions About Migrating WooCommerce to a New Site

What does it mean to migrate WooCommerce to a new site?

Migrating WooCommerce to a new site means moving four interconnected layers — WordPress core files, the WooCommerce plugin and extensions, your MySQL database (orders, customers, products), and uploaded media — to a new server or domain. All layers must arrive intact and pointed to the correct URLs for the store to function properly.

What should I do before starting a WooCommerce migration?

Before you migrate WooCommerce to a new site, take a full backup of both files and the database, audit your PHP version and active plugins, document your permalink structure, and note payment gateway settings. Store the backup off-server (e.g., Google Drive or AWS S3) and verify it downloaded completely before touching any migration tools.

How do I update URLs after migrating WooCommerce to a new domain?

Use WP-CLI’s search-replace command or the Better Search Replace plugin to swap the old domain for the new one across all database tables. This correctly handles serialized data that a basic SQL find-and-replace would corrupt, ensuring product links, images, and checkout URLs all point to the new domain.

Will my WooCommerce SEO rankings drop after migrating to a new site?

A brief dip in rankings is normal after a WooCommerce site migration, especially if the domain changes. Set up 301 redirects for all changed URLs, resubmit your XML sitemap in Google Search Console, and monitor for 404 errors. Sustained drops usually indicate a technical issue — missing redirects or broken canonical tags — that needs investigation.

Do I need to reconfigure payment gateways after a WooCommerce migration?

Yes. Payment gateways like Stripe and PayPal tie API keys and webhook URLs to a specific domain. After migrating WooCommerce to a new site, update your gateway credentials in WooCommerce > Settings > Payments and run a test transaction using a sandbox account to confirm checkout works correctly before going live.

What is the best tool to migrate WooCommerce to a new site?

The right tool depends on your store’s size and complexity. Plugins like Duplicator and All-in-One WP Migration handle straightforward moves, while WP Staging suits pre-launch testing. For cross-domain transfers involving Elementor layouts and WooCommerce products, Doubly offers a purpose-built copy-paste approach that standard migration plugins often handle poorly.