Recurly often anchors recurring billing and subscription account management. Azotte adds an subscription model for teams operating across storefronts, regions, payment providers, and entitlement structures.
Recurly migrations should focus on preserving subscriber state while moving policy decisions into Azotte.
Each row shows who manages what, how Azotte changes it, and what happens when you move.
| Aspect | Current way | Azotte way | What changes |
|---|---|---|---|
| Subscription control | Recurring billing state is the main operational reference. | Lifecycle state is a shared management record across channels. | Map active, trial, pause, cancellation, failed, and recovery states. |
| Entitlement architecture | Access often reads billing or plan status from external services. | Access is defined by entitlement rules independent of billing source. | Translate plans and account state into access relationships. |
| Storefront expansion | New storefronts may require added integration and process work. | Storefront behavior is governed as part of the same subscription model. | Select the first storefront or cohort for controlled cutover. |
| Payment control | Provider behavior is typically linked to recurring billing operations. | Routing, retry, and recovery can vary by PSP, region, and channel. | Preserve payment references and define future provider routing policy. |
| Migration complexity | Accounts, subscriptions, invoices, coupons, and recovery data need reconciliation. | Imported records become the continuity base for future policy decisions. | Validate renewal timing, failed-payment state, and customer access. |
The comparison is most useful when framed around subscription control: which system decides what the subscriber can do next.
