Two facts get blurred in the account team's framing, so separate them first. End-of-sale means the legacy SKU cannot be purchased new after the cutover. End-of-life, which is a different and later event, is when support or the product itself goes away. Confuse the two and you will re-paper your whole estate in a panic on the vendor's terms. The wider pricing picture sits in our 2026 guide to agentic AI ITSM pricing and negotiation; this piece is the action plan for the SKU transition specifically.
Book an AI cost control review →What actually changes on 1 July 2026?
From that date, new ServiceNow purchases land on the Foundation, Advanced and Prime structure rather than the old four-tier model. AI capability that used to be sold separately is bundled into the higher tiers from April 2026, which is the commercial point of the whole exercise: the new structure is built to carry AI pricing. If your contract is mid-term, nothing breaks on 1 July. If your renewal falls near it, you will be quoted on the new tiers, and that is where attention belongs.
Does end-of-sale force me onto the new AI tiers?
Not directly, but it removes the comfortable default of renewing the old SKU as-is. When the legacy tier cannot be sold new, your renewal becomes a re-mapping exercise onto Foundation, Advanced or Prime, and the vendor controls the translation unless you do it first. The buyer who maps their own estate onto the new tiers walks in with a position. The buyer who waits for the vendor's mapping inherits whatever tier carries the most AI margin.
The detail of how the three new tiers price out, and which one your estate genuinely needs, is in negotiating the new Foundation, Advanced and Prime tiers. Do that modelling before the quote, not after.
Legacy versus new structure: the buyer-side translation
The table maps the vendor's transition story to what it means for your wallet. List figures vary by deal size and should be confirmed against your order form, so this is direction, not a price sheet.
| Element | Legacy model (pre-July 2026) | New model and the buyer risk |
|---|---|---|
| Tier structure | Standard / Pro / Pro Plus / Enterprise | Foundation / Advanced / Prime, re-mapped by the vendor unless you map first |
| AI pricing | Sold as separate add-ons | Bundled into higher tiers from April 2026, harder to isolate and challenge |
| Buying the old SKU | Available | End-of-sale 1 July 2026: cannot be purchased new |
| Renewal leverage | Renew as-is as a fallback | No as-is fallback, so preparation replaces the default |
What must ServiceNow buyers do before the cutover?
Run these five steps. They convert a vendor deadline into a buyer plan.
- Confirm your real dates. Pull your order form and establish exactly when your term ends and when the renewal conversation opens. Plan from your dates, not the vendor's headline date.
- Map your true entitlement. Reconcile fulfiller counts and tier usage before the vendor quotes the new structure, so the translation starts from reconciled need rather than inflated history.
- Model the new tiers. Cost Foundation, Advanced and Prime against your actual usage and identify the single capability that would push you up a tier. Often it serves a handful of people and carries the whole base.
- Isolate and cap the AI. Treat bundled AI as a separately priced, separately capped line. Fix a unit rate and a hard ceiling so consumption cannot run away after cutover.
- Time the renewal deliberately. Use the deadline as your lever. A renewal worked six to nine months out keeps the clock on your side; a renewal worked in the final weeks hands it to the vendor.
Our gated ServiceNow Now Assist cost control guide includes the tier-mapping worksheet and the AI cap language that keep a SKU transition from becoming a price rise.
How do I keep the deadline working for me, not against me?
Deadlines cut both ways. ServiceNow wants the transition booked, in volume, before the cutover, which gives a prepared buyer real leverage in the window leading up to it. The vendor would rather close your migration than lose the timing, and a buyer who can credibly choose to renew late, or to contest the tier mapping, is a buyer the account team has reason to sharpen its pencil for. The discipline behind that is benchmark evidence: a target grounded in what estates of your size actually pay, not in the vendor's value narrative.
This is the same method that, across more than 500 engagements since 2019 and over $420M in ITSM contract value, has delivered a 30% average reduction. The number does not come from a single discount. It comes from refusing the vendor's baseline and rebuilding it line by line, which is exactly what a SKU end-of-sale demands. Run the engagement through our AI cost control service on fixed fee or gainshare, with the full account context on the ServiceNow platform page.
What will the account team argue, and how do you answer?
The transition gives the vendor a script, and it is worth knowing the lines before the call. "You have to move before 1 July or lose your pricing." You will not lose an in-term entitlement, and a renewal worked early keeps your pricing leverage intact, so the deadline is a planning input rather than a gun to your head. "The new tiers are simpler and better value." Simpler for the vendor to sell, certainly; better value only if your usage matches the tier you are mapped to, which is why you model the mapping yourself rather than accept theirs. "AI is included now, so there is no separate cost." Included in the price you pay for the higher tier, which is not the same as free; insist on seeing the AI as its own line so you can challenge it.
A worked example shows the trap. Suppose your estate sits comfortably on a legacy Pro footprint and uses one capability that only the top new tier carries. The vendor maps the whole base to Prime to capture that one capability, and the per-fulfiller rate applies to everyone. The buyer-side answer is to isolate the capability, count how many people genuinely need it, and either license those few differently or weigh the cost of the whole base at Prime against doing without. That single piece of analysis, done before the quote, is often worth more than the headline discount the vendor offers to close.
The discipline behind all of this is the same Map, Benchmark, Leverage, Close sequence we run on every renewal: map the true estate, benchmark the rate against deals of your size, build the leverage of a credible timeline, and close terms that survive the next cycle rather than just a price for this one.
Frequently asked questions
- What happens to ServiceNow legacy SKUs on 1 July 2026?
- They go end-of-sale. New purchases move to Foundation, Advanced and Prime, with AI bundled from April 2026. You cannot buy the old SKUs new after that date, but an in-term contract continues. Confirm your dates against your order form.
- Does end-of-sale switch off my current contract?
- No. End-of-sale only stops new purchases of the legacy SKU. Your existing entitlement runs to term. The pressure point is the renewal, where the deadline is used as a stopwatch.
- How do I keep leverage through the transition?
- Map your true entitlement first, model the new tiers against real usage, isolate and cap the AI, and time the renewal so the deadline favours you. Benchmark every line against deals of your size.
Turn the deadline into leverage.
We map your estate onto the new tiers, isolate and cap the AI, and time the renewal so the cutover works for you. Fixed fee or gainshare.
Book an AI cost control review →