---
title: Test before switching traffic
description: Test your Tapmy store signed out before you change profile links, domains, ads or email links, so a migration does not lose sales or access.
lead:
  - "Before you move traffic to Tapmy, run the full buyer journey signed out: offer page, payment, delivery, access, emails, analytics and support. A preview alone proves none of it."
tags:
  - migration
source: docs/tapmy-wiki/pages/test-before-switching-traffic--6ede7d56.md
---

## What should I check before moving traffic? {#what-to-map}

| Area | What to decide or check |
|---|---|
| Discovery | Public URL, mobile layout, page speed, offer visibility, links |
| Purchase | Price, currency, buyer fields, payment, authentication, error recovery |
| Fulfillment | Receipt, download, course or Community access, booking, service intake |
| Operations | Order record, customer identity, Stripe status, creator notification |
| Measurement | Visit, checkout, order, attribution, refund where safe to test |
| Recovery | Support contact, rollback link, owner, evidence packet |

## How do I test before switching traffic? {#migration-steps}

1. Write a test plan: expected results, who tests, which device and browser, account state, and where you save evidence.
2. Test signed out on a phone first, then on desktop and one more browser.
3. Run a free flow, and a controlled paid flow where it makes sense, using a safe test or an approved low-value live purchase. Do not assume a refund will be possible.
4. Check the receipt and access under the exact checkout email. Try the wrong-email and expired-session cases without real customer data.
5. Compare the buyer's result with your records: order, customer, access, booking and Stripe status.
6. Check analytics and attribution with the right time zone and live or test context. Allow only the documented delay.
7. Log every issue, fix it, then rerun the whole critical path. Never switch on a partial retest.
8. Approve the cutover only when someone owns the rollback and the monitoring window is set.

## What does a passing test look like? {#what-success-looks-like}

The critical journey works on mobile and desktop, money and access records match, emails arrive, analytics make sense, and a rollback is ready.

## What are the risks? {#risks-and-limits}

- Never use real customer data or a card you are not authorized to use.
- A good preview does not prove payment, email or access.
- One working transaction does not cover every country, currency, browser or payment method.
- Do not change DNS, cancel the old platform and launch an ad campaign all at once.

## What next? {#next-steps}

Move one traffic source, watch the results, then add more. Keep the test record as your baseline for later changes. See [Test the complete buyer journey](/help/test-the-complete-buyer-journey) and [Migration master checklist](/help/migration-master-checklist).