---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Migration upgrade prerequisites

# Migration upgrade prerequisites {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Before you install the required applications for Security Exposure Management Workspace, review the following information and setup tasks.

## Unified Security Exposure Management overview {#sem-install-prerequisites__section_af4_lfy_hgc}

Unified Security Exposure Management (USEM) introduces a unified foundation across all Vulnerability Response and Security Exposure Management applications. The new architecture consolidates data models, streamlines feature sets, and enhances performance and scalability. However, migrating to USEM is a significant upgrade that requires careful planning, validation, and change management.  
Security Exposure Management supports the following applications:

* Vulnerability Response (infrastructure)
* Application Vulnerability Response
* Container Vulnerability Response
* Configuration Compliance
{#sem-install-prerequisites__ul_o4r_wfy_hgc}

## Prerequisites and notes for upgrade {#sem-install-prerequisites__section_s5n_kgy_hgc}

* You're aware of the significant data model changes and user experience updates outlined in this document.
* Perform the upgrade in a non-critical, non-production instance first and validate the migrated data and any customizations.
* Rollback is not possible once an instance is upgraded to USEM.
* You must deactivate all third-party integrations and verify that no integration runs are underway before upgrade.  
  To deactivate scheduled jobs and scheduled jobs within integration-specific scopes:
  1. Navigate to the Third Party Integration \[sn_sec_int_integration\] table.
  2. Open an integration record.
  3. Locate the integration instances related list and open a record.
  4. Clear the Active flag and save (Update) the record.
  {#sem-install-prerequisites__ol_nfk_g3y_hgc}
* You must deactivate the scheduled jobs and scheduled jobs within integration-specific scopes for the Vulnerability Response, Application Vulnerability Response, Container Vulnerability Response, and Configuration Compliance applications. For a list of scheduled jobs you must deactivate, see [Migration upgrade reference information](https://servicenow-prod.fluidtopics.net/FBdvhgutJ72CihQN1zSCfA "Lists and tables of scheduled jobs, table deprecations, and new columns added to existing tables for migration to Security Exposure Management Workspace.").  
  To deactivate scheduled jobs:
  1. Navigate to AllSystem DefinitionScheduled Jobs.
  2. Open a record.
  3. Clear the Active flag and save (Update) the record.
  {#sem-install-prerequisites__ol_z3y_zny_hgc}
{#sem-install-prerequisites__ul_xwq_mgy_hgc} After you have completed the deactivation of scheduled jobs and third-party integrations, upgrade plugins in sequential order to migrate to USEM. See [Download and activate applications](https://servicenow-prod.fluidtopics.net/MNh4tcKjC8Va239j9W5BWQ "Download the required Security Exposure Management Workspace applications from the ServiceNow Store into your ServiceNow AI Platform and activate them to upgrade.") for more information.

1. Vulnerability Response (This will upgrade all the dependent plugins shown in the flow chart)
2. Configuration Compliance
3. Container Vulnerability Response
4. Upgrade each of the third-party integrations you're using, one at a time.
{#sem-install-prerequisites__ul_xss_bsy_hgc}

*[\>]: and then