SaaS Pricing Grandfathering: How to Manage Legacy Customers Through Price Increases
Grandfathering existing customers during a price increase is a loyalty tool, not a revenue leak. The design of the grandfathering structure — duration, conditions, and the eventual migration — determines whether it builds retention or creates a permanent pricing problem.
Price increases are one of the most efficient growth levers in SaaS. Grandfathering is what separates a price increase that builds loyalty from one that triggers churn. The mechanics of grandfathering — how long, which customers, what conditions, and how the eventual migration happens — determine whether the price increase improves NRR or creates a two-year pricing headache.
Most SaaS founders treat grandfathering as a binary: either everyone gets the old price forever (losing the revenue benefit of the increase), or everyone gets the new price immediately (risking churn from customers who weren't expecting the change). The reality is more nuanced — a well-designed grandfathering structure protects both the customer relationship and the company's pricing integrity.
The Three Grandfathering Structures
Structure 1: Time-limited grandfather (recommended for most SaaS companies)
Existing customers maintain their current rate for a defined period (typically 6–12 months) after the new pricing is announced. At the end of the period, they migrate to new pricing on their next renewal.
Why it works: customers know the change is coming, have time to budget for it, and feel they received fair notice and fair treatment. The migration is scheduled and predictable for both the company (revenue planning) and the customer (budget planning).
Implementation: grandfather period is noted in the renewal contract or in a customer notification email. CS teams have a specific date to manage the migration conversation.
Structure 2: Indefinite grandfather (rarely the right choice)
Existing customers keep their current rate indefinitely — they are permanently exempt from new pricing as long as they remain customers on the same plan.
Why companies do this: it feels like the safest option during a price increase announcement. No migration to manage, no churn risk from the transition.
Why it creates long-term problems:
- The pricing differential between legacy and new customers grows over time (if you raise prices again, legacy customers get further behind)
- New customers become aware of the legacy rate through sales conversations, support tickets, and churn interviews — creating renegotiation pressure
- NRR from legacy customers is capped by the grandfathered rate, limiting expansion potential
- Sales efficiency decreases because proposals have to explain why a similar company is paying 40% less
Indefinite grandfathering is appropriate only when the price increase represents a genuine product fork — customers on the old product version are grandfathered on the old product at the old price, while new customers get a different product at new pricing. Shopify uses this model for legacy API version customers.
Structure 3: Conditional grandfather
Existing customers maintain their current rate as long as they meet specific conditions — most commonly, commitment length (rate maintained on a 2+ year contract) or usage tier (rate maintained if usage stays below a threshold).
Conditional grandfathering is an upgrade-incentive tool as much as a retention tool. "Keep your legacy rate by committing to a 3-year contract" converts a potential churn risk (customers who might leave over the price increase) into a retention and revenue commitment.
Works best for: enterprise accounts where the price delta is significant and the customer has budget flexibility to commit long-term. Less effective for SMB accounts where multi-year commitment is harder to obtain.
Designing the Grandfathering Communication
The design of the grandfathering communication matters as much as the structure itself. ProfitWell's research on SaaS pricing communication consistently shows that customers who understand the reason for a price change and feel treated with transparency accept the change at 3–4x the rate of customers who receive a transactional notification.
The four-part communication framework:
1. Lead with value, not price
The announcement should open with a substantive summary of what the product has delivered and what has been built since the customer's pricing was set. Not marketing language — specific product improvements, new integrations, feature expansions, and infrastructure investments that represent real value since the last pricing date.
"Since you joined us in [year], we've [specific improvements]. The [product metric] performance has improved by [X%], and we've added [N] integrations to the tools you use every day."
2. Announce the price change with the reason
State the price increase, the new price for the customer's plan, and the business rationale. Customers don't need a detailed P&L, but they do need to understand that the price change reflects real cost increases (infrastructure, support, development) or deliberate underpricing correction — not pure profit extraction.
"We're updating our pricing to better reflect the value we're delivering and to sustain the level of product investment you've seen over the past [period]."
3. State the grandfathering terms clearly
"As an existing customer, your current rate of $[X]/month is locked through [specific date]. You'll receive a second notification 60 days before your grandfathering period ends with details on the transition."
4. Offer the migration path proactively
Don't wait for the grandfather period to expire to have the migration conversation. Include the migration path in the initial announcement: "When your grandfather period ends, you'll have the option to continue at $[new price] or to lock in a multi-year rate."
Managing the Migration
The most critical moment in grandfathering is the migration from legacy pricing to new pricing. The companies that execute this well treat the migration as a renewal conversation, not a billing change.
90-day migration playbook:
Day -90: CS team is alerted to all customers whose grandfathering expires in the next 90 days. Review account health for each: usage trends, support tickets, NPS score, relationship strength.
Day -90 to -60: For high-value accounts (typically top 20% by ARR), personal outreach from CSM: "I wanted to connect ahead of your pricing transition to make sure you have everything you need and to share what's coming."
This call serves three purposes: relationship maintenance before a potentially difficult conversation; usage review to demonstrate value delivered; proactive identification of any accounts that are at risk before they receive the billing change.
Day -60: Formal notification email to all grandfathered accounts transitioning in the next 60 days. Include new price, transition date, and offer to discuss.
Day -30: For accounts that haven't responded to -60 day outreach: follow-up email with specific migration path options (continue at new pricing, commit to multi-year for rate lock, or options for right-sizing if usage has changed).
Day 0: Migration to new pricing. For accounts on multi-year commitments, the rate stays locked. For accounts on monthly billing, the new rate applies at the next billing date.
Day +30: Post-migration check-in for all high-value accounts. Confirm receipt of new invoices, confirm usage satisfaction, proactively address any concerns before they escalate to cancellation requests.
The Multi-Year Conversion Opportunity
The grandfathering migration period is the highest-conversion moment for multi-year deal upgrades. Customers who are about to face a price increase will consider locking in current or discounted pricing on a multi-year basis — a deal that benefits both parties.
The offer structure:
"Your current rate is $[X]/month. The new standard rate for your plan is $[Y]/month. If you commit to a 2-year contract, I can lock in $[Z]/month — saving you approximately $[amount] over the term compared to year-to-year billing at new pricing."
Where Z should be:
- 10–15% below new pricing for a 2-year lock
- 15–20% below new pricing for a 3-year lock
The customer perceives this as getting ahead of future price increases at a lower rate. The vendor gets predictable ARR and avoids annual renewal negotiation for the committed term.
Conversion rates for multi-year offers during grandfathering transitions typically run 20–35% for well-managed CS outreach — significantly above the 5–10% conversion rate for multi-year offers in non-transition periods.
Pricing Integrity After Grandfathering
The long-term risk of grandfathering programs is pricing complexity — a customer base segmented across multiple legacy rates that are hard to manage, report on, and sunset.
Preventing legacy rate accumulation:
Every grandfathering period should have a defined end. Commit to the principle that no customer should be more than two pricing cycles behind the current rate. If you raise prices every 18–24 months, the maximum lag for a grandfathered customer is 36–48 months before migration.
After migration, all customers should be on current pricing. A small subset may have multi-year rate locks that create temporary pricing differentiation — but those are dated and self-resolving.
Reporting on legacy rates:
In your NRR calculations and investor materials, segment ARR by customers on current pricing versus legacy pricing. This provides a more accurate picture of the economics and helps you model the uplift from grandfathered customers migrating to new pricing.
The price increase playbook covers the end-to-end process for raising prices, with grandfathering as one component of the strategy. For managing existing customers through pricing transitions more broadly, see SaaS pricing models comparison.
See Your Growth Ceiling Now
Calculate when your SaaS growth will plateau — free, no signup required.
The Grandfathering Decision Matrix
When to grandfather versus migrate immediately:
Grandfather (time-limited) when:
- Price increase is >20% for the affected customer's plan
- Significant portion of customer base is mid-contract rather than at renewal
- Enterprise customers with annual budgets that can't absorb mid-year changes
- Customer concentration is high (losing 2–3 customers materially affects ARR)
Migrate immediately when:
- Price increase is <10% and product value improvement since last pricing is well-documented
- All customers are on monthly billing (no mid-contract disruption)
- Churn rate in the customer base is low and satisfaction metrics are high
- The price change is at renewal time for all customers simultaneously
Conditional grandfather when:
- You have enterprise accounts willing to commit long-term in exchange for rate protection
- The price delta is large enough to justify a retention-for-commitment exchange
- Your CS team has bandwidth to manage the conditional negotiation at scale
The grandfathering structure is a customer success tool first and a revenue tool second. Design it to protect the relationship through the transition, and the revenue follows.
Frequently Asked Questions
What is grandfathering in SaaS pricing?
Should you grandfather all customers or only some?
How long should grandfathering last?
How do you migrate grandfathered customers to new pricing?
What happens to NRR when you have a large grandfathered customer base?
Related Posts
Enterprise SaaS Pricing: Discount Floors and Approval Tiers
A rigorous framework for enterprise SaaS pricing discount floors and approval tiers — covering discount governance, approval workflow design, the financial math of unmanaged discounting, and how best-in-class revenue operations teams protect gross margin.
9 min readAnnual vs Monthly Pricing Test: SaaS Cash Flow Trade-off
Measure the real impact of shifting customers to annual billing — the cash flow benefit, churn reduction, and revenue per customer trade-offs. Includes the annual discount break-even formula and experiment design for testing billing term incentives.
7 min readCohort-Based Pricing Experiments for SaaS
Use cohort analysis to run pricing experiments that isolate causal effects from confounders. Covers cohort design, measurement windows, holdout groups, and interpreting cohort-level pricing signal.
9 min read