Upgrade to the Australia release

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Upgrade to the Australia release

    Upgrading to the Australia release involves a structured approach to ensure a successful transition. This process requires thorough planning, testing, and validation across various phases, particularly focusing on non-production instances before updating the production environment.

    Show full answer Show less

    Key Features

    • Phase 1: Read the release notes to understand upgrade and migration tasks.
    • Phase 2: Clone your production instance to a non-production environment to assess upgrade duration.
    • Phase 3: Verify configurations and schedule the upgrade using Now Support.
    • Phase 4: Monitor the upgrade process, address skipped records, and conduct functional testing.
    • Phase 5: Upgrade other non-production instances and apply necessary post-upgrade changes.
    • Phase 6: Prepare the production instance for upgrade after refining the test environment.
    • Phase 7: Execute the production upgrade, validate completion, and conduct user acceptance testing.

    Key Outcomes

    By following these phases, you will ensure a smooth upgrade process, minimize risks, and enhance the stability and functionality of your ServiceNow instance. This approach allows you to validate changes thoroughly before affecting the production environment, ultimately leading to improved service delivery and user satisfaction.

    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.

    Release notes

    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.

    Upgrade checklist

    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.

    Calendar with an upgrade date

    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.

    Upgrade progress screen

    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.

    Upgrade other instances

    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.

    Upgrade checklist

    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.

    Upgrade progress screen

    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).