Grandfathering SaaS Pricing: A Retention Framework

Grandfathering pricing plans means letting existing customers keep their old price when you raise prices for new customers. It protects retention in the short term.

Held too long, it creates a second problem. A growing group of customers ends up paying far below what your product is worth.

When consulting clients, I've watched a retention conversation turn into a pricing one the moment someone asks how many customers are still on the old plan. Nobody budgets for that question until the gap is big enough to hurt.

This guide shows you how long to hold a legacy rate, and when to end it.

Key takeaways

• Drop the price-increase cancel trigger for your existing base by grandfathering their rate.
• Weigh a revenue gap that widens every renewal cycle you hold the old price.
• Watch Parseur bill some customers $9/month for a plan now priced at $129.
• 71% of subscribers name a price increase as their top reason for leaving.
• Tie a sunset to the customer's renewal date, not an arbitrary calendar cutover.

What is grandfathering in SaaS pricing?

Grandfathering means letting existing customers keep their current price after you raise prices for new customers. It's a retention tactic that trades short-term churn avoidance for a long-term, growing revenue gap. Legacy pricing is the same thing under a different name.

The existing customer's invoice doesn't change, so the price increase gives them no reason to cancel.

But now you run two prices for the same product, and you run them indefinitely. That costs you revenue and support overhead, not just goodwill.

Parseur, an email-parsing tool, still bills some customers on a discontinued 1,000-credit plan at $9/month. New customers pay $129/month for the same plan today.

Co-founder Sylvain Josserand has said those early customers were critical to the company's survival, so it holds the rate on purpose. The company pays that 14x gap by choice.

Grandfathering isn't the only response to a price increase. Some companies raise prices for everyone instead, and that clean increase sometimes serves the business better.

Grandfathering vs. raising prices for everyone

The two choices put the churn risk in different places. Grandfathering shields your existing base and grows a revenue gap. A clean increase keeps one price but risks losing current customers.

In Recurly's research, 71% of survey respondents named price increases as the top reason they lost customers.

Raise prices without grandfathering, and every existing customer re-checks the subscription the moment it gets more expensive. A cancel-flow prompt creates that same trigger on purpose, except here it fires across your whole base at once.

Grandfathering removes the trigger for existing customers, and you pay for it with the revenue gap instead.

Read the 71% figure from Recurly's research with care. It's what people report as their top reason for losing customers. It is not proof that every price increase causes churn in step. Treat it as a signal that price changes are the moment customers reconsider.

If you're leaning toward raising prices for everyone, that path has its own churn math to work through.

How long should you grandfather old pricing?

There's no fixed grandfathering duration. The right length weighs a widening revenue gap against the churn risk of ending it. Both move in opposite directions the longer you wait.

Every renewal locks more of your revenue to the old price, and the gap grows further if you raise list price again. The churn risk of ending it climbs too.

Customers get more attached to a rate the longer they hold it, so a sunset three years in stings more than one at year one. Wait longer and you make both the gap and the exit worse.

Put a number on it.

Per Parseur's report above, that $9 plan is $120/month below current list price, per customer, every month it stays open. Multiply that by the accounts still on it, and you have the running cost you weigh against the churn risk of sunsetting.

Churn.io's monthly recurring revenue (MRR) calculator can total it up.

The longer the plan stays open, the more accounts stay on the old price.

A second cost has nothing to do with churn. Raise prices several times without sunsetting old plans, and you end up running several legacy tiers at once. Every tier is a separate billing edge case and a support burden.

So set a duration limit for that reason alone, even when churn risk wouldn't force one.

How much should you grandfather?

You can grandfather the price only, or freeze the entire plan. Scope is a separate decision from duration, and the two options carry different long-term costs. Price-only keeps the old rate but treats new features as paid add-ons. Full-plan freezes both the price and the feature set.

Parseur uses the price-only approach. Per Parseur's report, legacy customers keep the $9 rate and pay separately for new features and integrations. The product can evolve for everyone while the discount stays contained to price alone.

Full-plan grandfathering freezes the customer on old features too. That adds to the support burden, since you now maintain a feature set you may no longer sell.

Price-only carries its own risk. Say your new features are the main reason people pay for the product. Splitting them out as paid add-ons can feel like a bait-and-switch to legacy customers. 

Scope depends on whether your new features are genuinely optional or the reason people stay.

Billing cadence is a separate lever from scope. If you're rethinking how you price more broadly, annual vs. monthly billing moves retention on a different axis than what you freeze for legacy customers.

When to sunset a grandfathered plan

Sunsetting is safest when you tie it to a renewal point. Give affected customers a fixed migration window rather than an abrupt cutover. A renewal trigger folds the pricing conversation into a decision the customer was already going to make.

The renewal is their next natural decision moment. Attach the price change to it, and you avoid springing a new decision mid-cycle. Then give them time.

Commonly cited guidance runs 3 to 6 months for SMB accounts and 9 to 12 months for larger ones, enough to budget for the change.

The window and the communication do most of the work.

One documented migration of a legacy B2B tier hit an 87% migration rate before its deadline. It held total churn under 5%, and lifted revenue 12% on the accounts that moved. The deadline and the communication plan carried that result more than the price change did.

A customer who refuses to migrate is in a cancellation decision, whether or not you call it one. That's when the migration needs a real exit path, the same care you'd give a cancel flow.

So if you sunset a grandfathered plan, build the migration around a cancel flow that saves the customers who won't move on their own.

Pricing decisions are retention decisions, and the sunset is where the two meet.

FAQ

Does grandfathering count as a discount?

Grandfathering is usually a legacy price point, not a discount, since the customer pays what they originally agreed to. How you book it internally is a finance call, but framing it as a discount can hide the real cost of the gap.

Can you grandfather only some customers and not others?

Yes, and companies often limit it by signup date, plan tier, or account value rather than extending it to everyone. Deciding who qualifies is a separate question from what you freeze, and the narrower the group, the smaller the long-term gap you carry.

What if a grandfathered customer upgrades their plan?

An upgrade usually forfeits the legacy rate, because the customer is moving to a plan that didn't exist at their original price. Spell this out before the upgrade, so a customer who values the old rate isn't surprised into losing it.

Is grandfathering the same as a price lock guarantee?

No. Grandfathering applies after the fact when you raise prices, while a price lock is a promise you sell upfront at signup.