
Chapter 2
Back up data and define customer obligations
Part of How to Migrate From Stan Store, Linktree or Gumroad to Tapmy Without Losing Customers.
Finish this chapter with a backup customer-obligation and entitlement plan you can use immediately to back up data and define customer obligations, while avoiding switching the public link before customer access and tracking are verified.
What you’ll get
- A completed backup customer-obligation and entitlement plan, not a list of abstract ideas.
- One explicit decision rule for back up data and define customer obligations.
- 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 backup customer-obligation and entitlement 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. |
Export what the source platform currently provides
Use the platform’s current official documentation and your account plan. As of this guide’s review date, official help pages describe CSV exports for certain Stan Store income/customer fields, Linktree contacts or eligible Insights data, and Gumroad sales or subscriber records. Availability and included fields can differ by product, plan, date range, and later product changes.
Save exports in a restricted location, record the export date/time and filters, and avoid emailing unprotected customer files. Keep only the data you are entitled and required to retain.
Separate four customer groups
- Past one-time buyers who need continued access or support under the original purchase.
- Active subscribers/members with recurring billing and ongoing service.
- Leads/subscribers with a valid communication status and source.
- Contacts without marketing permission who must not be silently added to promotional messaging.
Migration does not erase refunds, access commitments, licenses, subscription obligations, privacy choices, or support duties. Determine what applies to your business and customers before changing access or billing.
Build an entitlement plan
For every product, answer:
- Where will an existing buyer access what they already purchased?
- Will access remain on the source, move by a supported method, or be provided through a controlled manual path?
- How will identity be verified?
- What happens to updates previously promised?
- Who handles refunds, disputes, or failed renewals during overlap?
- How will duplicate billing be prevented?
Do not cancel or recreate recurring subscriptions casually. Confirm supported transfer options and obtain any required customer action or consent.
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The backup customer-obligation and entitlement 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 backup customer-obligation and entitlement 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.






