Skip to main content
Migration should reduce dependency on app-store billing without creating a new dependency that is just as hard to unwind.

​
What is portable

  • Payment rail account
  • Subscription records in the rail
  • Subscriber identifiers and state exports
  • Event history and reporting exports where configured
  • Access model in the customer’s stack
  • Domain and sender assets owned by the customer

​
What is not reversible

Once a subscriber is successfully moved to web billing, the commercial relationship has changed. You can stop using Recurr, but you would not usually move that subscriber back to app-store billing unless there is a specific business reason.

​
If Recurr is removed

The customer should still have:
  • Payment rail access
  • Billing records
  • Subscriber data
  • Access model control
  • Exported reporting data
What stops is the Recurr-operated layer: Kairos decisioning, Oikos motions, Recurr subscriber surfaces, migration operations, and cohort reporting.

​
Diligence questions

Ask:
  • Where does billing data live?
  • Who owns the payment account?
  • Where does access state live?
  • What exports are available?
  • What happens to domains and sender identity?
  • What does the agreement say about termination support?