Grandfathering: keeping old customers on the old price

Grandfathering, sometimes framed as a legacy or acquired-rights clause, means keeping current customers on the old price or plan after a price increase or a change in packaging. New customers sign up under the new terms, and the old ones stay exactly where they were, as if the increase had never happened for them.

The term describes a transition choice, not a metric. The company deliberately leaves part of the base frozen on a legacy price. That creates two worlds living side by side for a while: the current list price, which carries future revenue, and the old contracts, which preserve the relationship with early customers.

The logic is protecting the relationship with people who already trusted the product. A price increase communicated carelessly can trigger cancellations, and grandfathering acts as a shock absorber: old customers do not feel the increase, the sales team avoids hard conversations, and churn does not spike in the month after the change.

There is also a fairness component. Customers who joined early, often when the product was more immature and riskier, feel they deserve the price they committed to. Keeping that price signals loyalty, reduces public complaints, and avoids a wave of refund requests right after the announcement.

The short-term relief comes with a trade-off. Every customer kept on the old price is revenue that does not track the value the product now delivers, which works as a silent ceiling on expansion. The gap between the old and the new price becomes an opportunity cost that grows with every renewal.

There is an operational cost too. A base with several legacy prices and packages is harder to support, to reprice, and to migrate later: code, billing, and support carry exceptions for years. Because retention is one of the factors that weigh most on the value of a SaaS, according to research from SaaS Capital, it makes sense to protect the customer, but not to the point of permanently freezing the ability to grow revenue inside the base.

The alternative to grandfathering is migrating the whole base to the new price, with advance notice and a designed transition. Instead of freezing terms, the company gives time (say, sixty or ninety days of notice), explains why the price is changing, and offers incentives to soften the move: a guaranteed window at the old price, a loyalty discount for a few months, or an upsell that delivers more value for the new price.

Migrating everyone preserves a simple base and full revenue potential, at the cost of a more delicate conversation. Grandfathering does the opposite: it avoids the conversation now and pushes the complexity forward. Many teams combine both, keeping old customers for a defined period and migrating them in stages, rather than picking one extreme.

The decision depends on how far the old price sits from current value and how price-sensitive the base is. If the product has evolved a lot and adopted value-based pricing, keeping old contracts indefinitely can get expensive. If the increase is small and the base is large and sensitive, temporary grandfathering protects the relationship without giving up much revenue.

A practical rule is to treat grandfathering as a transition, not a permanent state. Define how long old customers stay protected, which plans will be discontinued, and what the migration path looks like. OpenView, a well-known pricing research firm, often notes that price is the most under-invested lever in SaaS: reviewing prices regularly and planning the transition avoids piling up a base that is impossible to reprice.

Communication decides the outcome. The announcement has to be clear about what changes, for whom, when, and why, and it has to arrive before any new charge. State explicitly who is protected by the old price and for how long, so the old customer feels recognized and the new one understands the rules.

Tie the increase to value delivered, not to internal costs. List what the product has gained since the last price, offer a clear path for anyone who wants to change plans, and keep a channel open for questions. Done this way, grandfathering becomes part of a story of growth and trust, rather than a patch to postpone a hard decision.