Category: Plan Changes

Grandfathered SaaS pricing is the arrangement where existing customers keep paying an old rate after the vendor raises it for everybody else. It used to be indefinite by default. Loyal customers kept their price, sometimes for a decade, and nobody wrote it down because nobody had to.

That default has flipped. The 2026 pattern is time-limited grandfathering: twelve to twenty-four months of protection, paired with feature gates so anything new belongs to the current tier. Your rate is safe. Your product slowly stops improving.

Why vendors changed the deal

Grandfathering used to be a marketing expense that retention paid for. A customer sitting on a five-year-old rate still threw off near-100% gross margin, so protecting them cost the vendor an opportunity rather than a dollar.

AI broke that arithmetic. Inference is a real per-use cost, so a grandfathered customer who uses AI features can now cost the vendor actual money every month. Withholding those features forever is not an option either, because they are the roadmap, and a legacy tier that visibly falls behind churns on its own.

So the industry landed on time-limited grandfathering with feature gates. Existing customers get a defined runway, any increase is tied to visible new capability, and, in the part that matters to you, a protection that used to have no expiry date now has one.

The feature gate is the part people miss

Most buyers hear “your price is protected” and stop listening right there. The gate is where the cost actually accrues.

On a gated legacy tier your rate holds, but every new capability ships to the current tier instead. For a few months you will not notice. By month twelve your team is working around gaps that a competitor’s users do not have. By month eighteen the migration you turned down is one you are asking for, at whatever the price is by then, with no leverage at all, because you are the one who brought it up.

That is the design. Time-limited grandfathering does not stop the increase. It schedules it, and arranges for you to request it.

Whether that is a bad deal comes down to whether you use the gated features. A team that will never touch AI summarisation should take the gated legacy rate cheerfully and look again in a year. The mistake is accepting the gate without working out which side of that line you are on.

Six questions to ask before you sign

In writing, before renewal. Keep the answers.

1. Is our current tier being retired, and on what date? The whole conversation in one question. A vendor who will not answer it by email has answered it.
2. How long is the grandfathered rate guaranteed, and is that in the contract? “You’re fine for now” from an account manager who will have changed roles before your next renewal is not a commitment.
3. Which features are gated to the current tier, and which of those are on the roadmap? The forward-looking half is the half that matters, and the half they would rather answer vaguely.
4. What is the migration price, quoted today? Get the number while you can still do something with it. A migration quote at 120 days is a completely different document from the same quote at 20.
5. Does our uplift cap survive a SKU change? Usually it does not. A cap governs renewal of a product, and a retired product cannot be renewed. Better to find that out now than in the quote. See Forced SKU Migration.
6. If we migrate, is the new rate protected, and for how long? Routinely forgotten. Move to an AI tier with no cap and you are doing all of this again next year, from a higher base.

Getting the protection into the contract

Four clauses do most of the work. None of them are unusual asks.

• A price-hold with an explicit end date. The rate and the term, in writing. Without this the rest is decoration.
• A SKU-continuity clause. If the tier is discontinued mid-term, you migrate at an equivalent effective rate instead of at list. This is the clause that survives a forced migration, so it is the one to spend your negotiating capital on.
• An uplift cap that applies across SKU changes. The wording carries real weight here. A cap on “renewal of the Services” is far stronger than a cap on “renewal of the Plan”.
• A notice period on tier retirement. Ninety days minimum. Productiv gave four days’ notice on a full shutdown in August 2026, which is the argument for writing a number down rather than trusting the market norm.

If you have already lost it

Once the rate is gone, what is left are the moves that do not need the vendor to agree to anything. Reclaim unused seats, because most organisations are meaningfully over-licensed and a migration is the natural moment to audit. Consolidate overlapping tools, because AI bundling means you are probably paying twice for the same capability now. Trade term length for rate if you are staying regardless. And price one real alternative, not as a threat, just so you know.

Watch it happen to someone else first

Grandfathering usually ends for a vendor’s entire customer base at once, in a wave that starts months before it reaches your renewal date. Seeing the wave early is most of the advantage.

CopperFeed records those changes as dated entries: launches, releases, repricings and shutdowns, in the order they happened. The running list of retirements is in Legacy Plan Sunsets: Every SaaS Tier Being Retired in 2026.

Figures here come from published third-party reporting. General guidance, not legal or procurement advice. Contract language varies, and your own terms govern.

Forced SKU migration is what happens when a vendor kills the pricing tier you are on and tells you that at renewal you have to move to a pricier one. You are being upgraded against your will. The quote in front of you is a product decision nobody asked you about.

It is the defining renewal problem of 2026. PricePulse puts the average increase from AI-inclusive migrations at 24%, and that sits on top of ordinary list price movement rather than replacing it.

Why it is not simply a price increase

The distinction sounds like semantics right up until you are the one negotiating.

When a vendor raises the price of your existing plan, you have leverage. There is a prior price and a percentage. Procurement can hold up last year’s invoice and ask what changed. Plenty of enterprise agreements cap year-over-year increases outright, and even without a cap the conversation has a familiar shape: that is too much, meet me in the middle.

Retire the plan and none of that survives. There is no prior price for what you are being sold, because what you are being sold is new. The uplift cap in your contract governs the renewal of a product that no longer exists. Your benchmark is scrap. And the vendor is telling the truth when they say they have not raised your price: they have discontinued a product, which every software company has always been free to do.

That asymmetry is the whole game. It turns a negotiation into an announcement.

Why vendors are doing it now

AI cost recovery. Vendors spent two years building AI features, and inference is a real recurring per-use expense inside a business model that was built on near-zero marginal cost. That money has to come from somewhere.

Three options, one of them quiet:

• Add AI to the existing plan and raise the price. Honest, and it invites every enterprise customer to reopen terms at once.
• Sell AI as an add-on. Clean, except 2025 attach rates showed most customers just say no.
• Retire the non-AI plan. No renegotiation, no attach-rate problem, and finance books the revenue as a migration instead of an increase.

The third one won. Worth being clear-eyed rather than indignant here, because it is a rational answer to a real cost and some of these AI features are good. The objection is not that vendors charge for AI. It is that this particular mechanism removes your ability to decline, then bills the feature to people who will never open it.

How to recognise it in a quote

Forced migrations rarely announce themselves. Look for:

• A renamed line item. “Business” becomes “Business AI”. Same seat count, different SKU.
• A quote that arrives late. The compressed timeline is deliberate. A migration quote delivered three weeks out is one you cannot competitively bid, and everyone involved knows it.
• An uplift that does not match the vendor’s published increase. If the press release says +12% and your quote says +30%, the gap is the migration.
• Talk of “alignment” or “modernising your agreement”. Nobody modernises an agreement downward.
• A tier that has disappeared from public pricing. The single most reliable check you can run, and it takes two minutes against an archived copy of the page.

What actually works in the negotiation

Less than you would like. Not nothing. Roughly in order:

1. Start 120 days out. Almost all your remaining leverage is time. A vendor who can see you are out of runway has no reason to move, and every concession worth having (a competitive evaluation, a phased migration, a co-terminus extension) needs weeks you will not have at day 20.
2. Make them quote the migration separately. Insist on two numbers: the like-for-like renewal, and the migration delta. Vendors push back hard, because one blended figure is far easier to defend. The delta is the part you can actually argue about.
3. Ask for a term extension on the legacy tier. Often available, almost never volunteered. Twelve to twenty-four months of time-limited grandfathering is the standard 2026 shape, and you will not be offered it unless you ask. More on that in Grandfathered SaaS Pricing Is Ending.
4. Right-size seats at the same time. The most reliable lever on this list, because it is the only one that does not require the vendor to agree to anything. Most organisations are 10–20% over-licensed. A 25% rate increase on 20% fewer seats is roughly flat.
5. Price one real alternative. Not as a bluff. Bluffs are transparent and you will get called. Do it because if the migration is bad value you want to know what else is out there, and because a live competing quote is the only argument that has ever moved a renewal.
6. Trade term for rate. If you are staying anyway, a multi-year commitment is real value to them, and usually the cheapest concession they can hand back.

What does not work

Escalating to the AE’s manager on the last day. Citing an uplift cap on a discontinued SKU. Threatening churn you cannot execute, when they can see your usage data and know precisely how embedded you are. Waiting for a better offer at expiry, which is the exact moment your leverage hits zero.

Track it before it reaches your inbox

The best defence is finding out a tier is being wound down before the renewal notice lands, which usually means spotting that it already happened to somebody else. That is what CopperFeed records: dated entries for repricings, releases and shutdowns as they happen. The running list of retirements is in Legacy Plan Sunsets: Every SaaS Tier Being Retired in 2026.

Figures here come from published third-party reporting, linked inline. General guidance, not procurement or legal advice. Check your own contract terms.

A legacy plan sunset is when a software vendor retires the pricing tier you are on and tells you that, at renewal, you have to move to a different one. Your usage has not changed. Your seat count has not changed. The plan you bought just stops existing.

This became the most common form of SaaS price increase in 2026. It is why so many renewal quotes came back 20–30% higher with nothing on the invoice explaining it. Below is the pattern, then what we know is being retired.

Why legacy plan sunsets replaced ordinary price increases

Through 2024 and 2025, most large B2B vendors bolted an AI tier onto the top of their lineup. A new, more expensive SKU, sitting above whatever you already paid for. Buying it was optional, and plenty of buyers said no.

So in the first half of 2026 the strategy changed. Instead of selling you the AI tier, vendors started retiring the tiers underneath it. Salesforce, HubSpot, Notion and Asana have all been reported doing a version of this. PricePulse’s H1 2026 report pins an average 24% increase on AI-inclusive migrations specifically, and puts total H1 cost growth at 34% for companies spending north of $84K a year.

The mechanism is the point. Raise the price of a plan somebody is already on and you have invited a fight: they have a contract, a renewal date, and a procurement team holding last year’s number. Retire that plan and offer them a different one, and you have not raised anything. You are selling a new product, at a new price, because the old one is gone. Resubly calls this forced SKU migration. It is the most effective price increase available to a vendor who does not want the argument.

How to tell a sunset from a normal increase

On an invoice they look almost identical. In a negotiation they behave nothing alike. The tells:

• Your plan name changed. Last year said “Business”, this year says “Business AI”. That is a migration wearing a renewal’s clothes.
• The old tier is gone from the public pricing page. Compare it against an archived copy. A tier that has vanished from marketing is a tier being wound down.
• You were handed a date instead of a number. Sunsets come with deadlines. Price increases come with percentages.
• Nothing you actually use got better. The clearest signal of the four. If none of the features your team touches improved, you are paying for shelf space on someone’s AI roadmap.

What is being retired in 2026

What follows is a floor, not a ceiling. Vendors are wildly inconsistent about announcing this. Some give a year’s notice, some tell you at renewal, some tell one customer segment and nobody else.

Confirmed plan and tier retirements

Microsoft is the biggest single mover. Most Microsoft 365 products took an average 16% increase on 1 July 2026, with Microsoft 365 Apps at +17%, Windows E3 at +15%, Entra Plan 1 at +16%, and EMS E3 at +13%. Customers who renewed before 30 June could lock the old rate for another year. Separately, Microsoft has confirmed it is retiring close to 70 products and services across 2026, SharePoint Server 2016 and 2019, Project Server, SQL Server 2016, Dynamics GP 2016, NAV 2016 and InfoPath among them.

GitHub moved Copilot to usage-based billing on 1 June 2026, replacing premium request units with AI Credits metered on token usage. Base plan pricing held exactly as it was: Pro at $10/month, Pro+ at $39, Business at $19/user, Enterprise at $39/user. The price did not move and the bill did, because a fixed line in your budget became a variable one. Different problem, same finance meeting.

Price movement in the same window

Not sunsets, but the same pressure behind them. Notion and Ahrefs both took 25% in March 2026. Asana went up 23% the same month. Linear took 60% in February, ClickUp 58%. By category, design and development tooling led at roughly +57%, with automation at +50% and project management at +45%.

Full product shutdowns

Where a sunset ends up. Productiv announced it was retiring its SaaS management platform on 6 August 2026, leaving four days between the announcement and the shutdown. Remember that the next time a vendor assures you there will be plenty of notice.

What to do before your renewal

The window that matters opens about 120 days out. It closes the moment you sign.

1. Inventory your tiers now. For every contract over roughly $10K, write down the exact plan name and check whether it still appears on the vendor’s public pricing page. The ones that quietly disappeared are next year’s problem, and you have time to deal with them today.
2. Ask the question in writing. “Is our current tier being retired, and if so, when?” A vendor who will not answer that in an email has answered it.
3. Price the migration early. If the answer is yes, get the AI-tier quote while there is still room to look at alternatives. A quote that lands three weeks before renewal is not a negotiation, it is a deadline.
4. Separate the AI question from the renewal question. If you would not buy the AI tier on its own, say so out loud. Some vendors will hold your rate. The ones that will not have told you something useful about the relationship.
5. Get the terms in the contract. A verbal “you’re fine for now” is worth nothing at the next renewal, when your account manager has moved on and nobody remembers the call.

That last point is the subject of Grandfathered SaaS Pricing Is Ending. The negotiation mechanics are in Forced SKU Migration: Why Your Renewal Quote Jumped 24%.

Tracking this as it happens

Pricing trackers tell you what a tool costs today. Shutdown trackers tell you what already died. Neither one covers the plan that still exists but is being wound down, which is where the money actually moved in 2026. That gap is what CopperFeed records: dated entries for launches, releases, repricings and shutdowns, in the order they happened.

Figures here come from published third-party reporting, linked inline. Vendor plans change without notice. Check your own contract before acting on any of it.