ServiceNow Upgrade Planning – Xanadu vs. Australia

[maximepalmier]

Hello,

As part of our ServiceNow instance management, I would like to request guidance regarding the upcoming upgrades:

• Should we plan to upgrade to Xanadu by the end of 2025,

• or would it be more advisable to wait directly for the release of Australia?

The objective is to ensure platform stability while benefiting from the latest features and security updates, and to avoid back-to-back upgrades if not required.

Thank you in advance for your advice and recommendations.

Best regards,

[Nikhil Bajaj9]

Hi @maximepalmier ,

Every organization have their own policies to have N-1 (1 version below the latest one as latest versions have bugs ex:- Zurich is latest so Yokohama) or N-2 (2 Down versions as those are stable) so you need to check what is the policy over there in your organization. If you are planning to upgrade by the end of 2025 then you can also plan for Zurich version. Most of the organization is upgrading once a year not every 6 months so mostly no one is going fgor back to back upgrades. We are also planning to upgrade to Zurich by the end of 2025, we are also upgrading once a year. 

[SebastianR99694]

On which version are your instances right now? Are you sure that you are not on Xanadu already?

Xanadu is currently the last supported release but will be go out of N-1 Support with the Zurich Release this week.

If you are on Xanadu you should definitely upgrade to Yokohama/Zurich depending on your support contract (normally N-1 is supported, some customers have N-2 releases support).

[AbinC]

Hi @maximepalmier ,

When considering software upgrades, especially for platforms like ServiceNow, it's important to align with your organization's policies regarding version management. Here are some key points to consider:

Version Management Policies

1. N-1 or N-2 Strategy:

   • N-1: This strategy involves using one version below the latest release. It allows organizations to avoid potential bugs or issues that might be present in the newest version.
   • N-2: This involves using two versions below the latest release, often chosen for stability, as these versions have been tested and patched over time.

2. Organizational Policy:

   • Check with your IT department or ServiceNow administrator to understand the specific version management policy in your organization.
   • Policies may vary based on the organization's risk tolerance, resource availability for testing, and the criticality of the systems involved.

3. Upgrade Planning:

   • If planning an upgrade by the end of 2025, consider the Zurich version or whatever stable version is recommended at that time.
   • Most organizations opt for annual upgrades rather than every six months to allow sufficient time for testing and adaptation.

Best Practices for Upgrades

• Testing: Thoroughly test new versions in a sandbox or development environment before deploying them in production.
• Documentation: Review release notes and documentation to understand new features and potential impacts.
• Training: Ensure users are trained on any changes or new functionalities introduced by the upgrade.

Encouragement for Feedback

If you find this guidance helpful, acknowledging the effort by marking it as a solution and helpful  can be motivating for those providing support. It also helps others identify useful answers in community forums.

If you have more questions or need further assistance, feel free to ask!

[Dr Atul G- LNG]

Hi @maximepalmier 

The upgrade depends entirely on the needs and nature of your business.
If you believe that the new features in Xanadu could be helpful, you can try them out in the client first and then consider updating.

According to the latest SN release cycle, if you're able to wait until mid-next year, then going for Austral might be a better option. Otherwise, Xanadu is also a solid upgrade choice for now.