ServiceNow Brazil is open to every customer: what should you check before upgrading from Zurich or Yokohama?

Brazil Patch 2 shipped on November 5, 2026 and is the first Brazil version any ServiceNow customer can upgrade to. Here is what to check first if you are coming from Australia, Zurich or Yokohama.

Quick Answer

As of November 8, 2026, yes. ServiceNow's available versions page lists Brazil Patch 2, released November 5, 2026, as Available, which it defines as "any user can upgrade to the version." ServiceNow publishes upgrade notes for moving to Brazil from Australia, Zurich and Yokohama. Preview the upgrade, test it on a clone, then plan time for skipped records.

Key takeaways

  • Brazil Patch 2, released November 5, 2026, is the first Brazil version that ServiceNow's available versions page marks as open to any customer.
  • ServiceNow's Brazil release notes offer separate upgrade notes for customers coming from Australia, Zurich and Yokohama.
  • A Yokohama instance that jumps to Brazil picks up the Zurich and Australia changes at the same time, so it needs a longer test plan.
  • Skipped records, the customized records the upgrade did not overwrite, are reviewed in the Upgrade Monitor and must be resolved and retested after the upgrade.
  • If you are not upgrading this quarter, ServiceNow's Q4 2026 patching targets tell you which patch to move your current family to instead.

Planning your Brazil upgrade?

Get a scoped quote for upgrade preparation, clone testing and skipped record cleanup, sized to how far your instance is from the Brazil family today.

Get a Project Quote

Can every ServiceNow customer upgrade to Brazil now?

Yes, from Brazil Patch 2 onward. ServiceNow's available versions page lists Brazil Patch 2 as a patch released on November 5, 2026 with the status Available. Earlier Brazil builds were limited to early availability customers. Available versions show up on the Instance Upgrade Management Dashboard, and you do not need to request an entitlement for them.

A quick vocabulary note. ServiceNow calls each major release a family (Yokohama, Zurich, Australia and now Brazil, named alphabetically and wrapping from Zurich back to A). Inside a family, a patch is a bundle of fixes and a hotfix is a smaller targeted fix on top of a patch. Here is how the Brazil family has opened up, as the available versions page showed it on November 8, 2026:

Brazil versionTypeReleasedStatus on November 8, 2026
Brazil security and notable fixes, All other Brazil fixesFeature Early AvailabilitySeptember 24, 2026Unavailable
Brazil Patch 1PatchOctober 8, 2026Unavailable
Brazil Patch 1 Hotfix 1HotfixOctober 15, 2026Available to Early Availability customers
Brazil Patch 2PatchNovember 5, 2026Available

The Brazil Patch 2 release notes say it includes 348 problem fixes and that ServiceNow recommends customers upgrade to it "for the most secure and up-to-date features." The security fixes are described in Now Support article KB3228372. One exception to watch: the same notes say Brazil is still being evaluated for the ServiceNow Government Community Cloud (GCC), the separate environment for public sector customers. If your instance runs there, Available on the general page does not settle it for you.

Can you upgrade straight from Zurich or Yokohama to Brazil?

ServiceNow's Brazil release notes are built for it. The Brazil family release notes page, updated November 5, 2026, offers three upgrade paths: release notes for upgrading from Australia, from Zurich and from Yokohama. Each path combines every change between your current family and Brazil onto one page per product, so you read one document instead of three.

That matters because admins have been asking. A ServiceNow Community thread opened on December 5, 2025 asked whether a Zurich to Brazil upgrade would be due soon after Brazil shipped, and replies posted in June 2026 were still asking whether a Zurich to Brazil upgrade is possible. When we read it on November 8, 2026, the thread had no official reply. The combined Zurich to Brazil and Yokohama to Brazil notes are the clearest written signal that both starting points are expected.

Two cautions. The combined notes describe what changes, not how long your current family stays supported, so confirm support dates with your account team. And a Yokohama instance moving to Brazil absorbs everything Zurich and Australia changed in one test cycle.

What should you check before you upgrade to Brazil?

Start with a preview, then rehearse the upgrade on a copy of production. The Brazil family page itself recommends three phases in order: learn about the release, prepare your upgrade, then upgrade, and it says to test on non-production instances before production. The checklist below turns that into concrete steps for an admin or platform owner.

  1. Run Upgrade Preview. ServiceNow's Zurich documentation for Upgrade Preview describes a page in the Upgrade Console where you pick a target version from a drop-down and select Go. It shows a skipped list prediction, the applications that will be installed or upgraded with their from and to versions, predicted schema changes, and Automated Test Framework (ATF) pass rates from the last 30 days. An empty drop-down means your instance is not eligible to upgrade to any version yet.
  2. Read the combined notes for your path. Open the Australia, Zurich or Yokohama path on the family page and read the product pages for the applications you actually run. Prioritise the Removed and Deprecations sections.
  3. Clone production to a sub-production instance. Upgrade the clone first. Our guide to cloning ServiceNow instances covers what a clone copies, what it wipes and the cleanup to do afterwards.
  4. Take a health baseline. Run Instance Scan on the clone before and after the upgrade and compare the findings. New findings after the upgrade point at upgrade side effects.
  5. Run your ATF suites. ATF is ServiceNow's built-in test automation. Run the same suites before and after the clone upgrade and investigate every new failure.
  6. Freeze and track in-flight work. Know which update sets are still open and which scoped applications are mid-development, so development changes and upgrade fixes do not tangle together.
  7. Review legacy automation. If you still run legacy Workflow Editor workflows, a family jump is a natural moment to plan migrating them to Flow Designer rather than retesting them yet again.

What changes in the Upgrade Console between Yokohama and Brazil?

The Upgrade Console itself, the screen you plan and run upgrades from, changed in Zurich and Australia but not in Brazil, so how much is new depends on where you start. ServiceNow's combined Yokohama to Brazil notes and combined Zurich to Brazil notes, both updated November 4, 2026, list the following.

FamilyUpgrade Console changeWho meets it during a Brazil upgrade
ZurichNew pre-upgrade step to choose an existing or new upgrade plan; Guided upgrade can also be reached by selecting Resume upgradeYokohama customers
AustraliaBulk application update console to review, select and update multiple applications from one consoleYokohama and Zurich customers
AustraliaApp version compatibility support for AI Suites, updating related applications automaticallyYokohama and Zurich customers
AustraliaAccess to the ATF troubleshooting agent from the Conduct post-testing stepYokohama and Zurich customers
BrazilNo updates for this releaseEveryone

A Yokohama admin will see a different upgrade screen than last time. Walk through plan selection and the bulk application update console on the clone, so nobody meets them for the first time in the production window.

How do you handle skipped records after the Brazil upgrade?

Review every skipped record in the Upgrade Monitor, decide whether to keep, merge or revert it, then retest. ServiceNow's Brazil documentation on processing skipped records says that if you customized a record the upgrade touches, such as a business rule or script, the upgrade generates a skip log record instead of overwriting your version.

  1. Navigate to All > Upgrade Center > Upgrade Monitor.
  2. In the Upgrade Summary Report, select Review changes in the Skipped box.
  3. Work through the Skipped Changes to Review related list and set a resolution on each record.
  4. After the upgrade, test every record you changed. The documentation is direct: "Post-upgrade, thoroughly test all changes you made to these records."
OptionWhat it doesUse it when
Retain as isKeeps your customized record; status becomes Reviewed and RetainedYour change is still needed and the new base version adds nothing you want
MergeCombines your customization with the updated record through Resolve Conflicts; status becomes Reviewed and MergedYou need both your logic and the new base behaviour
Revert to Base SystemReplaces your version with the upgraded baseline and creates a Customer Update record; Reapply Changes can restore it laterThe new release now does what your customization did

Do this on the clone first and capture the resolutions in an update set, so the production upgrade reuses decisions instead of repeating them. If performance changes after the upgrade, our checklist for troubleshooting a slow ServiceNow instance is a good next stop.

Should you upgrade to Brazil now or wait for a later patch?

There is a fair case on both sides. ServiceNow recommends Brazil Patch 2 for the most secure and up-to-date features, and it is the first Brazil build open to everyone. Against that, it is also the first broadly available Brazil patch, and some environments, such as GCC, are still under evaluation. Your support dates and test capacity should decide it.

The case for moving now. The Patch 2 notes carry 348 problem fixes, including security fixes, and ServiceNow recommends upgrading to it. Starting clone testing now also gives you the longest runway before your current family's support ends.

The case for waiting. Teams with thin test coverage, a Yokohama starting point or a GCC instance may prefer to finish preparation first and let a later Brazil patch absorb early fixes. Waiting is not the same as standing still, though. ServiceNow's Q4 2026 patching program targets name the patch to move each current family to:

  • Australia: Australia Patch 5b W44
  • Zurich: Zurich Patch 5a W44
  • Yokohama: Yokohama Patch 13 Hotfix 5a W45

The page notes that targets are subject to change prior to patching, so check it again before you schedule. Either way, the preparation work in the checklist above is the same, and none of it is wasted if you upgrade a quarter later.

Get one practical ServiceNow tip every week

Release changes, upgrade traps and admin shortcuts, explained in plain English for people who run the platform. Free, and you can unsubscribe at any time.

Subscribe to the Newsletter

Frequently asked questions

Is ServiceNow Brazil available to all customers?

Yes. As of November 8, 2026, ServiceNow's available versions page lists Brazil Patch 2, released November 5, 2026, with the status Available, which it defines as any user can upgrade to the version. Earlier Brazil builds were limited to early availability customers, so Patch 2 is the first Brazil version open to everyone.

What is ServiceNow Brazil Patch 2?

Brazil Patch 2 is a patch for the Brazil release family, released on November 5, 2026. Its release notes say it includes 348 problem fixes, including security fixes described in Now Support article KB3228372, and ServiceNow recommends that customers upgrade to it for the most secure and up-to-date features.

Can I upgrade from Yokohama directly to Brazil?

ServiceNow's Brazil family release notes include a path called release notes for upgrading from Yokohama, alongside paths from Zurich and Australia. Those combined notes gather every change between Yokohama and Brazil per product. Confirm your support dates with your account team, and expect a longer test cycle because you inherit two families of changes.

Do I need to request an entitlement to upgrade to Brazil Patch 2?

No. ServiceNow's available versions page says versions marked Available appear on the Instance Upgrade Management Dashboard and that you do not need to request an entitlement for them. Versions marked Available by request are different: those need approval from ServiceNow Customer Service and Support before you can upgrade.

How do I check whether my instance can upgrade to Brazil?

Open Upgrade Preview in the Upgrade Console, choose a target version from the drop-down and select Go. ServiceNow's Zurich documentation says an empty drop-down means your instance is not eligible to upgrade to any version. When a version appears, the preview shows predicted skipped records, application upgrades and schema changes.

Where do I review skipped records after a Brazil upgrade?

Go to All, Upgrade Center, Upgrade Monitor. In the Upgrade Summary Report, select Review changes in the Skipped box and work through the Skipped Changes to Review list. For each record choose retain, merge or revert to base system, then test every changed record after the upgrade, as ServiceNow's Brazil documentation advises.

What changed in the Upgrade Console in Brazil?

Nothing new in Brazil itself. ServiceNow's combined Upgrade Console notes list no updates for the Brazil release. The changes came earlier: Zurich added a plan selection step, and Australia added a bulk application update console and access to the ATF troubleshooting agent. Yokohama customers meet all of these when moving to Brazil.

Which patch should I apply if I am not upgrading to Brazil yet?

ServiceNow's Q4 2026 patching program targets are Australia Patch 5b W44 for Australia, Zurich Patch 5a W44 for Zurich and Yokohama Patch 13 Hotfix 5a W45 for Yokohama. The available versions page says these targets are subject to change prior to patching, so check the page again before scheduling.

Is ServiceNow Brazil available in the Government Community Cloud?

Not confirmed yet. As of November 8, 2026, both the Brazil Patch 2 release notes and the available versions page say the Brazil version is being evaluated for use in the ServiceNow Government Community Cloud. If your instance runs in GCC, check with ServiceNow before planning a Brazil upgrade date.

How should I test a ServiceNow family upgrade before production?

Clone production to a sub-production instance and upgrade the clone first. Run Instance Scan and your Automated Test Framework suites before and after, compare the results, and resolve skipped records on the clone. ServiceNow's Brazil release notes recommend testing on non-production instances before upgrading your production instance.

The ServiceNow admin handbook

The NowSpectrum Administration Handbook covers roles, ACLs, update sets, cloning, and instance governance.

Get the Admin Handbook โ†’
โ† Back to all posts