Skip to main content
Recurr starts with migration because migration creates the web book Oikos can operate. The operating sequence is:
1

Audit

Size the opportunity, current store exposure, eligible cohorts, and first-pass economics.
2

Pilot

Run a controlled slice of the migration to validate uptake, retention, support load, and migration economics.
3

Migrate

Expand cohort by cohort when the agreed signals hold, until the waves have reached your whole eligible book. The customer approves the guardrails; Recurr operates the workflow.
4

Compound

Oikos runs the connected web book and its lifecycle motions, while migration keeps reaching each new store cohort as it matures.
The fourth stage is not a finish line. Your eligible book refills as new store cohorts arrive, so migration keeps running at the same 5% alongside everything Oikos does.

​
Audit

The audit estimates the size of the recoverable opportunity and gives the buyer a way to decide whether the program is worth exploring. The audit is not the final model. It is the starting point. The Migration Hub refines the view with subscriber base shape, integration path, cohort selection, approvals, and commercial terms.

​
Pilot

The pilot is designed around your subscriber base, billing and data setup, and the first cohorts needed to validate uptake, retention, and migration economics. When the program continues, the pilot fee is credited in full against migration fees.

​
Migration

Migration runs cohort by cohort. Each wave uses approved messaging, offer framing, timing, and guardrails. Recurr reports the results and only scales when the data supports it. The agreed timeline describes how long it takes to reach your whole eligible book, not how long until migration is over. New store cohorts keep arriving behind the ones already moved, and ascension keeps migrating them as they mature, at the same 5%.

​
Ongoing growth

Oikos turns on as the web book comes online. It runs subscriber surfaces, lifecycle motions, cohort reporting, and Kairos decisioning across the connected web book. Migration does not hand off to Oikos and stop. The two run in parallel from that point: Oikos grows every subscriber on the web book, and migration keeps adding to it.