Skip to main content

Documentation Index

Fetch the complete documentation index at: https://recurr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Migration runs as a four-phase engagement. Each phase has clear gates and a defined output before the next phase starts.

​
Phase 1 — Audit

Week 1. A 60-second self-serve calculator quantifies fee exposure, recovery cases, and cash-flow upside on your numbers. You receive a PDF brief by email. Output: dollar-level visibility on year-one recovery, steady-state recovery, and the one-time cash-flow injection from the store-to-Stripe settlement window. Run the audit →

​
Phase 2 — Migration Review

~30 minutes, founder-led. Pressure-test the audit economics on your real variables (IAP share, store mix, plan mix). Confirm a safe pilot path exists. Output: a clear go / no-go on the migration path, plus a Migration Analysis if the call confirms strong fit. Book the Migration Review →

​
Phase 3 — Pilot

Weeks 2–3. A controlled wave on a small, low-risk cohort — matched against an IAP holdout to measure and contain churn impact. The pilot fee (from $10K, scaled to your migration project) is credited against migration and refundable before kickoff if internal alignment changes. Output: real cohort data on migration rate, retention, and payback. Decision-grade input for the full migration scope.

​
Phase 4 — Full migration

Weeks 4–12. Wave-by-wave migration across your subscriber base. Each wave is gated on retention and payback signals from the prior wave. Pause or roll back at any wave if signals diverge from pilot benchmarks. Output: a scaled migration path across proven cohorts. Recurring margin lift is permanent for as long as each migrated subscriber remains active.

​
Three factors of success

Migration is a multi-touch campaign run on a live subscriber base — emails, web checkouts, billing transitions, support flows. Like any campaign at that scale it carries risks, but the framework keeps those in check by sequencing for safety in three places:
  • Wave-based pilots with matched IAP holdout. Each migration runs in waves. The pilot wave targets a small, low-risk cohort. A matched IAP holdout — same tenure, plan tier, and engagement, no migration offer — runs alongside as the comparison baseline.
  • Multi-axis cohort selection. Each cohort is selected on five dimensions — tenure, geo, engagement, renewal window, and plan. Pilot waves test these axes individually so migration cohorts can sequence based on what cleared.
  • Store-policy compliance. Migration runs entirely outside the app: subscribers are reached via email or owned channels, billing settles through your branded web checkout. The app binary stays untouched.