Migrating a WooCommerce store requires the same steps as any WordPress migration plus extra care around two things: active orders and payment gateway configuration. A standard WordPress site can tolerate a brief period where the staging environment and production environment are out of sync. A live WooCommerce store takes orders continuously, which means the migration window needs to be managed carefully to avoid lost order data.
This guide covers the full WooCommerce to WP Engine migration process with the specific steps that apply to stores rather than standard WordPress sites.
Before You Migrate: WooCommerce-Specific Checks
Inventory your active extensions. List every WooCommerce extension active on your store. Most work on WP Engine without changes. Check WP Engine’s restricted plugin list for any conflicts. The most common WooCommerce extensions — Stripe, PayPal, WooCommerce Subscriptions, WooCommerce Memberships, Klarna, Shipstation — are all compatible.
Check caching plugins. Any caching plugin you are using on your current host needs to be deactivated after migration. WP Engine’s EverCache handles WooCommerce caching automatically and conflicts with third-party caching plugins. W3 Total Cache, WP Rocket, and LiteSpeed Cache should be deactivated on WP Engine. Your cart and checkout will work correctly without them.
Schedule the migration for a low-traffic window. WooCommerce stores typically have quieter periods — overnight, early morning, or mid-week. Schedule the DNS cutover for that window to minimise the number of orders that could be affected by the transition period.
Notify your payment gateway. Stripe, PayPal, and most payment gateways do not require notification for a host migration since your domain remains the same. However, if you are using a payment gateway with IP-based whitelist restrictions, update the whitelist with WP Engine’s outbound IP ranges before going live.
Step 1: Create a WP Engine Environment and Run the Migration
Create a new environment on your WP Engine account and use WP Engine’s automated migration plugin (BlogVault) to transfer your store. Install the plugin on your current WooCommerce site, connect it to your WP Engine environment, and run a full migration (files and database). The migration process is the same as for any WordPress site.
Full instructions for the migration plugin process are in How to Migrate from cPanel Hosting to WP Engine. For Bluehost specifically: How to Migrate from Bluehost to WP Engine.
For large stores with databases over 1GB, the automated migration plugin may time out. WP Engine’s support team offers assisted migrations for large stores — contact them before starting if your database is very large.
Step 2: Test Your Store on the WP Engine Temporary URL
After migration, access the store on the WP Engine temporary URL (yourenv.wpengine.com). Test thoroughly before cutting over DNS:
- Browse product catalogue and individual product pages
- Add products to cart and verify cart totals calculate correctly
- Complete a test order using a payment gateway test mode (Stripe test cards, PayPal sandbox)
- Verify order confirmation emails send correctly
- Check that WooCommerce admin shows orders, products, and customer data correctly
- Test any subscription or membership renewals in test mode if applicable
Deactivate your old caching plugin if still active (W3 Total Cache, WP Rocket, etc.) — EverCache handles caching automatically on WP Engine and conflicts with third-party caching plugins.
Step 3: Handle the Order Gap During DNS Cutover
This is the step unique to WooCommerce migrations. Between when you run the final migration sync and when DNS fully propagates, some visitors are still on the old host. Orders placed during this window land in your old host’s database, not the new WP Engine environment.
The cleanest way to handle this is to put your WooCommerce store into maintenance mode or add a banner on the checkout page for the duration of the DNS cutover window (typically 1 to 4 hours). This is not always practical for busy stores. The alternative is to manually export orders from the old host’s WooCommerce after DNS has propagated and import them into the WP Engine environment, reconciling any orders that landed in the old database during the cutover window.
For stores with steady order flow, scheduling the cutover at 2am local time and completing the DNS propagation before the next business day minimises the gap window.
Step 4: Go Live and Verify Payment Processing
After DNS propagation completes and SSL is active on WP Engine, switch your payment gateway from test mode back to live mode. Place a small real transaction to confirm the payment gateway is processing correctly on the new host. Check that order confirmation emails and payment receipt emails are sending from the correct address.
Monitor your WooCommerce order inbox and payment gateway dashboard for the first 24 hours after migration to catch any issues early. Check your WP Engine error log for any PHP errors that did not appear during staging testing. For how to access and read error logs, see How to Read and Debug WordPress Error Logs.
Frequently Asked Questions
Will orders be lost during the WooCommerce migration?
With careful planning, no orders are lost. The key is managing the DNS cutover window: schedule it during low-traffic hours, keep your old site live until full propagation, and reconcile any orders placed during the transition period. WP Engine’s support team can advise on strategies for stores with high continuous order volume.
Do I need to reconfigure my Stripe or PayPal account after migrating to WP Engine?
No. Stripe and PayPal are configured with API keys stored in your WooCommerce settings, which migrate with your database. Since your domain stays the same, your payment gateway webhook URLs remain valid. Verify that live mode is active after migration (not test mode) and place a small test transaction to confirm payment processing is working correctly.
How long does a WooCommerce migration to WP Engine take?
The automated migration plugin transfer takes 15 minutes to 2 hours depending on store size. Testing on the WP Engine temporary URL adds another hour for thorough testing. DNS propagation takes 1 to 4 hours typically. Total elapsed time from starting the migration to a fully live store on WP Engine is typically 3 to 6 hours, most of which is waiting for DNS propagation rather than active work.
