The finance question on migration is straightforward: what does this do to the P&L and the cash-flow statement, on what timeline?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.
P&L impact
Migration recovers margin permanently for as long as each migrated subscriber stays subscribed. Net recovery per migrated dollar:| Source | Year 1 | Year 2+ |
|---|---|---|
| iOS Year 1 subscriber (30%) | 22 cents | 25 cents |
| iOS Year 2+ / Google Play (15%) | 7 cents | 10 cents |
- Year-one recovery: ~$385K
- Steady-state ongoing recovery: ~$470K/year
- 3-year cumulative: ~$1.3M
Cash-flow impact
Separate from the P&L: the one-time cash-flow injection during the migration window. The public audit models a 45-day timing difference between app-store settlement and web-billing settlement. As subscribers migrate, their renewal cycle shifts from store settlement to the faster web-billing cadence. Trailing store settlements still arrive on schedule; new web settlements arrive faster. The two cash flows overlap during the migration window. Net effect: ~45 days of net revenue (your share, after store fees) from migrated subscribers, pulled forward as a one-time working-capital release. Magnitude: at a 22% blended store-fee assumption, roughly 5.3% of total ARR at baseline migration (12.3% × 0.78 × 55%); your audit reports the specific figure using your actual blended rate. A 264K cash injection. A 528K. Apps on lower blended fees (Google-heavier) see proportionally more cash because Apple’s net is smaller for them. This does not change the P&L. The dollars eventually arrive on either schedule — you just have them earlier. Cash-flow detail →Payback
The pilot fee starts from $10K (scaling with the migration project), credited against migration, and refundable before pilot kickoff if internal alignment changes. Once kickoff begins, the pilot fee pays for pilot work. The full migration fee is scoped separately and typically lands below one month of the app-store fees you’re already paying. For most qualified apps, payback on the full migration cost lands inside the first few renewal cycles, helped by the cash-flow injection. The recurring margin lift is the ongoing P&L impact on top.What to model before pilot reservation
A finance reviewer evaluating the migration should model:- Year-one net recovery at conservative / baseline / optimistic migration rates
- Year-one cash-flow injection as a separate line — it’s working capital, not P&L
- Steady-state Year 2+ recovery, multiplied by retention curves (your existing churn rate is the right input)
- Migration cost vs the per-month app-store fee leakage — full migration is typically scoped below one month of current app-store fees
What’s not in the migration cost
- Subscriber retention impact. This is a real risk; the holdout measurement is how it gets quantified, and pilot gating is how it stays bounded. The framework treats this as the dominant downside, not a surprise line item.
- Engineering cost on your side. Light — 2–4 hours integration + 1–2 hours/week during active migration. Not a meaningful drag.
- Customer support spike. Possible during waves; the framework supports this with documentation + the wave dashboard, but a temporary support uplift is realistic to budget for.
The ratio
For most apps in the target segment, the math is decisively favorable:- Year-one recovery vs migration cost: typically 5–15× cost
- Cash-flow injection vs migration cost: typically 3–8× cost on its own
- Steady-state recovery: pure upside in Year 2+