Migration Method
Move your existing book to web
A managed, cohort-by-cohort migration from app-store billing to direct web billing. Recurr runs the program, measures uptake and retention, and scales each wave only when the signals hold.
Sized in the audit across conservative, base, and upside cases.
Framework
The controlled migration framework
Four gated phases move the book from app-store billing to web billing without forcing a single big-bang cutover. Each phase has a clear decision point before the next one scales.
Audit
Week 1
Size the opportunity, segment the book, and choose the first cohorts.
Pilot
Weeks 2–3
Run a real migration slice to validate uptake, retention, billing success, and support load.
Decision point — proceed, adjust, or stop
Migrate
Weeks 4–12
Expand cohort by cohort as the agreed signals hold, until the base you have today is covered.
Compound
Ongoing
Keep moving new store cohorts as they mature, while web-first acquisition grows the direct book.
Your team approves cohorts, messaging, and guardrails. Recurr runs the workflow, reporting, and subscriber follow-up.
Subscriber Experience
What subscribers see
Migration only works if the subscriber experience is clear, branded, and low-friction. Recurr handles the messaging, checkout path, cancellation guidance, and follow-up so the move feels like part of your product.
Built to reduce friction
Subscribers are not dropped into a generic payment flow. The migration path carries your brand, explains the reason to move, and keeps the next action obvious at each step.
Recurr tracks completion state, sends reminders, and flags subscribers who need follow-up.
Migration email
Receives a branded, personalised offer to move to web billing.
Web checkout
Completes checkout on your branded web surface, with wallet-first payment where available.
Store cancellation guidance
Gets clear instructions and follow-up to cancel the app-store subscription after web billing starts.
App access continues
Access stays uninterrupted while billing moves onto your direct rail.
Safeguards
Retention is the gate
Migration only scales when the signals hold. Each wave is measured against the store-billing baseline, with agreed gates for uptake, retention, billing success, and support load.
Prevents false confidence from raw migration rates by reading uptake and retention against subscribers who stay on store billing.
Keeps finance, product, and support aligned before scale, with thresholds for uptake, renewal, payment success, and support load.
Limits downside if a cohort reacts badly. The program can pause, adjust the offer or cadence, and protect the rest of the book.
Lets the program expand from pilot slices to broader cohorts only where the data supports it.
Store Policies
Built outside the app
Nostos runs outside your app binary. Subscribers are contacted off-app, move through branded web checkout, and keep app access through your existing entitlement system. No in-app purchase link, no app-store payment flow, no external-purchase entitlement required.
Apple’s Guideline 3.1.3 explicitly permits out-of-app email about web pricing — Apple confirmed exactly this in its 2021 developer settlement, with no commission on purchases made outside the app. 3.1.3(b) extends it to multiplatform services: signed-in users may access content acquired elsewhere. Nostos uses that off-app path, without changing the app binary.
Google Play policies allow consumption-only apps to support access to purchases made outside the app. Nostos keeps the purchase path on web and uses your existing entitlement setup to preserve app access.
Because the migration path runs outside the app experience, store technology fees tied to in-app external-purchase flows are not part of the model.
Billing Rail
Your Stripe rail, operated by Recurr
Nostos moves subscribers onto direct web billing in your own Stripe account. Payments settle to you. Recurr operates the migration, subscriber surfaces, lifecycle follow-up, and reporting on top.
Your own Stripe account
If you already have Stripe, we connect to it. If not, setup is part of onboarding. The customer relationship and billing rail sit with you.
Direct settlement
Web payments settle through Stripe on your payout schedule, instead of waiting on app-store payout windows.
Subscription billing
Plans, renewals, invoices, payment methods, and failed-payment recovery run through the connected rail.
App access continuity
Your existing RevenueCat or entitlement setup keeps access aligned as subscribers move from store billing to web billing.
Need the technical shape?
Read the implementation docs for the migration flow, billing rail, and subscriber surfaces.
See what it recovers on your book
You’ve seen how the migration runs. The audit maps it to your book — your blended store tax, the margin you’d reclaim, and the first cohorts worth moving. A minute, on your numbers.