> ## 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.

# For finance

> The finance lens on migration: net-of-fees math, cash-flow timing, payback, and what to model before pilot reservation.

The finance question on migration is straightforward: **what does this do to the P\&L and the cash-flow statement, on what timeline?**

## P\&L impact

Migration recovers margin permanently for as long as each migrated subscriber stays subscribed.

<Note>
  **Worked-example assumptions.** US-based app on Stripe (2.9% + $0.30/txn). Average transaction $17 (50/50 mix of $10 monthly and $100 annual subs) — the per-transaction flat fee adds \~1.76 points to the Stripe percentage basis at this ARPU, so all-in Stripe is \~4.66%. Recurr fees: 3.5% platform + 2.5% migration performance (Y1 only). Your live [Migration Audit](https://recurr.dev/audit) resolves your country-specific Stripe rate and uses your actual ARPU.
</Note>

**Net recovery per migrated dollar:**

| Source                          | Year 1     | Year 2+    |
| ------------------------------- | ---------- | ---------- |
| iOS Year 1 subscriber (30%)     | \~19 cents | \~22 cents |
| iOS Year 2+ / Google Play (15%) | \~4 cents  | \~7 cents  |

These are net of Recurr's fees (3.5% platform fee + 2.5% migration performance fee in Year 1) and Stripe processing at the US baseline + \$17 ARPU. EU/UK/AU recover proportionally more on web because Stripe processing there is 1.5–1.7%. Annual-heavy books recover proportionally more because the per-transaction flat fee amortizes across a larger ARPU. The audit puts these per-dollar deltas through your specific blended rate, country-resolved Stripe rate, actual ARPU, baseline 55% migration percentage, and ARR.

A representative US-based app at $5M ARR with a 22% blended rate, $17 ARPU sees:

* **Year-one recovery:** \~\$310K
* **Steady-state ongoing recovery:** \~\$380K/year
* **3-year cumulative:** \~\$1.1M

[See the math →](/opportunity/where-recovery-comes-from)

## Cash-flow impact

Separate from the P\&L: the **one-time cash-flow release** 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 released as a one-time cash-flow 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 $5M ARR app at 22% blended sees ~$264K cash-flow release. A $10M ARR app sees ~$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.

This release is the mechanism behind the self-funding migration: the program fee is covered by the release itself — typically within 2–3 weeks of migration starting — and the invoice is only due once it has been.

[Cash-flow detail →](/opportunity/cash-flow-release)

## Payback

The pilot deposit starts from \$10K (scaling with the Migration Program), refundable before pilot kickoff if internal alignment changes, and credited in full against the migration fee — a commitment device around a reserved implementation window, not a price for an experiment. The full migration fee typically lands at less than one month of the app-store fees you're already paying.

For most qualified apps, the program typically returns from cash flow alone within 2–3 weeks of migration starting. 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 release** 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

The audit PDF includes all of these as a starting point. The Migration Analysis and MSA name specific dollar amounts and timing.

## 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 release vs migration cost: typically 3–8× cost on its own
* Steady-state recovery: pure upside in Year 2+

The Migration Review pressure-tests these on your specifics before pilot reservation.