Ecommerce Migration Testing: What Should You Test Before Launch?
What to test before an ecommerce migration launch: checkout, payments, shipping, tax, accounts, data, integrations, redirects, SEO, analytics and performance.
Quick answer
Before launching a migrated store, test the flows that make money first: checkout with every payment method, market and shipping option, taxes, discounts and gift cards, then order flow into fulfilment, ERP and customer notifications. Validate migrated data with counts, totals and samples, test customer accounts, check every redirect automatically, verify SEO elements and analytics, and test performance, accessibility and mobile. Run several test cycles with the people who use the store daily, and fix and retest before go-live.
Why Migration Testing Is Different
A new store isn't only new code; it's new data, new integrations, new URLs and new configuration, all switched on at once. Problems often appear at the boundaries: a tax setting that works for one market but not another, an integration that handles standard orders but not partial refunds, redirects that miss uppercase URLs. Testing must cover these edges.
This article is the test plan. For the checklist of preparation tasks, see migration checklist; for launch day, see launch plan.
Test Priorities
| Priority | Area | Why |
|---|---|---|
| 1 | Checkout, payments, shipping, tax | Revenue and legal correctness |
| 1 | Order flow to fulfilment and finance | Orders must ship and reconcile |
| 2 | Customer accounts and data | Customer access and service |
| 2 | Redirects and SEO | Traffic protection |
| 2 | Analytics and tracking | Measuring the launch |
| 3 | Performance, accessibility, mobile | Experience quality |
| 3 | Content and merchandising | Presentation |
Checkout and Payments
- Every payment method, including wallets and instalments
- Every market and currency
- 3-D Secure and authentication challenges
- Declined payments and error messages
- Guest and signed-in checkout
- Discount codes, automatic discounts and gift cards
- Taxes and duties correct by market
- Order confirmation page and email
- Small live orders placed and refunded before launch
Shipping, Fulfilment and Operations
- Shipping rates and options by zone
- Pickup and local delivery
- Orders reaching the warehouse or 3PL correctly
- Split shipments and partial fulfilment
- Tracking numbers returning to orders and customers
- Cancellations, refunds, returns and exchanges
- Inventory updates in both directions
Data Validation
Compare record counts and totals between the old and new systems, check random samples and edge cases (products with many variants, customers with many orders), and test relationships. See ecommerce data migration.
| Data | Test |
|---|---|
| Products and variants | Counts, prices, options, images, SEO fields |
| Collections | Membership and ordering |
| Customers | Counts, addresses, consent, tags |
| Orders | Counts, totals, statuses, refunds |
| Gift cards and credit | Balances |
| Content | Pages present, links working |
Need an independent test plan before go-live?
ZSpace Labs plans and runs migration testing across checkout, data, integrations, SEO and performance.
Customer Accounts
Test as migrated customers: activating accounts or signing in (passwords usually don't migrate), viewing order history, reordering, managing addresses, subscriptions and loyalty balances. Check activation emails render correctly and links work.
Integrations
Run end-to-end scenarios through every integration: ERP, OMS, WMS or 3PL, payments, tax, email and SMS, CRM, reviews, search, loyalty and marketplaces. Include failure scenarios: what happens when an integration is down, and whether messages are retried without duplicates. See OMS integration.
Redirects and SEO
Test the full redirect map automatically, then spot-check high-value URLs by hand. Crawl the new site to compare titles, meta descriptions, canonicals, headings, structured data and internal links with the old crawl. Check robots rules and sitemaps. See URL migration and SEO migration.
- Every old URL returns one permanent redirect to the right destination
- Destinations return 200
- Titles, descriptions, headings match or improve
- Canonicals and structured data valid
- No noindex or robots blocks left from staging
- Sitemaps list only final URLs
Analytics and Tracking
Check that analytics records page views and ecommerce events with the same names and parameters as before, that purchases match platform orders, that ad pixels fire with consent respected, and that consent banners work in each market. Changes to tracking during migration make performance comparisons unreliable. See event tracking.
Performance, Accessibility and Mobile
Measure page speed for key templates on mobile and compare with baselines. For high-traffic stores, load test checkout and search. Test key journeys with keyboard and a screen reader, and run automated accessibility checks on templates. Check layouts on common phones and tablets. See accessibility checklist.
Security Basics
Before launch, review staff and app access, remove test accounts and staging credentials, check scripts on checkout-adjacent pages, confirm HTTPS on all domains and review integration credentials. Custom code and headless builds may warrant professional security testing. See security audit.
User Acceptance Testing
The people who run the store should test their own work: merchandisers updating products and collections, customer service finding orders and issuing refunds, operations processing fulfilment, finance checking reports. Give them scripted scenarios and a way to log issues with severity.
Managing Issues
Log every issue with steps to reproduce, severity and owner. Agree go-live criteria in advance: no open critical issues in checkout, payments, order flow or redirects; known minor issues documented with fixes scheduled. Retest fixes before closing them.
| Severity | Example | Launch rule |
|---|---|---|
| Critical | Payment method failing, orders not reaching warehouse | Must fix |
| High | Tax wrong in one market, many redirects wrong | Must fix or scope out market |
| Medium | Account page layout issue | Fix soon after launch |
| Low | Cosmetic issues | Backlog |
A Test Cycle Plan
| Cycle | Focus | Data |
|---|---|---|
| 1 | Functional and integration testing | First data rehearsal |
| 2 | Fixes retested, UAT with store teams | Second rehearsal |
| 3 | Full regression, redirects, performance | Production-like data |
| Launch | Smoke tests, live payments | Final migration |
72 Hours After Launch: Check and Roll Back
Testing doesn't stop at go-live. Many migration problems only show up with real customers, real payment methods and real volumes, so plan the first 72 hours as a watch period with named owners, set check times and agreed triggers for a hotfix or a rollback. Decide before launch who can call a rollback, and confirm that the old platform, its data and DNS settings stay available until the window closes.
- Rollback or hotfix trigger: any payment method failing for real customers
- Rollback or hotfix trigger: orders not reaching fulfilment, or reaching it twice
- Rollback or hotfix trigger: tax or shipping charged wrongly in a market you sell to
- Rollback or hotfix trigger: customers unable to sign in or reach order history at scale
- Hotfix, not rollback: missed redirects, broken tracking or cosmetic issues
| When | Check | Owner |
|---|---|---|
| First 2 hours | One live order per payment method, then refund it; orders reach the warehouse, 3PL or ERP; confirmation and shipping emails send; top redirects resolve; the purchase event fires once per order | Project lead, operations |
| First 24 hours | Orders, payments and fulfilment messages match across systems; failed payment and checkout error rates; 404 log for missed redirects; support tickets grouped by theme | Operations, developer, customer service |
| 24 to 72 hours | Full redirect list re-run; spot-check taxes and shipping by market; first payout and transaction report compared with orders; integration error logs and retry queues; tracking compared with platform orders | Developer, finance, marketing |
First 30 Days: Operational Reconciliation
Some problems only appear once money, stock and customers have gone through a full cycle. For the first 30 days, reconcile operations weekly with the people who own each area, and keep the issue log open until every item below has been checked at least once.
This page covers operations. For the search and traffic side of the first month, see the 30-day table in our guide to migrating to Shopify, and for post-launch checks specific to a WooCommerce move, see the WooCommerce to Shopify migration checklist.
| Area | What to reconcile | Owner |
|---|---|---|
| Payouts | Payment provider payouts against orders, refunds and fees for each payout period; any gap traced to specific orders | Finance |
| First returns and refunds | The first returns of each type (refund, exchange, store credit) processed end to end; refund amounts, tax and restocking correct; returned stock back in the right place | Customer service, operations |
| Inventory drift | Stock levels on the new platform compared with the warehouse, 3PL or ERP; variances investigated, not just corrected | Operations |
| Subscription renewals | The first renewal for migrated subscribers charges the right amount on the right date, and failed renewals are retried and reported | Developer, customer service |
| Integrations | Error logs, retry queues and duplicate records in ERP, CRM, email and marketplaces | Developer |
Worth noting
Moving to Shopify? The Shopify-specific test mechanics (the Test payment gateway, test mode and redirect limits) are covered in Step 7 of the Shopify migration guide, so they aren't repeated here.
Worked Example
An illustrative scenario, not a client case: during testing, standard orders flow correctly to the ERP, but partial refunds create mismatched totals because tax is recalculated differently. Because the test plan included partial refunds and ERP reconciliation, the issue is fixed before launch instead of appearing in the first month's accounts.
Common Mistakes
- Testing only the happy path
- No live payment test before launch
- Integrations tested with standard orders only
- Redirects spot-checked instead of fully tested
- Analytics changes not compared with the old setup
- No agreed go-live criteria
Ready to test your migration properly?
Talk to ZSpace Labs about migration QA, Shopify launch testing and conversion checks after launch.
Conclusion
Migration testing protects revenue by prioritizing checkout and order flow, validating data and accounts, testing integrations with edge cases, checking every redirect and SEO element, and confirming analytics, performance and accessibility, with agreed go-live criteria. Related: parallel runs and migration strategy.
Common questions.
Checkout and payments, shipping and tax, discounts and gift cards, customer accounts, product and order data, integrations, redirects and SEO elements, analytics and tracking, performance, accessibility, mobile and security basics.
The flows that make money and the integrations that fulfil orders: checkout with every payment method, shipping and tax calculation, and order flow to fulfilment and finance.
Both, at different stages. Use your platform's test payment gateway or your payment provider's test mode for most testing; these simulate approvals, declines and failures without moving money. Switch test mode off before launch, because some platforms block live orders while it is on. Then place a small number of real orders with each live payment method and refund them, to confirm live configuration. Your payment processor may still charge fees on these orders, even after a refund.
Compare counts and totals with the old system, check samples and edge cases field by field, and test journeys such as a migrated customer viewing order history.
Automatically: request every old URL and check it returns one permanent redirect to the expected destination, which returns 200.
People who use the store daily: merchandisers, customer service, operations and finance, following scripted scenarios for their work.
Enough to run all test cycles, fix issues and retest. Plan several cycles, including at least two full data migration rehearsals.
Yes. Check page speed on key templates on mobile and, for high-traffic stores, load test checkout and key journeys.
Test key journeys with keyboard and screen reader and run automated checks on templates, since new themes and apps can introduce barriers.
At minimum check access, apps, scripts and settings. Custom code and integrations may warrant professional security testing before launch.