Should You Grandfather Customers on a Legacy Plan?

Should you grandfather existing customers when you change your SaaS pricing?

Grandfather them for a fixed period, not forever. A time-limited grace window, often six to twelve months, protects goodwill and gives customers time to plan. Permanent grandfathering feels kind at launch but slowly splits your customer base into tiers you cannot support, price, or report on cleanly.

Every SaaS company that changes its pricing hits this question within the first week. The new plans are ready, the pricing page is designed, and then someone asks what happens to the hundred customers on the old plan. The easy answer is to leave them alone. That answer has a cost that shows up later, usually when nobody remembers why the old plan exists.

I work with B2B SaaS teams on go-to-market and the systems behind it, and in my view legacy plans are one of the quietest sources of mess in a CRM. They are rarely a pricing problem on day one. They become an operations problem by year two.

What does grandfathering actually mean?

Grandfathering means existing customers keep their old price, old features, or both after you launch new pricing. It can be permanent, time-limited, or tied to a condition such as staying on annual billing. The term covers many different promises, so the first step is deciding exactly which promise you are making.

There are at least three versions. Price grandfathering keeps the old price but moves the customer onto the new plan structure. Plan grandfathering keeps the whole old plan, features and limits included. And conditional grandfathering keeps the old terms as long as the customer meets a rule, such as renewing on time or not changing seat count.

These look similar from the outside, but they create very different work inside the company. Plan grandfathering is the most expensive to support, because your product, billing, and support teams must keep an old package alive. Price grandfathering is easier, because everyone is on the same features and only the invoice differs.

Why do founders default to grandfathering forever?

Because it avoids an uncomfortable conversation. Early customers took a risk on the product, and raising their price feels like punishing loyalty. Founders also fear churn spikes. So they promise the old plan forever, which solves this quarter's anxiety and quietly creates a long tail of exceptions.

I understand the instinct, and I think it comes from a good place. Early customers often shaped the product. Many of them pay less because the product was worth less when they joined. Protecting them feels fair.

The problem is that forever is a long time. In three years, the product may be worth several times what it was. The early customer is now paying a price that has nothing to do with the value they get, and the company cannot fund the roadmap that customer benefits from. Generosity that cannot be sustained is not really generosity. It is a debt that comes due later.

What does a legacy plan cost you over time?

It costs you clarity. Every legacy plan adds a branch to your billing logic, your CRM reports, your support playbooks, and your product's permission checks. Revenue reporting gets harder, expansion motions break, and nobody can say with confidence what a customer is entitled to without opening a contract.

In the CRM, this shows up as plan fields with values nobody uses anymore, and deals that cannot be forecast cleanly because their pricing follows old rules. In support, it shows up as agents asking whether a customer on an old plan should have access to a feature. In product, it shows up as feature flags that exist only to protect a handful of accounts.

The worst cost is to expansion. When a grandfathered customer wants to add seats or a new feature, the sales team has to invent a price. That usually ends in either a discount that undercuts the new pricing or an awkward conversation that sours a happy customer. Some teams end up avoiding upsells to legacy customers entirely because nobody wants to have that conversation.

When does grandfathering make sense?

Grandfathering makes sense when the customer group is small, the price gap is modest, and the old plan maps cleanly onto the new structure. It also makes sense as a deliberate retention play for your most strategic early accounts, as long as it is written down, time-bound, and owned by someone.

There are honest cases for it. If you have twenty early customers who act as references and case studies, protecting their price for a year is cheap marketing. If the new price is only slightly higher, the support cost of migrating may outweigh the revenue gain. And if the old plan is identical to a new plan except for price, keeping the old price is almost free operationally.

The key word is deliberate. Grandfathering should be a decision with an end date and a named owner, not a default that nobody revisits.

How do you sunset a legacy plan without losing customers?

Give customers a clear end date, a reason in plain language, and a better path forward. Announce early, offer a transition discount or extra features that make the new plan feel like an upgrade, and let account owners talk to the most valuable customers personally before the email goes out.

The sequence I recommend looks like this in prose. Start by sorting legacy customers by revenue and strategic value. Talk to the top group personally, so no important customer learns about the change from a mass email. Then announce the change to everyone with at least one billing cycle of notice, and usually more for annual customers. Explain what they gain on the new plan, not just what they pay. Offer a time-limited transition price that steps up toward the new rate.

How you word that announcement matters as much as the timing. I covered the messaging side in how a SaaS should announce a price increase. The short version is to lead with what the customer gets, be specific about dates, and never hide the change in fine print.

Before you send anything, check your contracts. Some customers may have terms that lock their price for a set period. Those terms win, and your plan should respect them.

How should your CRM track grandfathered accounts?

Track them with explicit fields, not tribal knowledge. Every grandfathered account should have a legacy plan flag, the original price, the agreed end date of the grace period, and the owner responsible for the migration conversation. Then build a report that lists every account approaching its end date.

This is where most teams fall down, and it is the part I care most about as someone who builds GTM systems. A promise made in a founder's email is invisible to the rest of the company unless it lands in a field. Six months later, a new sales rep sends an expansion quote at the new price, and the customer forwards the founder's original email. Trust takes a hit that was completely avoidable.

In HubSpot or Salesforce, I would set up a simple property set on the company record and a workflow that creates a task for the account owner sixty days before the grace period ends. That one automation turns a fuzzy promise into a scheduled conversation. If you are reworking packaging at the same time, my notes on handling pricing and packaging changes for existing customers cover the broader rollout.

What is my rule of thumb?

Grandfather the price for a defined window, migrate everyone onto the same plan structure, and track the promise in the CRM. One product, one set of plans, and clearly dated exceptions. That keeps goodwill with early customers without freezing your pricing or your reporting for years.

I would rather have a slightly harder conversation now than a permanent exception that every future hire has to learn about. Customers respect clear, early, honest communication far more than founders expect. Most of the churn fear I hear about never shows up when the change is explained well and the customer is given time.

There is also a growth reason to migrate. Once everyone is on the current plans, you can run clean expansion motions. Knowing when to ask a customer to upgrade is much easier when every customer sits on the same ladder.

What should you do next?

List every customer on a legacy plan, note what they pay and what they were promised, and decide on one end date for the grace period. Add those details to your CRM as explicit fields, then plan personal conversations with your most important accounts before any announcement goes out.

If you are about to launch new pricing, decide your grandfathering policy before the pricing page goes live, not after the first support ticket. Write it down in one paragraph that sales, support, and finance can all read. That paragraph will save you more time than any pricing calculator.

I help B2B SaaS teams design their go-to-market and the CRM systems that carry it, including the fields and workflows that keep pricing promises visible. If you want help planning a legacy plan migration, reach out at pravinkumar.co. Let's chat.