How to Migrate a BigCommerce Store Without Downtime (2026)

TL;DR: Zero-downtime BigCommerce migrations require running both platforms simultaneously — not just faster imports. Lower DNS TTL 72 hours before cutover, set up webhook-based order forwarding during the transition, and map 301 redirects for 95%+ of URLs. The DNS switch takes minutes, but plan for 24-48 hours of dual-platform order management while propagation completes.

Why Store Downtime Costs More Than You Think

For a store processing $50,000 monthly, every hour offline means roughly $69 in lost sales. That’s $1,667 daily revenue divided by 24 hours. A typical 6-8 hour “quick migration” costs $414-552 in direct revenue alone. Add abandoned carts, damaged SEO, and frustrated customers hitting a broken checkout — you’re looking at weeks of recovery.

The hidden costs run deeper than lost sales. Customer trust erosion takes 3-6 months to rebuild, and search engines treat site unreliability as a signal to reduce crawl frequency and rankings. Itbrew reports that Forbes Global 2000 companies lose around $400 billion annually to unplanned downtime — roughly $9,000 per minute. Your store operates at a different scale, but the proportional impact on a small business can be just as painful.

Zero-downtime migration isn’t about speed — it’s about running both your old and new platforms simultaneously during the transition. While DNS propagates globally over 24-48 hours, some customers hit your old store, others reach the new one. Both need to work flawlessly.

What Makes Zero-Downtime Migration Work

Three non-negotiable elements make this possible:

1. Parallel Environment Setup Your new BigCommerce store runs on a temporary domain (yourstore.mybigcommerce.com) while your old platform keeps serving customers at your primary domain. You build, import data, configure integrations, and test everything without affecting live sales. The temporary domain lets you share preview links with stakeholders without exposing the unfinished store to customers or search engines.

2. Webhook-Based Order Sync During the transition window, orders arrive at both platforms. Configure webhooks on your old platform to forward order data to BigCommerce’s API in real-time with sub-2-second latency. This creates intentional duplicate orders — you fulfill from BigCommerce, and the old platform order serves as a backup record. This eliminates manual reconciliation and prevents missed transactions.

3. DNS Propagation Strategy DNS propagation takes 24-48 hours to complete globally. During this window, 15-30% of your traffic may still resolve to the old platform’s IP address. Lower your DNS TTL to 300 seconds (5 minutes) at least 72 hours before migration. Some ISPs ignore TTL values entirely, but this reduces the transition window for most visitors.

Timeline: In experience, standard migrations can take 8-16 weeks from planning to post-launch monitoring, while enterprise migrations can take 4-8 months. Data transfer alone can take up to several weeks, depending on if you’re importing the products manually or using an automated tool. The actual DNS cutover happens in minutes.

Pre-Migration: Building Your Parallel Environment

Setting Up Your Staging Store

Sign up for your BigCommerce plan and use the temporary domain as your testing ground.

Configuration checklist:

• Payment gateways in test mode (Stripe, PayPal, etc.)
• Tax calculation rules for all nexus states
• SSL certificate (BigCommerce provides automatically)
• Domain registrar connected but DNS not pointed yet
• Order notifications to a test email address

Third-Party Integration Inventory

Before importing data, audit every app and integration on your current platform. None transfer automatically.

Create an inventory tracking each third-party service:

• Email marketing (Klaviyo, Mailchimp): Subscriber lists export via CSV, but automation workflows must be rebuilt manually — a process that can take days for complex sequences
• Reviews (Yotpo, Judge.me): Export reviews as CSV, map product IDs to new BigCommerce catalog
• Loyalty programs: Rebuild point balances and tier rules in the new system
• Shipping and tax (Avalara, TaxJar): Reconfigure carrier integrations, state nexus rules, and product tax codes
• Inventory management: Reconnect ERP or warehouse systems

Document the current configuration for each one. This prevents the “everything looks good until we go live and realize reviews are missing” scenario.

Exporting Data Without Disrupting Operations

Export while your old store stays live — most platforms support CSV export without disrupting operations.

Sequence: Products first (complete catalog including variants, images, descriptions, pricing) → Customers next (accounts, addresses, order history) → Orders last (for record-keeping only — these won’t import to BigCommerce).

BigCommerce CSV import supports up to 600 variants per product. If migrating from Shopify’s 100-variant limit, you may need to restructure products with extensive option combinations.

Image URLs: Product images often break during migration because URLs change. Download all product images locally before importing, then re-upload to BigCommerce. This prevents broken images when you eventually decommission the old platform.

Passwords: BigCommerce uses bcrypt hashing, which is incompatible with most platforms’ MD5 or SHA256 hashing. Customer passwords cannot transfer. Plan a “We’ve upgraded! Reset your password to access your account” email for launch day — this preempts the inevitable support tickets. You can also put a similar message on the Login page.

The Migration: 7 Steps to Zero Downtime

Steps 1-3: Data Transfer and Theme Setup

Step 1: Import products and categories. For catalogs under 500 products, manual CSV import works fine (2-3 days including verification). For 500-10,000 products, automated tools like Cart2Cart ($69-$499+ depending on product count) handle variants, images, and customer data in 6-8 hours. After import, spot-check your top 50 revenue-generating products for pricing accuracy, correct variant display, image loading, and inventory counts.

Step 2: Configure theme and design. Custom themes need rebuilding in BigCommerce’s Stencil framework — this is where complex migrations can take longer. Test responsive design on mobile devices, since custom CSS can break layouts.

Step 3: Import customer data. Upload customer CSV including email addresses, names, and addresses. Create test customer accounts and verify that login works, saved addresses display correctly, and customer group pricing applies properly.

Steps 4-5: Testing and Pre-Launch Verification

Step 4: Payment gateway testing. Process $1-5 test orders with real credit cards. Cover these scenarios: successful US payment, international payment with currency conversion, declined card handling (does the error message display correctly?), partial refund processing, and subscription/recurring payment setup if applicable.

Step 5: Tax calculation verification. Tax failures account for 40% of post-migration support tickets. Depending on your tax nexus, you may want to test orders in states with sales tax (California, New York), without sales tax (Oregon, Delaware), with county/city taxes (Colorado, Louisiana), and with tax-exempt customer accounts. If using Avalara or TaxJar, verify the integration calculates correctly at checkout.

Steps 6-7: DNS Switch and Order Sync

Step 6: Implement 301 redirects. Research analyzing 127 e-commerce migrations shows sites with 99%+ redirect coverage see less than 5% traffic loss, while those below 95% lose an average of 23% organic traffic. Crawl your old site to export all live URLs, map each to the equivalent BigCommerce URL, and bulk import via BigCommerce’s CSV redirect tool (supports up to 25,000 redirects).

Step 7: DNS cutover and webhook activation. Change your domain’s A record to point to BigCommerce’s IP. Approximately 25% of traffic will still resolve to the old IP in the first 12 hours. Activate webhook forwarding on your old platform to push new orders to BigCommerce’s API in real-time. Keep your old platform operational for 48-72 hours post-cutover.

Handling Orders During DNS Propagation

This is the gap most migration guides skip: what happens to orders while DNS propagates?

About 25% of traffic still hits your old platform 12 hours after the DNS change. By hour 24, it drops to 5-10%, but some ISPs cache DNS for days regardless of TTL settings.

There are multiple approaches to handling this:

Webhook forwarding (technical, most reliable): Configure webhooks on your old platform to forward order data to BigCommerce API with sub-2-second latency. Creates intentional duplicates — fulfill from BigCommerce, keep old orders as backup. Requires developer implementation but eliminates manual work.

Manual reconciliation (simpler, more error-prone): Export orders from both platforms every 6 hours, match by customer email and timestamp. For stores processing 50+ daily orders, this becomes unmanageable quickly. Or simply disable purchasing on the old store when you make the DNS changes and accept that you’ll have a few hours without transactions.

Inventory freeze (safest for limited stock): Pause inventory updates 24 hours before cutover. Accept the small risk of overselling limited-stock items to prevent the worse scenario of simultaneous sales on both platforms.

Customer communication: Send a brief email 24 hours before migration: “We’re upgrading our store this week. You might notice a slightly different look. Your account, order history, and saved information are all safe. If you have any issues logging in, use the ‘Forgot Password’ link.”

Common Migration Failures and How to Fix Them

Checkout fails for logged-in customers: Customer address data imported with formatting issues (missing required fields, invalid state codes). Export addresses from BigCommerce, fix blank fields, re-import, and test with a saved-address account.

3D Secure not configured: International orders decline with “authentication failed.” Enable 3D Secure/SCA in your payment gateway settings and process a test order with a European card.

Tax returns $0.00: Tax rules didn’t import or nexus states aren’t configured. Manually set up tax rules in BigCommerce Settings > Tax and verify API credentials for Avalara/TaxJar.

Broken product images: Image URLs in CSV pointed to old platform’s CDN. Re-upload to BigCommerce’s CDN using the bulk image import tool.

Nobody can log in: Expected — bcrypt vs. MD5/SHA256 incompatibility. Send password reset emails to all customers immediately.

Rollback triggers (act within 4 hours): Checkout rate drops 30%+ below baseline, payment failures exceed 5% of attempts, a critical integration fails completely, or order volume drops to zero.

Post-Migration: The First 72 Hours

Hours 0-12: Monitor checkout completion rate vs. pre-migration baseline, payment authorization success (target >95%), order notification emails, shipping rate calculations, and customer login flow.

Hours 12-24: Review Google Analytics for traffic changes (some fluctuation is normal during propagation), check server response times, and watch support ticket patterns — password resets are expected, checkout errors are red flags.

Hours 24-72: Submit new sitemap to Google Search Console, monitor Coverage report for new 404 errors, verify top 20 organic landing pages are indexed, and confirm 301 redirects are working.

Performance benchmarks: Compare pre- and post-migration load times. Targets: homepage under 2 seconds, product pages under 2.5 seconds, checkout under 2 seconds.

When to decommission: Don’t cancel your old platform immediately. Wait for zero orders at the old platform for 48 consecutive hours, all historical data backed up, and support tickets back to baseline. Safe timeline: 30 days post-migration.

Finding the Right Migration Partner

Simple migrations work fine in-house. Complex stores with custom integrations, B2B functionality, or international storefronts benefit from specialized expertise.

Duck Soup E-Commerce offers a focused approach to BigCommerce migrations. As a solo agency and certified partner since 2011, I use 4-hour focused sessions called Power Blocks — real-time collaboration with direct expert access, no account manager layer, no scope creep. Migrations are broken down into multiple Power Blocks, with sessions dedicated to product importing, theme customization, back-end configuration, etc.

Whether you migrate in-house or with a partner, success comes down to systematic execution: parallel environments, comprehensive redirects, and a plan for managing orders during DNS propagation.

Frequently Asked Questions

How long does a BigCommerce migration take?

Standard migrations may take 8-16 weeks from planning to post-launch monitoring. Data transfer ranges from 2-3 days to 2-4 weeks depending on the complexity and method. The actual DNS switch takes minutes, with 24-48 hours of dual-platform operation afterward.

What tools do I need for zero-downtime migration?

DNS management access, CSV exports from your old platform, a BigCommerce account, and optionally Cart2Cart ($69-$499+) for automated data transfer. You’ll also need a URL crawler for redirect mapping, webhook configuration capability, and Google Analytics plus Search Console for monitoring.

Will I lose SEO rankings?

Not if you implement 301 redirects covering 95%+ of your URLs before switching DNS. Submit your new sitemap to Search Console immediately after launch and monitor the Coverage report daily for two weeks.

How much does migration cost?

DIY: just your BigCommerce subscription ($29-79/month). Automated tools: $69-$499+. Full-service agency: $3,000-$15,000+ depending on complexity. The zero-downtime approach is methodology, not extra tooling.

What happens to orders during DNS propagation?

Orders arrive at both platforms for 24-48 hours. Use webhook forwarding for automatic sync, or manually export and reconcile every 6 hours. Keep both platforms operational throughout.

What data can’t be migrated?

Customer passwords (hashing incompatibility — everyone resets), order history display in customer accounts (BigCommerce limitation), and third-party app configurations (email automations, loyalty tiers, and review workflows require manual rebuild).

Should I migrate during off-peak hours?

Low-traffic timing (2-6 AM) reduces impact if issues occur, but doesn’t change DNS propagation requirements. Launch Tuesday-Wednesday to leave room for fixes before the weekend.

Can I test my store before going live?

Yes. BigCommerce provides a fully functional temporary domain where you can process test orders, configure payment gateways in test mode, and share preview links with stakeholders. Only switch DNS after everything works.

Ready to Migrate Without the Risk?

If you want expert guidance through the technical details, Duck Soup E-Commerce specializes in BigCommerce migrations through focused Power Block sessions that eliminate the typical agency delays. Whether you’re coming from Shopify, WooCommerce, or Magento, the parallel environment approach keeps your store running throughout.

When done successfully, your customers won’t notice the migration happened. That’s the goal.

Want to discuss your migration project? Contact me to schedule a discovery call.