The Complete ServiceNow Upgrade Planning Checklist (Xanadu to Yokohama Edition)

Why ServiceNow Upgrades Require Serious Planning

ServiceNow releases two major versions per year, and staying current is not optional — it is a business requirement. Older versions lose support, miss critical security patches, and cannot access new features that your competitors are already using. But a poorly planned upgrade can break integrations, disable customizations, and disrupt business processes for weeks.

After managing 30+ ServiceNow upgrades across enterprise environments, we have developed a comprehensive checklist that prevents surprises. Whether you are moving from Xanadu to Yokohama or catching up on multiple skipped versions, this checklist covers every phase.

Phase 1: Pre-Upgrade Assessment (2-4 Weeks Before)

Skipped Version Analysis

If you are skipping versions, review the release notes for every intermediate version. Each version may deprecate features, change APIs, or modify default behaviors. Create a matrix of breaking changes and map them against your customizations. Missing a deprecation notice is the number one cause of post-upgrade failures.

Customization Inventory

Generate a complete list of all customized out-of-box records using the Instance Scan or the sys_update_xml table. For each customization, determine: Is it still needed? Does it conflict with changes in the target version? Can it be replaced with a new platform feature? Document this in a spreadsheet with columns for record type, table, current behavior, and upgrade risk level.

Plugin Compatibility Check

Review all activated plugins against the target version’s compatibility matrix (available in ServiceNow’s product documentation). Some plugins require separate upgrades, some are deprecated, and some are replaced by new offerings. Contact ServiceNow support or your account manager for plugins that are not listed in the compatibility matrix.

Integration Audit

List every inbound and outbound integration. For each, verify: Does it use APIs that are changing in the target version? Are there authentication changes? Are there data model changes that affect field mappings? Test each integration in a sub-production environment before touching production.

Performance Baseline

Document current performance metrics — page load times, transaction response times, slow query counts, and scheduled job durations. You need this baseline to identify performance regressions after the upgrade. If you do not measure before, you cannot prove whether a post-upgrade issue is new or pre-existing.

Phase 2: Environment Preparation (1-2 Weeks Before)

Clone Production to Sub-Production

Start with a fresh clone of production in your test or development environment. Do not upgrade an environment that has been drifting from production for months — you need a realistic representation of what production looks like today.

Backup Verification

Verify that your backup process is working and that you can restore from it. If you are hosted on ServiceNow’s cloud, confirm your instance backup schedule with ServiceNow support. If you are on-premise (rare but still exists), test your restore procedure end to end.

Rollback Plan

Document the exact steps for rolling back the upgrade if critical issues are discovered post-upgrade. Include: who has authority to trigger a rollback, what the time window is (typically 24-48 hours), and what data will be lost if you roll back (any records created after the upgrade). A rollback plan that has never been tested is not a plan — it is a wish.

Communication Plan

Notify all stakeholders: IT teams, business users, integration partners, and management. Include the upgrade window, expected downtime, what users should expect immediately after the upgrade (slower performance during indexing, UI changes), and who to contact if they encounter issues.

Phase 3: Upgrade Execution

Run the Upgrade in Sub-Production First

Never upgrade production first. Run the upgrade on your cloned test environment, resolve all issues, and document the resolution steps. Then run it again on a second environment to verify your fixes work cleanly. Only proceed to production after two successful sub-production upgrades.

Execute During Low-Usage Window

Schedule the production upgrade during your lowest-usage period — typically weekends or late nights. The upgrade itself may take 2-8 hours depending on instance size, plus additional time for post-upgrade validation.

Monitor the Upgrade Process

Watch the upgrade log in real time. ServiceNow provides detailed logging during the upgrade process. Pay attention to warnings about skipped records, failed plugin activations, and data migration issues. Document everything — the upgrade log will be your primary reference for troubleshooting.

Phase 4: Post-Upgrade Validation (1-2 Weeks After)

Smoke Testing

Run your critical business processes end to end immediately after the upgrade. This includes: creating and resolving an incident, submitting and approving a change request, running a discovery scan, executing your most important flows, and verifying that all integrations are sending and receiving data correctly.

Performance Comparison

Compare current performance metrics against your pre-upgrade baseline. Some performance degradation is normal immediately after an upgrade (indexing, cache rebuilding) and should resolve within 24-48 hours. If performance is still degraded after 48 hours, investigate specific transactions using the Transaction Log.

User Acceptance Testing

Have key business users test their workflows. Technical testing catches configuration issues; user testing catches usability issues. Allocate at least one week for UAT before declaring the upgrade successful.

Instance Scan Post-Upgrade

Run Instance Scan again after the upgrade. Compare results with your pre-upgrade scan. New findings may indicate customizations that need adjustment for the new version. Resolve critical findings before moving on.

Need Upgrade Support?

ServiceNow upgrades do not have to be stressful. Milic Media has managed 30+ enterprise upgrades — from routine single-version jumps to complex multi-version catch-ups. We handle the assessment, planning, execution, and validation so your team can focus on their day jobs.

Book a free upgrade planning consultation and we will assess your upgrade scope, identify risks, and give you a realistic timeline and budget.