Access first
Subscribers should not lose app access because they moved billing rails. Before a subscriber is asked to complete the move, Recurr confirms how web subscription state will be recognized by the customer’s existing access model.Cancellation guidance
The app-store subscription is not cancelled automatically by Recurr. Instead, the subscriber receives clear guidance on how to cancel the store subscription after the web subscription path is established. The program monitors for overlap risk and routes support where a subscriber needs help.Campaign coordination
Migration should not run beside siloed campaigns that only see one subscription source. Before the pilot, Recurr maps active lifecycle, paywall, recovery, and winback paths for the target cohorts. Conflicting paths are either paused for the migration cohort or made state-aware so they read the subscriber’s full status across store and web billing. That keeps the migration from being undermined by adjacent automation, for example:- A migrated subscriber being treated as churned because the store subscription ended
- A store-native winback offer firing while the subscriber is moving to web billing
- A CRM, paywall, or recovery flow sending the wrong message because it only reads one billing source
- Support teams seeing conflicting subscription states without a clear source of truth
Cohort gates
Each cohort moves forward only when agreed signals hold:- Uptake
- Retention
- Billing success
- Support load
- Refund and dispute signal
- Access continuity