Most ServiceNow upgrade incidents are preventable. The checklist below covers the key pre-upgrade, cutover, and post-upgrade steps that keep implementations on track. Whether you’re moving to a new release family or applying a patch, a structured approach reduces risk before the upgrade window opens.
Need hands-on support? Explore Pathways’ ServiceNow upgrade services.
What should be on your pre-upgrade checklist?
Start these steps two to four weeks before your scheduled cutover:
- Run the Upgrade Preview in sub-production to flag skipped customizations and deprecated API usage.
- Read over the release notes for the release that you are about to upgrade to
- Confirm MID Server versions are compatible with the target release.
- Audit active integrations (REST, SOAP, JDBC) and verify API versions are supported post-upgrade.
- Clone over your sub production instances but always make sure to back up any in-progress work before doing so!
- Execute ATF regression tests, manual testing, and complete UAT sign-off with business process owners.
- Notify stakeholders of the upgrade window, expected downtime, and support contacts.
What should a cutover runbook include?
A cutover runbook assigns a named owner, estimated duration, and go/no-go criteria to every task. The core phases:
T-48 hours: Freeze non-emergency changes. Complete final ATF run in sub-production. Confirm rollback criteria.
T-4 hours: Notify stakeholders. Create a production snapshot.
T-0: Initiate upgrade from the Upgrade Center. Monitor logs in real time.
T+1 hour: Execute smoke testing in Production once the upgrade is complete. Confirm integrations are responding. Validate core workflows before releasing to users.
How should rollback be planned?
Define rollback triggers and a hard deadline before the upgrade window opens. Assign a single decision-maker. Note that ServiceNow does not support native rollback after an upgrade commits, so your options depend on snapshot availability and cloning strategy. Confirm this with your delivery team in advance.
What happens after the upgrade?
- Resolve any skipped customizations flagged in the upgrade log.
- Confirm integrations are processing data correctly.
- Monitor error logs daily for the first week and route upgrade-related tickets through a dedicated tag.
- Promote any update set fixes required during the initial upgrade testing
- Close the change record with documented outcomes and lessons learned.
Learn about ongoing ServiceNow support services from Pathways.
What does a realistic upgrade timeline look like?
Weeks 1 to 2: Upgrade Preview, skipped customization review, remediation planning.
Weeks 3 to 4: ATF and manual regression testing, integration smoke tests, UAT.
Week 5: Stakeholder communication, runbook finalization, CAB approval.
Week 6: Cutover execution and go/no-go decision.
Week 7: Stabilization, issue resolution, change record closure.
Patch upgrades can compress this to three to four weeks. Instances with heavy customization or HRSD and SPM complexity may need eight or more.
