Case study · Mining · Tier migration
This ServiceNow mining tier migration case study shows how a diversified mining group avoided a blanket move to the top tier, split its mapping across Advanced and Prime, and capped the renewal, using benchmark data from real enterprise renewals.
Reduction versus the migration quote
Saved over the three year term
Tier mapping right sized before signature
A diversified mining group reached renewal as the 2026 commercial model took effect and was handed a migration quote that mapped its legacy entitlements straight onto Prime, the most expensive of the three new tiers. The account team framed Prime as the natural home for a large estate. The group brought us in buyer side to test that mapping against benchmark data from real enterprise renewals before signing. The wider approach sits in our ServiceNow renewal guidance.
The estate had been licensed years earlier on the legacy Enterprise tier across ITSM, ITOM and HRSD. With the five legacy tiers, Standard, Pro, Pro Plus, Enterprise and Enterprise Plus, replaced by Foundation, Advanced and Prime in April 2026, every line needed a new mapping. The vendor proposal moved the whole estate to Prime, carrying a full uplift on top. With renewal inside the quarter, the default was to accept Prime as a like for like upgrade.
Our first task was to test the mapping workflow by workflow rather than accepting a single tier for the whole estate. We compared what each team actually used against the capabilities that distinguish Advanced from Prime, using the framework in our ServiceNow tier migration mapping guidance.
Most of the estate did not need Prime. The capabilities that justify the top tier were used by a minority of workflows, while the bulk of ITSM and HRSD use sat comfortably within Advanced. Mapping the whole estate to Prime was charging the group for headroom it would not touch. The fulfiller and requester split had also drifted, with people who only approved work holding full fulfiller licensing they did not need.
We built the strategy around three moves. First, a split mapping that placed the minority of workflows needing Prime on Prime and the majority on Advanced, rather than a single tier for all. Second, a right sizing of the fulfiller count, moving approval only users off fulfiller licensing. Third, a capped uplift on the renewal, fixed below the 7 to 12 percent default and tied to the new baseline. The detail of this work sits in our ServiceNow renewal tier migration guidance.
The group team led the conversations. We stayed behind the table, modelling each mapping scenario and briefing executives before each session, in the pattern set out in our ServiceNow renewal negotiation advisory.
The agreement signed inside the renewal window. The split tier mapping and the fulfiller right sizing brought the deal in roughly 24 percent below the migration quote, with the uplift capped and the new baseline set on the corrected entitlements. Across the three year term the mapping work saved the group in the region of 1.6 million dollars. Comparable engagements appear in our insurance tier migration and manufacturing ELA renegotiation case studies.
Three lessons carry beyond this engagement. A tier migration is a per workflow mapping exercise, not a single tier decision, because mapping a whole estate to the top tier charges for headroom most teams never use. The fulfiller and requester split should be corrected at the same time, since migration is the natural moment to move approval only users off full licensing. And the renewal baseline that the new mapping sets will compound, so capping the uplift on the corrected baseline matters as much as the tier choice itself.
The mining group avoided a blanket move to Prime, split its mapping so only the workflows that needed the top tier sat on Prime while the majority moved to Advanced, right sized the fulfiller count, and capped the uplift. The deal closed roughly 24 percent below the migration quote.
The case study is anonymised. It is based on real enterprise renewal engagements, with the client profile, estate and figures presented as plausible and internally consistent ranges rather than naming any organisation.
The 2026 model replaced five legacy tiers with Foundation, Advanced and Prime, so every line needs a new mapping. Vendors tend to map conservatively toward the top tier, which charges for headroom most workflows never use, so a per workflow mapping is where the saving sits.
No. All figures are typical negotiated ranges based on benchmark observations across real enterprise renewals, used as internal leverage rather than published as official list prices.
Your renewal