Plan migration
DEFINITION
Plan migration is the process of moving existing subscribers from one pricing plan to another while keeping their subscriptions active, typically when a business renames, reprices, restructures, or retires a plan. It requires deciding how each subscriber moves, when, and how any mid-cycle price difference is handled.
TABLE OF CONTENTS
RELATED TERMS
Plan migration is the process of moving existing subscribers from one pricing plan to another while keeping their subscriptions active. It usually happens when a business renames, reprices, restructures, or retires a plan and needs current customers to land on the new version without a break in service.
A migration can be as simple as shifting everyone on an old plan to its direct replacement, or as involved as mapping several legacy plans onto a new lineup with different features, prices, and billing periods. The work spans how and when each subscriber moves, what they pay after the change, how any mid-cycle difference is handled, and what they are told beforehand. A subscription platform such as Recurly can reassign subscriptions to a new plan and apply the timing and proration rules a business chooses. In Recurly, this is done through the Change Subscription feature, available in the admin UI (one subscription at a time) or through the API. Recurly has no native bulk-migration tool, so migrating many subscribers at once means scripting repeated API calls. Timing can be set to immediate, the subscriber's next bill date, or term renewal, and for immediate changes you choose whether the resulting credits and charges are prorated, full, or skipped.
Why plan migration matters for subscription businesses
Pricing and packaging change over time, but the subscribers already on older plans do not move on their own. Without a deliberate migration, a business can end up maintaining many legacy plans at once, each with its own price and feature set, which makes billing, support, and reporting harder to run. Plan migration matters because it:
Consolidates customers onto a current, supported set of plans instead of a growing tail of legacy ones.
Lets a repricing or repackaging reach existing revenue, not just new signups.
Reduces the operational and support load of maintaining plans that should be retired.
Done carefully, a migration protects the customer relationship through the change. Done carelessly, it can surprise subscribers with a new price or a lost feature and drive cancellations, so timing and communication carry real weight.
How plan migration works
Migrating subscribers is a planned sequence rather than a single switch. A typical approach:
Map each source plan to its target plan, deciding what happens to price, features, and billing period.
Decide the timing, such as moving subscribers at their next renewal or on a set date.
Choose how to handle any mid-cycle price difference, for example proration, a credit, or no change until renewal.
Notify affected subscribers ahead of the change, especially when the price goes up.
Execute the move, either in bulk or as each subscription renews.
Confirm subscribers landed on the correct plan and reconcile billing after the change.
Whether these steps run as a bulk action or one subscription at a time, and exactly how proration is calculated, depend on the billing platform. In Recurly there is no dedicated bulk-migration action: subscribers are moved one subscription at a time, whether through a manual edit in the UI or a script iterating over the API. Proration is calculated as the ratio of days remaining to the full billing period, applied against the new price.
Benefits and examples
Plan migration lets a subscription business evolve its catalog without stranding existing customers or freezing revenue on outdated plans. The main benefits are a cleaner plan lineup that is easier to bill and support, the ability to apply new pricing to the current base, and a controlled, communicated change that limits churn risk.
As an illustrative scenario, imagine a business retiring two old plans, Basic at $8 per month and Plus at $15 per month, in favor of a single Standard plan at $12 per month. It might migrate Basic subscribers up to Standard at their next renewal with advance notice, and move Plus subscribers to Standard at the same time, presenting the change as a lower price for that group. The amounts here are hypothetical and used only to show how a mapping can work.
Frequently asked questions
What is plan migration? It is moving existing subscribers from one plan to another while their subscriptions stay active, typically when a plan is renamed, repriced, restructured, or retired.
When should subscribers be migrated, at renewal or immediately? Both are common. Moving subscribers at their next renewal avoids mid-cycle proration and feels less abrupt, while an immediate move applies the change to everyone at once. The right choice depends on the price change and how much notice you have given.
How are mid-cycle price differences handled during a migration? Options include prorating the difference, issuing a credit, or leaving the current cycle unchanged and applying the new price at renewal. In Recurly, a price increase applied immediately generates a charge calculated as (days remaining ÷ full billing period) × the new price when prorated, or simply the price difference if you choose the full-charge option instead of proration.
Can I migrate many subscribers at once? Bulk migration depends on the tooling your billing platform provides. Recurly does not offer a native bulk-migration UI action; moving many subscribers at once means writing a script against the Change Subscription API endpoints to iterate through the affected accounts.
