Upgrade to the Brazil release

Brazil Release Notes

Release

brazil

ft:locale

en-US

ft:publication_title

Brazil Release Notes

ft:clusterId

bundleId

Upgrade to the Brazil release

Release version: Brazil

Updated September 10, 2026

2 minutes to read

Summarize

Summarized using AI

Summary of Upgrade to the Brazil release

Upgrading your ServiceNow instance to the Brazil release requires careful planning, testing, and validation to ensure a smooth transition. The process involves multiple phases, beginning with understanding the release notes and ending with validating the production upgrade. This structured approach minimizes risk and helps maintain system stability throughout the upgrade.

Show full answer Show less

Upgrade Phases

Phase 1 - Read the release notes and plan your upgrade: Review the Brazil release notes thoroughly to understand upgrade and migration tasks. This is critical for effective planning.
Phase 2 - Prepare for the development instance upgrade: Request a full clone of your production instance to a non-production environment to estimate upgrade duration and confirm current and target versions for scheduling.
Phase 3 - Verify upgrade configurations and schedule upgrade: Check the "Check distribution for possible upgrade" scheduled job to understand its timing and frequency. Schedule your upgrade in Now Support accordingly.
Phase 4 - Upgrade and validate the development instance: Use the Upgrade Monitor to track progress, process skipped records, identify update sets, and perform functional testing in the development instance.
Phase 5 - Upgrade and validate other non-production instances: After refining your development instance, upgrade additional non-production instances like test environments. Apply post-upgrade changes such as activating plugins and applying update sets immediately after upgrade completion.
Phase 6 - Prepare to upgrade the production instance: Ensure your test environment accurately reflects production before preparing the production upgrade.
Phase 7 - Upgrade the production instance: Upgrade the production instance last after successful non-production upgrades. Validate completion, apply update sets and fix scripts, and conduct user acceptance testing (UAT).

Key Outcomes

Minimized production downtime and risk through staged upgrades and thorough testing in non-production environments.
Clear visibility into upgrade progress via the Upgrade Monitor.
Confidence in production upgrade readiness after validating configurations, update sets, and functional testing.
Structured and repeatable upgrade process that aligns with ServiceNow best practices for the Brazil release.

Upgrading and patching your instance requires planning, testing, and validation. To ensure a safe and effective upgrade, read the release notes, create upgrade plans, and test your upgrade on non-production instances before upgrading your production instance.

Important:

These topics contain in-depth explanations about upgrades. For a step-by-step reference of upgrade steps, refer to the Upgrade planning checklist.


	Phase 1 - Read the release notes and plan your upgrade Before you begin the upgrade process, it is essential to read the release notes for your target version so you understand the required upgrade and migration tasks. This information helps you plan a safe and effective upgrade.
	Phase 2 - Prepare for the development instance upgrade For a better understanding of your production upgrade duration, request a full clone of your production instance (including large tables and attachments) onto a non-production instance. Confirm your current and target release versions, because you will later use this information when scheduling your upgrade in Now Support.
	Phase 3 - Verify your upgrade configurations and schedule the development instance upgrade in Now Support Check the configuration of the Check distribution for possible upgrade scheduled job to view how often and when it runs. Review information about timing your upgrade in coordination with the Check distribution for possible upgrade scheduled job. Then, schedule your upgrade in Now Support.
	Phase 4 - Upgrade and validate the development instance Track the progress of your upgrades with the Upgrade Monitor. For your first non-production instance upgrade (your development instance), use the Upgrade Monitor to process the skipped list of records that were not addressed in the upgrade. Then identify your update sets and perform functional testing.
	Phase 5 - If applicable: Upgrade and validate your other non-production instances, such as your test instance After you've configured and refined your development instance, request to upgrade any other non-production instances you have, such as a test instance. Immediately after the upgrade is complete, apply the post-upgrade changes made to your development instance, including activating optional plugins, installing and upgrading applications, and applying update sets.
	Phase 6 - Prepare to upgrade the production instance After you have configured and refined your test environment to be a good representation of your production environment, prepare to upgrade your production instance.
	Phase 7 - Upgrade the production instance After you have upgraded your development, non-production, and test instances, upgrade your production instance last. Then validate that the upgrade was complete, apply update sets and fix scripts, and perform post-upgrade user acceptance testing (UAT).