Grandfathering

Grandfathering, sometimes called a grandfather clause, is the practice of allowing existing subscribers to keep their current plan, pricing, or terms even after a company changes its pricing or packaging for new customers. Existing customers are "grandfathered in" and continue paying the old rate or keeping the old feature set, while new signups move to the updated plan structure going forward.

Grandfathering comes up most often when a subscription business raises prices, restructures plan tiers, or retires a legacy plan altogether. Rather than forcing every existing customer onto new terms the moment a pricing change ships, the business lets the existing base continue on the terms they originally signed up for, either indefinitely or for a defined transition window. Supporting this well depends on the billing system's ability to run multiple plan versions or price points at once, since grandfathered and new customers are on different terms simultaneously. Supporting this well depends on the billing system's ability to run multiple plan versions or price points at once, since grandfathered and new customers are on different terms simultaneously. Recurly supports this natively: updating a plan's price only affects new subscribers immediately, while existing subscribers remain on their original price until explicitly migrated — so a single plan can carry two price points at once with no special configuration.

For grandfathering by attribute rather than by signup date, such as by region or account type, Recurly's Price Segmentation feature supports this directly: grandfathered subscribers keep their original segment code and price, while new subscribers are created with the current segment code — all within the same plan, with no migration or plan duplication needed.

Why grandfathering matters for subscription businesses

Price increases are one of the more common triggers for customer churn, so grandfathering is often used as a retention tool during a pricing change. By letting existing customers keep their current rate, a company avoids putting immediate pressure on the accounts most likely to react negatively to a sudden price jump, preserving goodwill and giving customer success teams time to communicate the change on their own terms.

That protection comes with a tradeoff. Over time, grandfathering can leave a company with a growing base of legacy price points, some of which sit well below current market rates for the same service. Every additional grandfathered cohort adds operational complexity to billing, reporting, and forecasting, since revenue per customer no longer maps cleanly to a single current price list. Businesses that grandfather customers need an eventual plan for when grandfathering ends and how the legacy base gets migrated, rather than treating it as a permanent state.

How to run a grandfathering strategy

• Decide the scope of what is being grandfathered: price only, or price and the associated feature set together, since older plans sometimes include features later removed from new plans.

• Decide the duration: grandfathering can run indefinitely or for a defined window, such as twelve months, after which affected customers are migrated to current pricing.

• Communicate proactively to affected customers that they have been grandfathered, and be specific about what could end that status, such as changing plans or adding certain features.

• Configure the billing system to support the old plan or price point alongside the new one, so grandfathered customers continue billing correctly without manual workarounds. In Recurly, date-based grandfathering needs no extra setup, since unmigrated subscribers simply stay on their existing plan price, while attribute-based grandfathering across segments is easier to manage with Price Segmentation than with separate duplicate plans.

• Set a review cadence to periodically assess the size and margin impact of the grandfathered base and decide whether and how to eventually migrate it.

Grandfathering vs forced migration

Grandfathering is one of several ways a company can handle a pricing or plan change. The other common approach is forced migration, where all customers are moved to the new pricing on a set date, typically with advance notice. Forced migration captures the benefit of updated pricing across the entire customer base immediately, but it carries a higher churn risk, since every affected customer experiences the change at once. In Recurly, this is typically executed as bulk subscription changes via the UI or API, scheduled either immediately, at each subscriber's next bill date, or at term renewal. A middle path, opt-in migration, offers existing customers the choice to move to the new plan voluntarily, sometimes with an incentive to do so. Grandfathering is the most customer-friendly of the three in the short term, but it is also the option most likely to leave a persistent gap between legacy and current pricing if it is never revisited.

Benefits and examples

Used deliberately, grandfathering gives subscription businesses a few concrete advantages:

• Lower short-term churn risk during a pricing change, since existing customers are not immediately confronted with a higher bill.

• Preserved customer goodwill and trust, which matters for renewal and expansion conversations later.

• Time to communicate a pricing change thoughtfully rather than under pressure from an abrupt cutover.

• A cleaner customer success narrative, since legacy customers can be told they are valued enough to be protected from an immediate change.

As an illustrative example, imagine a subscription company raises its standard plan price from $49 per month to $59 per month for all new signups starting the first of next month. The company decides to grandfather its 2,000 existing standard plan subscribers at the old $49 rate for 12 months, after which they will be migrated to the new pricing with 60 days' notice. During that 12 month window, those 2,000 customers continue generating $49 x 2,000 = $98,000 per month from that plan, rather than the $59 x 2,000 = $118,000 per month the same base would generate at the new rate. That $20,000 monthly gap is what the company accepts in exchange for lower churn risk during the transition.

Common mistakes with grandfathering

• Grandfathering customers indefinitely with no plan to revisit the legacy pricing, which leaves a large, low-margin base with no migration path.

• Failing to clearly communicate to customers that they have been grandfathered and what would cause that status to end.

• Using a billing system that cannot cleanly support multiple concurrent price points, which creates operational and reporting complexity as the number of legacy cohorts grows.

• Treating grandfathering as a one-time decision rather than a policy that needs periodic review as the legacy base ages.

Frequently asked questions

Does grandfathering mean a customer's price never changes? Not necessarily. Grandfathering can be indefinite or can run for a defined transition window, after which the customer may be migrated to current pricing, often with advance notice.

Can grandfathering apply to features instead of just price? Yes. Some companies grandfather both price and a specific feature set together, especially when a plan restructuring removes or bundles features differently for new customers.

Why would a company eventually end grandfathering? As the grandfathered base grows, the gap between legacy and current pricing can create a meaningful revenue and margin impact, and maintaining many legacy price points adds operational complexity, which often prompts a planned migration.

Is grandfathering the same as a price lock guarantee? They are similar in effect, but grandfathering usually applies in the context of a broader pricing or plan change for new customers, while a price lock guarantee is often marketed proactively as a standing feature of a plan, independent of any pending pricing change.