Blog · Commercial Model
The ServiceNow standard tier sunset is part of the 2026 commercial model change, where the legacy ladder of Standard, Pro, Pro Plus, Enterprise and Enterprise Plus is replaced by Foundation, Advanced and Prime. If your estate still sits on legacy Standard, the ServiceNow standard tier sunset means your next renewal will move you onto a new tier, and the mapping you accept decides whether that move is a swap or an increase.
This post explains what the sunset means in commercial terms, where legacy Standard lands in the new model, and the buyer side moves that keep the migration from quietly raising your base.
In April 2026 ServiceNow collapsed five legacy tiers into three. Legacy Standard, the entry rung of the old ladder, has no direct shelf equivalent in the new model, so customers on it are migrated rather than renewed in place. AI is now bundled across all three new tiers, but it is metered, so the bundled framing should not be read as a free upgrade. The full tier structure is laid out in our ServiceNow new commercial model pillar.
The practical point is that a sunset is a forced decision moment. You cannot simply renew Standard as it was, which means the vendor controls the framing of where you go next, and that framing is a negotiation position rather than a fixed product fact.
For most entry level estates, legacy Standard maps to Foundation, the new base tier. Foundation carries core capability plus a bundled, metered assist allotment that Standard never had. The risk is not capability loss, it is the new variable cost: bundled assists are metered, large agentic actions consume materially more units than simple lookups, and exceeding the included pool triggers overage top up charges. So a tier that reads as an upgrade can introduce a cost line that did not exist on Standard.
Some estates will be steered toward Advanced instead, on the argument that the workloads have outgrown Foundation. That may be true, but it may also be an upsell, so the capability case for Advanced should be tested against actual usage. The migration mechanics are detailed in the ServiceNow renewal tier migration guide.
The migration inflates in familiar ways. The new tier carries its own list construction, so a quote drawn from that list rather than from your effective Standard rate can erase years of negotiated discount. The bundled assist story is used to justify an uplift above the typical 7 to 12 percent annual range. And the move is often paired with a multi year commitment that locks the new base before you have metered real assist consumption. Each of these is a position you can push back on. The same dynamics appear when legacy Pro Plus moves, covered in the ServiceNow Pro Plus to Advanced migration walkthrough.
Before accepting any Standard sunset mapping, do four things. Express the new quote against your effective Standard rate, not a fresh list, so your historical discount carries forward. Size the included assist pool to your real trailing consumption rather than the vendor default. Hold the uplift inside the negotiated range and avoid pairing the migration with a long lock until consumption is proven. And fix the overage rate in writing so a spike does not reprice at list. Handled this way, the sunset is a controlled swap. Run buyer side, our ServiceNow renewal negotiation service runs exactly this migration.
A forced migration is not only a risk, it is also a moment of leverage if you time it. Because the vendor needs you to move, you have a legitimate reason to reopen the whole commercial relationship rather than accept a quiet tier swap. That is the moment to benchmark your effective rate against what comparable estates pay, to renegotiate uplift mechanics, and to fix overage terms for the metered assists you are about to inherit. A sunset handled passively funds the vendor plan, while a sunset handled deliberately becomes the best renegotiation opening you will get for years.
Practically, start the migration conversation well before your renewal date so you are not deciding under time pressure, and align that conversation with the vendor fiscal calendar where discretionary discount is deepest. Bring your trailing assist consumption so the included pool is sized to reality, and insist the new base is expressed against your effective Standard rate. The capability you end up with will be the same either way. The price you carry for the next several years is decided in how you run this one move.
Foundation is the likely landing tier for legacy Standard, but accept it only after confirming it carries the capability your teams actually use. Map your current Standard entitlements against the Foundation feature set line by line, and flag anything that would push you toward Advanced so you can test that case against real usage rather than a sales assertion. Where Foundation genuinely covers your workloads, it is the right destination and the cheaper one, and you should resist any steer toward a higher tier that your usage does not justify.
Then turn to the assist layer, which is the genuinely new cost. Pull your trailing consumption, model it against the Foundation metering, and size the included pool to that figure rather than a default. Insist the overage rate is fixed in writing so a busy quarter cannot reprice at list, and avoid committing to a multi year term until you have seen real metered usage. A Standard customer who confirms the tier, sizes the pool to reality and fixes the overage walks into the new model with costs they control rather than costs the vendor forecasts on their behalf.
The wider lesson is that a forced change is also a permission slip. Because the vendor needs you to move off Standard, you have every reason to reopen the commercial terms rather than accept a quiet swap. Buyers who treat the sunset as an opening rather than an imposition come out the other side with controlled costs and a relationship reset in their favour, which is exactly the outcome the migration was not designed to give them.
NowNegotiations Advisory Team. Independent ServiceNow negotiation advisors with benchmark data from real enterprise renewals, buyer side in hundreds of enterprise software negotiations. Last updated May 1, 2026.
Legacy Standard is retired in the move to Foundation, Advanced and Prime. Most entry level estates map to Foundation, the new base tier, which adds a bundled but metered assist allotment.
It can, mainly through list reset, bundled assist framing and uplift rather than lost capability. Quote against your effective Standard rate and size the assist pool to real usage to control it.
Yes. Standard cannot be renewed in place under the 2026 model, so a migration is required. The leverage is in how you map, price and time that move, not in avoiding it.