OBLYTECH Logo
OBLYTECH Logo

ServiceNow Releases Explained: How Upgrades Are Planned

The ServiceNow release cycle is the vendor’s planned sequence of platform releases, patches and hotfixes, and each instance moves to a newer release through an upgrade. Planning well means knowing which release your instance runs, how far behind the newest release you are willing to stay, and what has to be checked before and after each move. This guide covers each of those points in plain terms.

How the ServiceNow release cycle works

Each major release bundles platform changes into one package, and releases carry names that identify their family. Between releases the vendor publishes patches and hotfixes. A patch collects fixes for defects and security issues, while a hotfix carries fixes for a specific set of problems and ships between patches.

The number of releases published in a year changes over time, so avoid planning around a fixed count. Check which versions your own instance shows as available to upgrade to.

Finding the release your instance runs on

Your instance records the release it is running, and administrators can read it from within the instance. Note the version together with the instance name and the date you checked it. Support requests and upgrade discussions depend on that record, and it is easy to lose track of once several instances exist.

The version also tells you which release family your instance belongs to. Check the release notes for that version rather than relying on memory, because they describe the changes and fixes that apply to it. Look for it on your own instance rather than following an old screenshot.

Deciding how far behind the newest release to stay

No single answer fits every organisation. Staying close to the newest release gives you new platform features and fixes sooner, but it also means your team is testing against a release that other customers have only recently started using. Staying a step or two back gives your developers time to check customizations and lets early problems surface before you depend on the release.

A common approach is a written rule: for example, schedule the upgrade within a fixed period after a release becomes generally available, and review the rule once a year. The rule matters less than the discipline of applying it. Teams that upgrade only when something breaks usually end up moving several releases at once, which tends to make later upgrades harder. Scheduling and approving the upgrade window is part of change governance, and our release management and change governance service page describes how that work is handled.

Upgrading across several releases in one move

When your instance is several releases behind, the upgrade spans more than one software version, and each version in between can matter. Read the release notes for each version between your current version and the target, not only the target. The notes help you determine whether items you customized are being upgraded.

A practical habit is to keep one list per intermediate version, noting each change and the parts of your instance it touches. If you are weighing the Brazil family, the problem fixes in each patch and hotfix are an important factor. Compare the problem fixes in the release notes for each Brazil version you are considering before you choose the version to move to.

What to review before an upgrade starts

Preparation decides how smooth the upgrade is. Work through the following before you fix the window.

  • Inventory your customizations, scripted logic and integrations, and mark the ones that depend on behaviour the vendor might change.
  • Read the release notes for the target release and list every change that touches an area your team uses.
  • Confirm which plugins and applications are installed and whether each one is supported on the target release.
  • Take a current backup or restore point that meets your own backup policy.
  • Run the upgrade on a non-production copy first and record how long it takes, so you can size the production window.

If your changes move between instances through update set management, check that every set has been applied to the test copy before you start, so the test reflects what production will actually contain. Write the results down. A short list of what changed in the test copy, and who signed off each change, is the document you will need if something goes wrong after go-live.

Scheduling and following an upgrade in Upgrade Monitor

Upgrade Monitor is the Upgrade Center module where you schedule an upgrade on an instance and follow it while it runs. When no upgrade is in progress, go to All, then Upgrade Center, then Upgrade Monitor. The module covers one part of the larger process, which also includes cloning, testing and importing update sets.

If you log in with the admin role while an upgrade is running, the progress screen opens automatically. When the upgrade finishes, the Upgrade Summary Report lists conflicts between your customizations and the upgrade, with a link to reconcile them. On a non-production copy, the same report helps you estimate how long the production upgrade might take.

Working through skipped records on the first upgrade

The first non-production upgrade is where customization conflicts get resolved. The system skips the records you have customized so your changes are not overwritten, and it lists those records for review. Work through them in the Skipped Changes to Review related list on that instance.

The changes you make while working through the list are recorded in update sets. Later instances do not need the same reconciliation: apply the upgrade, then import those update sets. Teams that leave the list until production tend to meet the conflicts at the worst moment. The common release readiness mistakes guide makes the same point about deferring risk items until after go-live.

What to check after the upgrade

Testing does not end when the upgrade job reports success. Run the processes the business depends on most first, such as approvals, incident routing and any integration that sends or receives data. Compare the results with the expected outcomes you recorded before the upgrade, not with what you remember.

Keep watching the logs and scheduled background jobs for several days. Errors that appear under normal daily load are common, and they are far cheaper to fix in the first week than after the team has built new work on top of a broken change. If an update set fails to apply cleanly after the move, the troubleshooting guide for update sets covers the problems that usually cause it. Slow pages after an upgrade often have a performance cause, and the platform performance guides show where to look first.

Why some upgrades take much longer than others

The biggest factor is how far your instance differs from a standard setup. Heavily customized instances have more places where a platform change can break existing behaviour. Custom code that relies on internal details rather than documented interfaces is a frequent source of surprises.

Integrations are the second area to watch. An external system that expects a particular response format or timing can fail quietly after an upgrade. Plugins and applications need their own compatibility check, and a plugin that lags behind the platform can hold up an otherwise ready upgrade. Our upgrade readiness service page covers this kind of assessment if your team wants outside help with it.

For the wider set of guides on this topic, see the upgrades and release readiness guides.

Frequently asked questions about ServiceNow releases

What is the difference between a release, a patch and a hotfix?

A release is the larger platform package that adds features and changes behaviour. A patch collects fixes for defects and security issues, and a hotfix addresses one specific problem between patches. Read the release notes for each one before you decide whether to apply it.

How do I find out which release my instance is on?

Administrators can read the release version from within the instance. Record it with the instance name and the date, then review the release notes for the versions you are considering.

Should every instance upgrade to the newest release?

Not necessarily. Choose a lag that your team can test within its own schedule, write the rule down, and review it each year. A heavily customized instance usually needs a longer test period than a lightly configured one.

How much testing does an upgrade need?

Enough to cover the processes the business depends on, plus the integrations and custom code those processes use. Measure how long the upgrade takes on the test copy so the production window is realistic, and keep the test notes for the next upgrade.