How to run WooCommerce and Shopify simultaneously during migration (2026)

Many stores prefer a gradual migration over an overnight cutover. Running WooCommerce and Shopify simultaneously — often called "parallel running" or "dual-platform operation" — lets you test Shopify thoroughly while keeping WooCommerce live. It introduces operational complexity but reduces migration risk, especially for high-volume stores that can't afford downtime or errors.

Why run both platforms simultaneously?

Reasons to choose parallel running over a direct cutover:

• Risk reduction: Shopify is live but not yet the primary domain — issues don't affect sales yet
• Staff training: Ops team can learn Shopify using real orders before it's the only system
• Customer beta testing: Some customers can shop on Shopify staging URL before DNS switch
• SEO safety net: Monitor search rankings on WooCommerce while Shopify builds its search presence
• Big sale timing: Avoid migrating right before Black Friday or other high-traffic events

The dual-platform setup

During parallel operation, you typically have:

• WooCommerce (on yourstore.com): Live, taking real orders, primary domain
• Shopify (on yourstore.myshopify.com or staging.yourstore.com): Live in test mode, accessible via direct URL but not your main domain

Customers continue shopping on WooCommerce. Your team tests Shopify with real products and processes. When ready to cut over, you point your DNS to Shopify.

Inventory synchronization challenge

The biggest operational challenge of parallel running: inventory discrepancy. When a sale happens on WooCommerce, Shopify doesn't know about it — its inventory count becomes incorrect. When you eventually push products to Shopify, the stock levels will be stale.

Approaches to handle this:

Option A: Accept the discrepancy for short parallel runs

For parallel runs under 2 weeks with moderate volume:

• Note the exact inventory counts when you do the initial migration
• Shortly before DNS cutover, do a final inventory sync (export current WooCommerce stock, update in Shopify)
• This creates a 1–2 day window of potential overselling on Shopify, but risk is low if you're not taking Shopify orders

Option B: Disable Shopify inventory tracking during parallel period

Turn off inventory tracking in Shopify until you're ready to cut over. This means Shopify won't enforce stock limits, but since customers aren't shopping on Shopify yet, it doesn't matter. Re-enable inventory tracking and sync counts on cutover day.

Option C: Real-time inventory sync

For stores with high sales volume or long parallel periods:

• Use a sync tool like Trunk, Veeqo, or Katana to sync inventory between WooCommerce and Shopify in real-time
• When an item sells on WooCommerce, the sync tool deducts from Shopify inventory too
• More complex to set up, but maintains accurate stock levels on both platforms

Order management during parallel running

If you're only testing Shopify (not taking real orders), order management is simple: all real orders go through WooCommerce as usual. Staff fulfill from WooCommerce. No change to operations.

If you want to take some real orders on Shopify (e.g., for direct testing):

• Use Shopify's staging URL for select customers or a soft launch
• Process these orders through Shopify's order management
• Keep inventory sync in mind — update WooCommerce inventory for any Shopify sales

DNS cutover: the moment of switchover

The actual migration happens when you point your domain DNS from your WooCommerce hosting to Shopify. This is the highest-risk moment:

Pre-cutover checklist

• All products migrated and verified on Shopify
• Inventory counts updated (final sync)
• All redirects configured (old WooCommerce URLs → Shopify URLs)
• Payment gateway configured and tested on Shopify
• Email notifications verified
• Shipping rates configured
• Tax setup verified
• Abandoned cart / marketing automation reconnected to Shopify

DNS propagation timing

When you change DNS, it takes 1–48 hours to fully propagate worldwide (most users see the change within 1–4 hours). During this window:

• Some customers see WooCommerce, others see Shopify
• Orders placed during propagation may go to either platform

Mitigation: Lower your DNS TTL (Time to Live) to 300 seconds (5 minutes) at least 24 hours before cutover. This speeds up propagation so the transition window is minutes, not hours.

Handling orders during the cutover window

• Brief WooCommerce before cutover: place WooCommerce in maintenance mode 1 hour before DNS change to stop new orders
• Complete any processing WooCommerce orders
• Do the DNS change with the store in maintenance mode
• Once DNS propagates and Shopify is live on your domain, remove maintenance mode
• Gap in orders during maintenance: typically 1–2 hours, acceptable for most stores

Post-cutover: keeping WooCommerce accessible

After Shopify is live on your main domain, keep WooCommerce accessible for:

• Historical order lookups: Pre-migration customer service queries
• Digital download access: Customers with WooCommerce download links
• Refund processing: Pre-migration orders that need refunds
• Analytics reference: Historical revenue data

Keep WooCommerce on a subdomain (e.g., legacy.yourstore.com or woocommerce.yourstore.com). Disable the payment gateways and add a banner saying "This is the archived store — new orders at yourstore.com." Set a no-index robots.txt to prevent the legacy store from competing with Shopify in search.

Timeline for a typical parallel-run migration

Week	Activity
Week 1	Set up Shopify store. Migrate product catalog using k-sync. Configure collections, shipping, taxes, payments.
Week 2	Staff training on Shopify. Verify all products. Set up marketing integrations (Klaviyo, GA4). Test checkout thoroughly.
Week 3	Final QA. Set up URL redirects. Soft launch to select customers on myshopify.com URL. Process feedback.
Week 4	Final inventory sync. DNS cutover. Go live on main domain. Monitor closely.
Week 5+	Keep WooCommerce on subdomain. Address any post-migration issues. Gradually decommission WooCommerce after 3–6 months.

When parallel running doesn't make sense

Parallel running adds complexity. Skip it if:

• Your store has under 500 products and moderate traffic — a direct weekend cutover is simpler
• Your team can dedicate focused time to a fast migration
• You want to avoid the operational overhead of two systems
• Your WooCommerce hosting contract is expiring soon

For most medium-sized stores, a well-planned 3-day direct migration is less risky than weeks of parallel operation with the complexity of dual-platform order management.