Skip to main content
Store-to-web subscriber migration moves an existing Apple or Google Play subscriber onto a web subscription for the same app. The subscriber keeps using the app. What changes is the commercial rail: future renewals happen through your web billing setup instead of the app store.

​
What changes

​
What stays the same

The subscriber should experience continuity:
  • Same app
  • Same account where the app already has one
  • Same paid access
  • Same subscription value
  • Same app-store option for subscribers who do not move
Recurr does not require an app release for the migration path. The program operates through owned channels, branded web surfaces, and integration with the access model you already use.

​
Why migration is run as a program

Migration touches finance, product, lifecycle, support, and policy posture at the same time. That is why Nostos runs as a managed program rather than a one-off campaign. The program starts with a pilot slice, measures uptake, support signal, billing health, and churn risk, then expands cohort by cohort when the agreed signals hold. Nostos is not designed as a blanket discount campaign. Recurr’s posture is price parity, with limited-scope offer paths where they help break inertia without training the book to expect a lower web price.

​
Where Oikos fits

Nostos brings the existing book home. Oikos runs the web book from there. That matters because migration is not a one-time event. New store cohorts continue to appear after the first migration, so migration keeps running, at 5%. That continuation is ascension: moving those newer store cohorts onto web billing over time as they mature, on the same terms as the first waves.