Clarification on Plugin upgrade versions and compatibility

[anandcristy]

Hi Team,

We are planning to upgrade our instance from Zurich to Australia next month.

I want to confirm the correct process for identifying whether newer plugin versions are required post-upgrade. So that i can prepare the list of plugin needed to upgrade manually.

Thanks.

[meghanakra]

Core ServiceNow plugins usually get upgraded automatically during the family upgrade process. However, Store Applications, Scoped Apps, and IntegrationHub Spokes like Employee Center, Virtual Agent, DocuSign, Teams/Slack integrations, and HRSD packages often need separate validation and manual upgrades after the family upgrade because they follow independent release cycles and may have compatibility dependencies.

Before starting the upgrade, it is recommended to document all installed plugins, Store apps, spokes, and custom scoped applications along with their versions, customizations, and business criticality. After the upgrade in sub-production, check System Applications → All Available Applications or the ServiceNow Store to identify any available updates, compatibility changes, or dependency upgrades. Many Store apps are not automatically updated during family upgrades, so manual upgrade, testing, and version validation are usually required.

[Ankur Bawiskar]

@anandcristy 

you won't require any new plugin unless your customer asks you to install that as part of upgrade

New plugin has no dependency on upgrade

check this blog

Upgrade Resources 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏