OBLYTECH Logo
OBLYTECH Logo
ServiceNow Upgrade Readiness: Licensing and Cost Factors to Plan For

ServiceNow Upgrade Readiness: Licensing and Cost Factors to Plan For

Licensing Changes and Support Expectations During Upgrades

ServiceNow releases new platform versions multiple times per year. Support depends on which releases the vendor currently supports, so confirm the supported release list with the vendor before planning an upgrade schedule. Licensing cost usually moves with what the subscription entitles you to use, not with the release number alone, so reconcile entitlement before you price any upgrade. Older versions may receive limited or no support. Remaining on supported versions is important for security patches and bug fixes. Licensing alignment with support expectations shapes upgrade frequency and cost: organisations requiring latest features upgrade frequently; organisations prioritising stability may upgrade less often.

When you upgrade, some capabilities may require new licensing or license tier increases. New modules introduced in releases may not be available in your current license. Calculate upgrade cost including any license changes before committing to an upgrade schedule. Some organisations use release readiness assessments to evaluate upgrade impact; budgeting for these assessments helps identify cost surprises early.

Customisation Review and Deprecation Risk

Custom code may not be compatible with new releases. ServiceNow deprecates functionality over time; code that relies on deprecated APIs may stop working. Reviewing all custom code for compatibility before upgrade prevents post-upgrade failures. This review takes time and effort proportional to customisation volume. Organisations with heavy customisation spend significant effort on upgrades; organisations with light customisation may upgrade in days.

An upgrade can conflict with customisations: the upgrade process skips changes to objects that have been customised, and the platform records those skipped changes for review. Custom scripts may need rewriting after an upgrade. Test customisation thoroughly in non-production environments before production upgrade. Budget time for scripting changes and testing; don’t assume customisation will work unchanged in new releases.

Environment Upgrade Sequencing and Downtime Planning

Test the upgrade on non-production instances first and fix the defects found there before the production upgrade. Each environment upgrade takes time and requires validation afterward. Schedule production upgrades in a change window, ideally after hours, to limit the impact on users. Budget for maintenance window impact: financial services, hospitals, and other 24/7 operations may require planning around business cycles to minimise downtime impact.

Upgrade time varies by environment size and customisation. Small, lightly customised instances usually upgrade faster than large, heavily customised ones, so time a rehearsal rather than assuming a duration. Rehearse the upgrade on a sub-production instance cloned from production to estimate time and identify issues.

Data and Configuration Validation Post-Upgrade

After each environment upgrade, validate that data migrated correctly and functionality works as expected. This validation requires testing multiple scenarios: standard processes, edge cases, integration functionality, report generation, and user-facing features. Validation effort scales with configuration complexity. Budget post-upgrade testing equally to upgrade execution time; don’t assume upgrade is complete when the system restarts.

Planning for Unexpected Issues and Support Costs

Upgrades occasionally surface unexpected issues: custom functionality that breaks in ways not caught during testing, integrations that behave differently, performance degradation in certain scenarios. Allocate support resources for the first weeks post-upgrade to handle issues quickly. ServiceNow Support is available to assist. Internal teams should be prepared to troubleshoot and potentially rollback if critical issues occur.

Budget for post-upgrade support and issue remediation. The first weeks after a production upgrade often reveal issues in customisation or integrations that weren’t caught during testing. Allocate resources for quick troubleshooting and potential rollback if critical issues occur. Ask the vendor account team whether any additional support arrangement applies to your subscription before relying on one.

Cost Planning Questions for Upgrade Budgeting

What is your current platform version and what release cadence is realistic for your organisation? Frequent upgraders have upgrade costs built into the budget; infrequent upgraders face larger costs when they finally upgrade due to accumulated changes. How heavily customised is your instance? Light customisation means quick upgrades; heavy customisation means significant review and testing. How risk-averse is your organisation? Risk-averse organisations invest heavily in testing and validation; risk-tolerant organisations upgrade faster with less validation.

Integration Testing and Third-Party Tool Compatibility

Upgrades may affect integrations with third-party tools and systems. If you use middleware platforms, reporting tools, or custom integrations, validate that they remain compatible with the upgraded platform version. Some third-party tools may need updates themselves before they work reliably with new platform versions. Budget for integration testing and potential third-party tool updates as part of upgrade planning. Don’t assume integrations will continue working without validation.

Start with an entitlement check, not a price quote

Many licensing surprises during an upgrade come from a gap between what the subscription says it covers and what the team assumes it covers. Before anyone asks what an upgrade will cost, the person accountable for the subscription should be able to answer three questions in writing: which applications and plugins the subscription entitles you to use, which of those are already activated on each instance, and which non-production instances sit under the same agreement. Those answers are rarely held in one place. The contract lists products, the vendor account team holds the entitlement record, and the instance shows what is switched on. Reconciling the three is the real first task, and it often takes longer than the upgrade planning that follows.

The reason this matters is that an upgrade rarely adds a single line item. It can change which application versions are supported on a given platform release, retire something that was bundled into an earlier tier, or introduce a dependency the team only finds when a plugin refuses to activate. A team that has priced only the platform subscription is often caught out by the application it forgot to inventory.

Separating platform cost from application cost

Treat the platform subscription and each application as separate cost lines. The platform cost moves on the renewal schedule and is governed by the contract. Application and plugin costs move when you activate something new, when a capability is bundled into a newer release, or when usage crosses a boundary your agreement defines. Keeping them apart stops the finance conversation from collapsing into one number nobody can explain.

Cost line Where it usually comes from Question to settle before committing
Platform subscription The agreement and its renewal terms Does the current term run past the planned cutover, and does the target release fall under the existing support tier?
Applications already in use Entitlement record cross-checked against active plugins Is each active application still entitled in the target release, or does the agreement need a change first?
Newly exposed capabilities Release content that depends on an add-on or a higher tier Does the team intend to switch on anything new, and is that switch itself a licensing event?
Non-production instances Sub-production and test allocations How many copies are needed to rehearse the upgrade, and are they covered without extra charge?
Testing and partner effort Services purchased and internal staff hours Who carries the cost of compatibility work, and is it in the budget or assumed away?

The final row is the line that finance tends to find missing. Compatibility testing is a real licensing-adjacent cost, and it draws on the same sub-production capacity and skilled hours that would otherwise go to new work, so the upgrade planning and operational continuity article is a useful companion read. Putting it on the sheet makes the business case honest, and it is the figure that tends to move a decision when finance reviews the request.

An ordered procedure for building the licensing case

The sequence below keeps the work in an order that avoids re-doing estimates. The questions in the requirements workshop question set are a good place to surface the same entitlement issues with the people who own the business side. Each step produces a record that someone else can check without asking you what you meant.

  1. Export the list of active applications and plugins from every production and non-production instance, including their versions.
  2. Match each item against the entitlement record and flag anything that is active but not clearly entitled.
  3. Ask the vendor account team how each flagged item is treated in the target release, and keep the answer in writing.
  4. List every capability the business wants to enable after the upgrade and price it as a separate decision, not as part of the upgrade.
  5. Count the sub-production copies needed for rehearsal and confirm the allocation before the first clone is made.
  6. Tag each cost line as contracted, confirmed in writing, or assumed. Only the first two should carry a firm figure in the business case.

Where licensing plans usually break

  • An application is active on the instance, so it is assumed to be licensed. Activation and entitlement are different facts, and a licensing review usually separates them quickly.
  • A newly released feature is tried in testing, then switched on in production, and only then does the team realise it sits outside the agreement.
  • The team clones production several times for testing and uses up more sub-production capacity than the allocation was meant to cover.
  • The licensing question is held by one person who leaves before renewal, and nobody else knows which assumptions were agreed informally on calls.

When waiting is the cheaper answer

Licensing can argue for delay. If the release you would move to adds nothing your entitlement lets you use, and the cost of testing a large set of customizations is high, a later upgrade may be the right decision. That is a sound position when the reason is written down and revisited at renewal. It becomes a problem when the reason is simply that nobody has checked. Teams that defer for this reason often repeat mistakes listed in the common upgrade mistakes guide. Waiting has its own cost in support coverage, because older releases eventually fall outside what the vendor will help with, so the deferral should carry a review point at which the decision is made again.

Questions teams ask about upgrade licensing

Does an upgrade always change what we pay?

Not necessarily. An upgrade that keeps the same applications, the same tier and the same instance count often leaves the subscription unchanged. The change arrives when the target release or the target configuration moves something outside the existing agreement. The most reliable answer comes from comparing the entitlement record with the configuration you intend to run afterwards.

Who should own the licensing question inside the project?

Give it to a named person who sits between the platform owner and finance, and have that person sign off each cost line. Leaving it with the technical lead usually produces an accurate inventory and a vague commercial conclusion.

Can we keep an unused plugin so we avoid a licensing conversation?

You can, but an inactive or unused application still appears in the inventory and can be activated from the All Applications list. Plugins that are already activated cannot be turned off, so for those the reconciliation has to cover the entitlement itself.

What evidence should we keep for the licensing decision?

Keep the exported inventory, the readiness records kept alongside the upgrades and release readiness overview, the written vendor responses, the tagged cost case and the date each assumption was confirmed. When the agreement renews, that record tells the next owner what was agreed rather than what somebody remembered.

ServiceNow upgrade licensing: menus, names and values to check

An upgrade usually changes licence cost when it changes what your agreement covers or what you use. The deciding fact is that the subscription agreement, not the release number, sets entitlement, so compare the plugins and applications on each instance with that agreement before estimating any upgrade or renewal adjustment.

Confirm the names and menu paths below on your own instance and release before relying on them, because labels and defaults change.

Name What it lists Use it to
All Applications list Plugins on the instance See which are active and compare each against your agreement
Application Manager Licensed applications and plugins on the instance Review each licensed application and plugin against your agreement
Upgrade History module Earlier upgrade runs Estimate how long a rehearsal may take

Example (hypothetical): a finance lead asks why the renewal adjustment differs from last year. An administrator opens Application Manager, lists each licensed application and plugin, then marks each line as entitled, not entitled or unknown. Only the unknown lines go to the vendor account team, so the conversation covers a handful of items rather than the whole estate.

Feed that list into the upgrade and release readiness guides and the testing and acceptance checklist, and see platform upgrades and enhancements for how the work is run.

Which instance should I check first for licensing?

Start with production, because it shows what is genuinely in use. Then compare the sub-production copies, which can carry plugins that were activated for testing and never removed. Differences between them are the first items to explain before an upgrade estimate is trusted.

Is a custom application counted the same way as a store application?

Not necessarily. Custom applications you build are your own work, while store and vendor applications may be tied to entitlements. Ask the vendor account team how each category is treated in your agreement rather than assuming a single rule.

How do I estimate the effort for a rehearsal upgrade?

Use the Upgrade History module’s record of earlier runs as a starting reference, then repeat the upgrade on a clone and time it. The clone result is more reliable than any earlier run, because the data volume and customisation will have changed since then.

Turning the licensing case into a go, defer or fix-first decision

The licensing case is only useful if it ends in one of three decisions: upgrade on the planned date, defer with a named trigger, or fix the entitlement gap before anything else. Put that decision in writing before anyone books a rehearsal clone, because rehearsal time is wasted when the case behind it is weak.

Go ahead when every active application and plugin on production is marked entitled in the target release, each non-production copy has a matching allocation, and every cost line still marked assumed has been confirmed in writing. The remaining risk is then technical. If the technical side is still uncertain, a platform performance and upgrade readiness review is the natural next step before the schedule is fixed.

Defer when any active item is entitled only in the current release, or when the vendor account team has not answered how it is treated after the upgrade. A deferral needs a date, an owner and a trigger that reopens the case, such as a renewal date, the end of a support window or a feature the business can now justify paying for. Without a trigger, a deferral quietly becomes the default.

Fix first when the gap is small and tied to specific items. Where the platform allows it, restrict access to plugin features nobody uses through roles and ACLs, because an activated plugin cannot be deactivated; confirm entitlement for the rest and take the decision again. Teams that want a wider view of unused entitlements can start with the ServiceNow software license optimization guide. If the gap sits in Integration Hub, the Integration Hub licensing and cost factors guide covers that case directly.

Decision Use it when Record before acting
Go Every active item is entitled in the target release and each copy has an allocation Confirmed cost lines and the rehearsal schedule
Defer An item is entitled only in the current release, or the vendor answer is missing Review date, owner and the trigger that reopens the case
Fix first The gap is small and tied to named plugins or applications List of features to restrict by role or ACL, and the entitlement answer for each item that remains

Review the decision at every renewal and after each upgrade. The first answer is rarely the last one, and a record showing which assumptions held is what makes the next estimate faster and easier to defend.

Frequently asked questions

How often should we upgrade ServiceNow?

Upgrade cadence varies widely between organisations. Staying close to current releases is recommended for security and support. Upgrading more frequently increases costs but reduces per-upgrade effort (smaller changes). Upgrading less frequently defers costs but creates larger upgrades with higher risk. Choose a cadence your organisation can sustain.

Can we skip releases and jump multiple versions ahead?

Possible but risky. Skipping releases means skipping deprecation warnings—code working in skipped releases may break in the version you're jumping to. Upgrade to each sequential release or test thoroughly if you skip releases. ServiceNow supports moving directly to the latest release family and expects you to review the release notes for every family you skip.

What happens if an upgrade breaks critical customisation?

A move to a new release family cannot be rolled back. Only an update within the same family can be reversed, through ServiceNow support and only inside a short window after it is applied. For a family upgrade the realistic options are fixing forward quickly or, as a last resort, asking support for a point-in-time restore, which costs downtime and data. This adds time but prevents prolonged outages running broken code. Test all customisation in non-production before production upgrade to avoid this scenario. If testing isn't thorough, budget time for rollback and remediation.

Talk to Oblytech

Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.

Contact us