What to Test After an eCommerce Migration Before Black Friday

Before Black Friday, test whether your migrated data is accurate and whether customers can complete the journeys your campaigns will promote. Start with seasonal landing pages and bestselling SKUs, then check variants, inventory, accounts, discounts, redirects, tax, shipping, payment, tracking, notifications, and fulfillment. Repeat the critical checks after your final data update and on the live domain before sending campaign traffic.

A completed migration is an important milestone. But the first holiday order depends on more than the records arriving. Your new theme must display them correctly, your checkout must apply the intended rules, and the systems behind the store must receive a usable order.

At Next-Cart, we recommend turning that uncertainty into a short list of journeys with clear expected results. You do not need to inspect every page with equal intensity. You do need evidence that the products and customer experiences carrying your seasonal revenue work from beginning to end.

1. Start with the pages and products your campaign depends on

Use your campaign plan to choose the first test set. Include landing pages linked from ads and emails, your bestsellers, promoted variants, gift collections, and any bundle or subscription offer you intend to advertise. Add a few difficult records, such as products with custom fields or customers with extensive order histories.

Prioritizing these journeys helps you find commercially important problems early. It does not replace wider validation of the migration scope. Keep record-count checks, exception reports, and representative sampling across the remaining catalog.

• Open each campaign link on mobile and desktop, including links in a draft email or ad.

• Confirm that the advertised product, price, currency, availability, and offer match the destination.

• Follow collection filters, search results, and calls to action through to the intended product.

• Record the expected outcome, actual outcome, owner, and retest result for each issue.

If your move is still being finalized, our guide to preparing your store for migration explains how to agree the scope and launch requirements before this validation stage.

2. Separate migration results from storefront setup

Data-transfer validation asks whether the agreed records, fields, and relationships reached the target correctly. Storefront validation asks whether the destination’s theme, apps, checkout, and operating rules use those records as intended. A problem can involve either layer or both.

For example, a material field may exist correctly in the target admin but be absent from the product page because the theme has not been configured to show it. Reporting only “the material is missing” makes diagnosis slower. Include where it exists, where it does not appear, and an example SKU.

Use these checks to route an issue; ownership depends on the agreed project scope.

Compare against the supported entities and agreed options for your exact migration path. On a WooCommerce to Shopify migration, for instance, checking transferred products is separate from validating the destination’s payment configuration. Do not assume that a data migration recreates every app or business rule.

3. Validate products, variants, and inventory together

Start in the target admin, then check the storefront. Confirm titles, descriptions, images, prices, category assignments, and required custom fields. For variants, verify the option combination as well as the SKU, barcode, image, and price attached to it.

Imagine a navy jacket in medium. The page may show the right parent product while the selected variant points to the wrong stock record. Add that exact combination to the cart and inspect the resulting order line. This is the sort of relationship check that record totals cannot prove.

Our explanation of data mapping and connected SKUs shows why product, variant, and order relationships need their own validation.

Use the right inventory baseline

Compare quantities against an agreed snapshot or cutoff time. If the source store continued selling after the first migration, a difference may represent later activity rather than a transfer error. Reconcile that activity before approving inventory.

Where the store uses multiple locations or an external inventory system, confirm which system owns stock and which locations can fulfill online orders. Test an in-stock variant, an out-of-stock item, and the intended backorder behavior. Check that a controlled order changes availability as expected.

Avoid blind reruns. Before repeating a migration or using Additional Migration Options, confirm the supported scope, matching behavior, and effect on data already in the target. Agree how new orders and inventory changes will be reconciled.

4. Check returning customers and historical orders

Use authorized test accounts to validate the customer experience. Confirm the intended sign-in or account-activation process, password reset where applicable, saved addresses, and access to the correct order history.

Password portability depends on the source, target, and supported migration method. If existing passwords cannot move, prepare and test the replacement access journey before announcing the new store. A customer record arriving does not, by itself, prove that the customer can sign in.

Open representative historical orders and review their customer association, purchased items, quantities, discounts, currency, shipping, tax, and totals. An old order should remain understandable even if the product has since been discontinued. Confirm that customer accounts expose only the history they should.

If historical orders trigger email or fulfillment automations in the target, resolve that behavior before any later import. Customers should not receive a new shipment notification merely because an old order was migrated.

5. Prove the seasonal offer at checkout

Test the actual promotion you plan to run, including eligibility, exclusions, minimum spend, usage limits, start and end times, and interaction with other discounts. Review the store’s timezone rather than assuming the offer will begin when your marketing team expects.

Then combine the promotion with representative addresses, delivery methods, customer types, and payment methods. Have the person responsible for tax configuration provide expected results for your test scenarios; do not infer the right tax outcome from the previous store’s display alone.

An example purchase to trace

Consider an illustrative campaign offering 20% off an eligible $80 jacket. The expected merchandise subtotal for one jacket is $64 before shipping and tax. Test the promoted variant, an excluded product, and a cart that does not qualify. Then confirm the correct shipping and tax results for each approved address scenario.

• Complete a guest checkout and a returning-customer checkout on mobile.
• Check shipping availability, free-shipping thresholds, and unsupported delivery destinations.
• Test a successful payment, an appropriate failure scenario, and the customer’s retry path.
• Verify that the confirmation page, order record, and payment record agree.

Use payment test modes first and prevent tests from triggering real dispatches or customer emails. Before campaign approval, arrange any necessary controlled live payment check with your team, then reconcile or refund it according to your process. Sandbox success does not prove that live credentials and payment settings are correct.

Functional testing also does not establish capacity under a traffic spike. Use our holiday traffic stress-test guide for load, monitoring, and recovery checks alongside this post-migration checklist.

6. Follow old URLs to the correct new pages

Start with URLs that already attract shoppers: top organic landing pages, bestseller URLs, category pages, and links used in past emails or active ads. For changed URLs, confirm that the old address reaches the closest relevant new destination through the intended permanent redirect.

Check for redirect loops, unnecessary chains, broken destinations, and unrelated pages. Sending every retired product URL to the homepage can leave shoppers without the item they came for. Google’s site-move guidance recommends relevant URL mappings and direct redirects to the final destination.

Also review canonical URLs, internal links, and the sitemap. Confirm that pages intended for public search are not still blocked by development settings such as noindex directives. Keep private account and checkout pages governed by their intended indexing rules.

Test campaign links with tracking parameters, too. A redirect that reaches the right product but drops campaign information can make results harder to interpret. Passing these checks reduces avoidable issues; it does not guarantee unchanged search rankings after a platform move.

7. Confirm tracking with a real test journey

A tracking script appearing in the page source is only a starting point. Follow the selected product through product view, add to cart, checkout, and purchase, then inspect the events in the relevant testing tools.

For GA4, Google’s ecommerce validation guidance explains how to inspect events in DebugView. Verify the purchase’s transaction identifier, currency, item identifiers, quantities, and value according to your implementation. Reconcile the test transaction with the store order rather than comparing unrelated daily totals.

Check for duplicate purchase events, especially if both an app and a tag manager send them. Confirm the correct production property and advertising destinations, and test consent behavior without bypassing the customer’s choice. Use synthetic customer data and avoid sending personal information in analytics fields.

Our guide to safeguarding data tracking covers the continuity checks that are easy to miss when the storefront itself looks finished.

8. Trace notifications and integrations after the order

A successful checkout still needs a successful handoff. Check the customer confirmation, internal order alert, warehouse or fulfillment record, inventory update, and relevant CRM or accounting entry. Verify the recipient, content, timing, and order reference.

Inspect integration logs or queues where available. If processing is delayed, determine whether the delay is expected and who will respond when it exceeds the agreed limit. Test how failed work is retried and how duplicate processing is prevented.

Email templates deserve a separate review after a move. Links should point to the live domain, branding should match the new store, and customer account links should open the correct destination. Confirm that a historical import does not start an unwanted automation.

Document evidence using a shared test reference across the store, payment provider, and downstream system. This gives support and operations a way to investigate the same transaction without guessing which record another team means.

9. Sign off the first Black Friday campaign

Run the final checks after the last approved data update and repeat the critical buying journey on the live domain. Confirm live payment settings, emails, redirects, integrations, and tracking rather than relying only on results from staging.

Use this checklist for campaign approval:

• Seasonal landing pages and promoted SKUs lead to the correct purchasable items.
• Product relationships, customer history, and inventory pass the agreed data checks.
• Customers can use the intended account-access journey.
• Discount, tax, shipping, payment, and retry scenarios match their expected results.
• Priority legacy URLs and campaign links reach the right live destinations.
• Tracking, notifications, and downstream order processing have been verified.
• Critical defects are resolved and retested; remaining issues have named owners and approved workarounds.
• Marketing, operations, and the technical owner agree who can pause a campaign and how incidents will be handled.
• Keep a lightweight test log: scenario, environment, expected result, evidence, owner, and status. Do not mark a failed check as passed because a fix has been deployed. Retest the affected journey, including any dependent steps.

Hold the affected campaign if customers cannot pay, orders reach the wrong account, stock is unreliable, or fulfillment receives incorrect items. A high overall pass rate should not hide a critical failure.

Your first seasonal campaign should begin with a clear view of what has been tested and who owns what remains. If a discrepancy involves migrated records, give the migration team example IDs, the source value, the target result, and the expected behavior.

For help reviewing the migration scope and available support, compare Next-Cart’s migration services. Agree which validation tasks are included and which belong to your storefront or integration team. You can also explore our Migration Guides for the next steps in preparing and checking your move.