Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Legacy change risk assessment migration

Log in to subscribe to topics and get notified when content changes.

Legacy change risk assessment migration

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

Before you begin

Role required: itil_admin
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.

About this task

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.


  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.
  2. Navigate to Change > Risk 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.
    A message window appears stating that the assessment is migrated to a new change risk assessment.
    Note: Migrating legacy risk assessment to a new change risk assessment does not modify the existing legacy assessment records.
  5. Click OK.
  6. Repeat steps 4-5 for all the legacy risk assessment to be migrated.

What to do next

After all the legacy risk assessments are migrated, reach out to the support team to run the following scripts:
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.
Note: 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.