---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/it-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Migrate to legacy change risk assessments

# Migrate to legacy change risk assessments {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

Users can migrate legacy change risk assessments to versions compatible with the new Change Risk Assessment table schema and logic.

## Antes de Iniciar

Few points to remember:

* Customers with Change Management - Risk Assessment \[Legacy\] (com.snc.change.risk_assessment) plugin already installed on their instances should only follow this task.
* The Change Management - Risk Assessment \[Legacy\] (com.snc.change.risk_assessment) plugin cannot be installed for customers who are on Kingston and later releases.
* Migration guidance and best practice suggests that the migration should be performed on a development instance and not on a production instance.
* The development instance must have the new Change Management - Risk Assessment \[com.snc.change_management.risk_assessment\] plugin installed.
* All migration work must be captured in an update set, moved to a test instance, and then tested before moving them to a production instance.
{#legacy-change-risk-assessment-migration__ul_mm4_xql_5gb}

Role required: itil_admin

## Por Que e Quando Desempenhar Esta Tarefa

The following legacy risk assessment components are migrated:  
* Risk assessment definition, questions, and question choices.
* For multiple assessment conditions, the migration might result in the following one or more than one risk assessment records:
  * If all the multiple assessment conditions are on the same table, then the migration results in only one risk assessment.
  * If the multiple assessment conditions are on different tables, then the migration creates as many risk assessments as they pertain to different tables.
  {#legacy-change-risk-assessment-migration__ul_jmn_p5n_vgb}
{#legacy-change-risk-assessment-migration__ul_pq1_vm1_fbb}

## Procedimento

1. Create an update set and set it as the current set.  
   For more information, see [Create and select an update set as the current set](https://www.servicenow.com/docs/access?context=create-select-update-set&version=australia&pubname=australia-application-development&ft:locale=en-US).
2. Navigate to ChangeRisk Assessment (legacy).
3. Open the legacy risk assessment that you want to migrate to a change risk assessment.
4. Click the Migrate to Risk Assessment related link.
5. Click OK.
6. Repeat steps 4-5 for all the legacy risk assessment to be migrated.

## O que Fazer Depois

After all the legacy risk assessments are migrated, reach out to the support team to run the following scripts:

    disable_legacy_change_risk_assessment.js

Capture the results in the update set created and later mark the update set as closed complete. For more information, see [Mark an update set complete](https://www.servicenow.com/docs/access?context=t_CompleteUpdateSets&version=australia&pubname=australia-application-development&ft:locale=en-US).  
Nota:  
The given procedure is a suggested practice. Alternatively, you can capture each migrated Change Risk Assessment in their own update set. You can also capture the results of disabling of the Change Management - Risk Assessment \[Legacy\] using `disable_legacy_change_risk_assessment.js` in a separate update set.
* **[Migrated risk assessment components](https://servicenow-prod.fluidtopics.net/sN10IQKFf5E2XLcl9AWemg)**   
  When you migrate a change risk assessment, the system maps records from legacy risk assessment to the new risk assessment tables.