[object Object]

The ServiceNow N-1 policy makes skip-level upgrades a permanent temptation. Sometimes it is the right call. Often it is the reason the next quarter is on fire. The decision has a clear framework — most teams just skip the framework.

The skip-level rule of thumb

Two consecutive minor upgrades cost roughly 1.4x a single skip-level. The economic case is real. But the testing surface is not 1.4x — it is closer to 1.8x because deprecations and behavior changes from both releases land at once.

Three deal-breakers for skip-level

  1. Custom UI16 or legacy Service Portal widgets you have not refactored. Two release cycles of changes will land together and break things in non-obvious ways.
  2. Inbound Email Actions with custom regex. The parser changed twice in the Washington-to-Yokohama window. You will eat both changes.
  3. More than 25 active scoped apps from the Store. Vendor compatibility windows assume single-step upgrades.

If any of these are true, do two steps.

The prep that makes it boring

Run Upgrade Center on a clone first, with Show all skipped customizations enabled. The skipped count is your real workload — every row is a customization that was overwritten and now needs a manual reconcile decision.

Pre-upgrade clone checklist:
- Latest patch level applied
- Plugin inventory exported
- Active customization count baseline
- ATF suite passing at 100%
- Performance Analytics baseline snapshot

ATF is the upgrade insurance policy

If you do not have an Automated Test Framework suite covering your top 30 business processes, you are not ready for any upgrade — single or skip. Build the suite, gate the upgrade on a green run.

The two-clone strategy

Use one clone for the technical upgrade dry run. Use a second clone, refreshed after the first run completes, for business UAT. Do not collapse them — UAT findings rarely make it back into the technical dry run if you share an instance.

Know the rollback story before you start

Production rollback is not “click rollback.” It is “restore from backup, lose six hours of data.” Plan a true cutover window and confirm leadership accepts the rollback definition in writing.

What to do this week

Run Upgrade Center on a fresh clone against the next release. Count skipped customizations. If the number doubled vs the previous upgrade, you are looking at a skip-level that should be two steps.

[object Object]
Share