Migration cases
Recurr models three migration cases:
These are shares of the eligible book as it stands when the model is built, not shares of a base that closes. The eligible book refills: new store cohorts keep arriving and become eligible as they mature, so later periods carry their own migration volume at the same 5%.
The pilot validates where your real subscriber base sits. Cohorts differ by tenure, plan, renewal timing, geography, engagement, and reachability.
Commercial assumptions
Payment rail assumptions
Stripe is the default rail for most customers. Stripe processing, tax settings, refunds, disputes, and payout timing are governed by the customer’s Stripe setup. Paddle can be considered where merchant-of-record coverage or existing Paddle infrastructure makes it the better rail. Paddle support is scoped as early access.Store fee assumptions
The audit uses your stated or inferred store-fee exposure. Apple and Google rates vary by program, geography, transaction type, and policy changes, so the Migration Hub checks the assumptions before commercial terms are finalized.What gets refined later
The Migration Hub refines:- Eligible subscriber base
- Current store-fee blend
- Existing web billing footprint
- Payment rail choice
- Integration path
- Cohort selection
- Subscriber reachability
- Support and cancellation guidance
- Pilot scope and fee