Is migrating subscribers off the App Store actually allowed?
Is migrating subscribers off the App Store actually allowed?
Yes, with specifics. Recurr operates outside the app binary: email and owned channels reach the subscriber, checkout happens on web, and the app continues granting access through the existing entitlement system. See Apple compliance and Google Play compliance for the policy posture.
Will this trigger an Apple or Google response?
Will this trigger an Apple or Google response?
The migration operates outside the app binary by design — no SDK, no app release, no in-app links to web pricing, no in-app migration messaging. Apple’s and Google’s review processes are bounded to in-app activity; the rails Recurr operates on (email from your domain, web checkout on your server, subscriber portal) sit outside that perimeter. Your app continues to comply with in-app guidelines exactly as it did before.
What about churn? Won't subscribers cancel during the migration?
What about churn? Won't subscribers cancel during the migration?
The pilot is built to answer that with data. Each pilot wave runs against a matched store-billing holdout - same tenure, plan, engagement, and geo - so churn impact is measurable. The migration does not scale until retention and payback clear the agreed gates.
What does my engineering team have to do?
What does my engineering team have to do?
For apps with a centralized entitlement source, initial integration is typically 2-4 engineering hours: entitlement access, Stripe Connect, DNS for branded checkout, and webhook subscriptions. Ongoing involvement is usually 1-2 hours per week during active migration. No SDK, no app release, no migration build on your roadmap.
What if we are StoreKit-only?
What if we are StoreKit-only?
StoreKit-only apps with no centralized entitlement source are not a current fit. Recurr can integrate with RevenueCat, Adapty, or a custom backend, but it does not currently add a new mobile SDK or replace a StoreKit-only entitlement architecture.
Do I have to migrate everyone?
Do I have to migrate everyone?
No. Migration runs in waves on selected cohorts. Subscribers who do not respond stay on app-store billing — nothing changes for them — and are re-approached in later quarterly waves. The framework’s job is to move the cohorts where the economics, retention signal, and user experience justify scaling.
What happens to my Apple receipts / RevenueCat / current setup?
What happens to my Apple receipts / RevenueCat / current setup?
Your current entitlement system continues to work. Recurr writes web subscription state into the same system alongside existing Apple and Google receipts. The app’s runtime entitlement check is unchanged.
Are lifecycle motions included?
Are lifecycle motions included?
Migration creates the rails for pricing control, cleaner attribution, payment recovery, and lifecycle work. Recurr’s current offer focuses on migration, billing, entitlement sync, cohort operations, and reporting. Broader self-serve lifecycle modules are roadmap and partner-scoped.
What if my subscribers use Apple Sign In with private relay?
What if my subscribers use Apple Sign In with private relay?
Apple private relay can work when the relay address is deliverable and stable for the subscriber. Identity continuity is checked during the Migration Review because each app’s account and entitlement setup can differ.
Can I leave Recurr later?
Can I leave Recurr later?
Yes. The Stripe Connect account is in your company’s name, web subscriptions settle to your Stripe account, and subscriber data is exportable. The annual commitment runs to its term; after that, you can exit and continue with your own Stripe and entitlement setup.
Why does the all-in web-billing cost step down after the migration year?
Why does the all-in web-billing cost step down after the migration year?
Two pieces. The Recurr platform fee is flat 3.5% from day one — no step-up, no tier. The change is the 2.5% migration performance fee, which applies per subscriber migrated and lands across the first 12 months of their web billing. After that, you’re paying the 3.5% platform fee + Stripe processing only, with no migration performance fee on top. The performance fee reflects the work density during migration: cohort design, wave operations, observability, and gating decisions are heaviest while subscribers are actively migrating.
Who should be on the Migration Review call?
Who should be on the Migration Review call?
Founder plus finance lead is ideal. Tech can join if there are integration questions, but the call works best with the people who understand the economics and can decide whether to pursue a pilot.
What if my Migration Review doesn't go well?
What if my Migration Review doesn't go well?
Then no pilot slot is offered. The Migration Review is a real qualifier: fit profile, timing, technical readiness, and migration risk all matter. If the path is not credible, the process stops before any paid commitment.
How does Recurr's pricing compare to alternatives?
How does Recurr's pricing compare to alternatives?
Recurr is a managed migration platform, not a raw billing tool or a strategy-only consultant. The closest comparison depends on what you are optimizing for: speed of migration, low engineering lift, cohort analysis, retention safety, or long-term control. The Migration Review is the right place to compare alternatives against your app’s constraints.
Questions not on this list? Reply to any Recurr email or send to matt@recurr.dev. Common questions land here as patterns emerge.