Chapter 6
Run a staged cutover
Part of How to Migrate From Stan Store, Linktree or Gumroad to Tapmy Without Losing Customers.
Finish this chapter with a staged cutover and communication plan you can use immediately to run a staged cutover, while avoiding switching the public link before customer access and tracking are verified.
What you’ll get
- A completed staged cutover and communication plan, not a list of abstract ideas.
- One explicit decision rule for run a staged cutover.
- A 45-minute execution sequence you can repeat yourself or hand to a teammate.
- A quality gate that tells you whether to move forward, run one small test, or revise the input.
Use this chapter as a working session
Open the document, spreadsheet, or Tapmy workspace where this decision will live. Replace sample language with the exact offer, buyer, channel, price, and evidence you have today. If a fact is missing, label it as an assumption and assign the smallest test that can resolve it.
| Time | Work | Concrete output |
|---|---|---|
| 0–10 min | Collect buyer words, traffic data, sales conversations, support questions, and current page copy. | A short evidence list with source and date. |
| 10–20 min | Make the single decision this chapter is designed to resolve. | A one-sentence decision and reason. |
| 20–35 min | Build the staged cutover and communication plan with real names, numbers, links, and owners. | A usable operating asset. |
| 35–45 min | Review it from the buyer’s point of view and run the quality gate. | A keep, test, or revise decision. |
Work through the chapter
Do not switch every channel and close the source on the same day.
Prepare migration messages
Create separate communication for:
- prospective visitors: “Our store has moved; use this link”;
- existing one-time buyers: explain whether access changes and how to get help;
- active subscribers/members: explain billing/access changes only after the operational plan is confirmed;
- partners/affiliates: provide new links, attribution instructions, and effective date;
- support: give the team a response script and escalation path.
Do not frame the move as an emergency unless it is one. State what changes, what stays the same, when, and what action is required.
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The staged cutover and communication plan is ready to use. | Put it into the Tapmy journey and measure the next observable behavior. |
| One important input is assumed | The direction is testable, not yet proven. | Run the smallest test that can confirm or reject that assumption. |
| The asset serves several audiences, offers, or goals | The scope is too broad. | Narrow to one buyer, one job, one offer, and one reporting window. |
| The result depends on a claim you cannot show or deliver | Trust and delivery risk are higher than the upside. | Rewrite the promise around a supportable outcome. |
Quality standard
- The staged cutover and communication plan names one buyer and one job.
- Every number has a timeframe, currency, or denominator where needed.
- Every link and handoff has an owner.
- The next action is visible without rereading the chapter.
- The decision can be measured through customer behavior.
- No claim is stronger than the evidence.
