A ServiceNow government tier migration case study.

How the ServiceNow government tier migration case study unfolded

A central government department running ServiceNow across internal IT services and operational workflows reached renewal at the same moment the vendor moved every customer onto the 2026 Foundation, Advanced and Prime model. The account team presented a clean and simple proposal: migrate the entire legacy Enterprise and Enterprise Plus estate to Prime, the top tier, on a new four year term. The proposal was framed as the natural home for a department of this size. We were brought in buyer side to test that framing against real usage and benchmark data from real enterprise renewals before the migration quote set the anchor.

The situation

The department had accumulated legacy entitlements across two contract terms, with most users sitting on Enterprise and a smaller group on Enterprise Plus. The wholesale move to Prime carried three things in one number: the tier upgrade itself, a large bundled allowance of metered AI assists, and a standard annual uplift. Public sector budgets are approved in advance on fixed cycles, so an oversized commitment is not just a price problem, it is capital locked away from other priorities for four years. The internal default, with the deadline approaching, was to accept a proposal close to the vendor figure so the platform stayed live.

What we found

A four week usage led assessment told a different story than the migration quote assumed. Only a thin layer of teams, the genuinely advanced and automated workflows, used capabilities that justify Prime. The large majority of users ran standard service workflows that map cleanly to Foundation, with a middle group whose needs were fully met by Advanced. Around 34 percent of users proposed for Prime belonged on Foundation or Advanced once usage rather than legacy entitlement decided the tier. The bundled Prime assist allowance was sized to a vendor forecast well above the department real consumption, and a slice of fulfiller licences had sat dormant in restructured teams for more than six months.

The negotiation

We sequenced the work so volume and tier mix were settled before price. First, a usage led mapping that placed most users on Foundation, a defined group on Advanced, and only the genuinely advanced teams on Prime, reversing the wholesale upgrade. Second, a right sized fulfiller request that removed the dormant licences with a defined resize right for future programmes. Third, a Now Assist allowance rebuilt from the department real consumption pattern rather than the vendor forecast, with the overage rate fixed at signature. Fourth, a capped annual uplift stated as a number across the term. The mechanics behind the mapping are set out in our ServiceNow Foundation Advanced Prime guidance.

The department contracting officers led every conversation, as public procurement rules require. We stayed behind the table, reviewing each proposal revision, drafting counters and briefing leadership before each session, in the pattern set out in our ServiceNow renewal negotiation service. The approach mirrors the one in our technology sector tier migration engagement and the broader ServiceNow renewal method.

The outcome

The agreement signed inside the appropriation window. Around 34 percent of the users proposed for Prime were remapped to Foundation or Advanced, the assist allowance was rebuilt to real consumption with a fixed overage rate, and the annual uplift was capped as a number across the four year term. In total the renewal closed roughly 22 percent below the initial Prime migration quote, saving the department in the region of 3.1 million dollars over the term, capital it redirected to delivery rather than shelfware. The tier discipline echoes our mining sector tier migration work.

Lessons

Three lessons carry beyond this engagement. A wholesale tier migration is several decisions wearing one number, and the value sits in unbundling the tier, the assist allowance and the uplift. The right tier is the lowest one that covers the capabilities a team actually uses, so a blended estate almost always beats a single tier for everyone. And a metered assist allowance is only worth what you consume, so it must be sized from a real consumption model rather than a vendor forecast.