Backup of instances before upcoming Release Update

[LutzS]

Hi Everyone,

We are currently preparing for an upcoming ServiceNow Release Update across our instance landscape (Dev, Test, Stage, and Prod).

To ensure we are fully covered in terms of data integrity, custom configurations, and disaster recovery, I am looking for a structured "cookbook" or step-by-step best practice guide on how to safely back up all instances before kicking off the upgrade process.

Specifically, I would appreciate insights or existing guides on:

• Platform vs. Application Level: The recommended process for verifying ServiceNow Platform Backups via Now Support (HI) versus manually backing up application-level deltas (Update Sets, Git repository tags, Scoped Apps).

• Pre-Upgrade Safeguards: Best practices for locking down developments (Code Freeze), capturing skipped update logs, and setting up target-state clones on sub-production instances.

• Rollback & Recovery: Proven strategies for handling rollbacks or applying delta recoveries in case critical customizations are overwritten or post-upgrade issues arise.

• Post-Upgrade Checklist: Key validation steps (e.g., ATF runs, Smoke Testing, Skipped Changes Review) before signing off on the instance.

If anyone has a playbook, checklist template, or recommended community resources they use internally for release upgrades, I would be very grateful if you could share!

Thanks in advance for your support!

Best regards, L

[Hemanth M]

Hi @LutzS ,

ServiceNow has inbuilt guided set up for this (with tools) - have you explored upgrade console yet?

Navigation - Admin Center > Upgrade Console

Additionally you can refer this comprehensive guide here - https://www.servicenow.com/docs/r/platform-administration/upgrade-center/uc-landing-page.html 

Hope this helps

[LutzS]

Hi Hemanth,
thanks for your help. I will try that and come back with feedback.
Have a nice day
Lutz