Skip to main content
Migration is a managed subscriber campaign. A subscriber may move on the first touch, after follow-up, after support guidance, or not at all. Recurr tracks the state of each subscriber so the campaign can continue without treating every non-conversion as a failure.
1

Cohort enrolled

Kairos and the migration framework select eligible subscribers through approved cohort rules.
2

First branded touch sent

The subscriber receives a branded email or owned-channel message explaining the move and the path to web billing.
3

State is tracked

Recurr tracks whether the subscriber opens, clicks, starts checkout, completes web billing, needs support, or remains on store billing.
4

Follow-up path runs

Follow-up timing, message framing, and offer path can change based on subscriber and cohort signals.
5

Web checkout opens

Checkout loads with account context, offer framing, and the relevant payment rail.
6

Web subscription starts

The subscriber completes web billing through Stripe, or through a scoped Paddle path where applicable.
7

Access and store guidance continue

The customer’s access model recognizes the web subscription, and Recurr provides cancellation guidance where the store subscription still needs to be ended.

​
What the campaign watches

The migration flow is stateful. Recurr watches:
  • Subscriber readiness and tenure
  • Message engagement
  • Checkout starts and completions
  • Support questions
  • Store-cancellation progress where needed
  • Billing health after the move
  • Churn signal against comparison context
That lets the program keep working the cohort without sending the same message repeatedly or scaling before the signals hold.

​
What counts commercially

A subscriber counts as successfully migrated when they are live and renewing on web billing. The migration fee is earned as each subscriber successfully moves, and billed monthly on what that subscriber pays across their first 12 months on web billing.