Restoring data to its previous state

This section describes the steps to restore data to its pre‑migration state in case of issues.

About this task

If any issues occur with CI records during or after migration, you can restore the data to its previous state and rerun the migration for the affected classes.

Procedure

  1. Deactivate the migration scripts to stop the migration process. To deactivate:
    1. Go to System Definition > Scheduled Jobs.search for the following migration scripts:
    2. Search for the following migration scripts:
      • OOB Migration Scheduled Script - CICS & Sysplex
      • OOB Migration Scheduled Script - DB2
      • OOB Migration Scheduled Script - IMS
      • OOB Migration Scheduled Script – MQ
    3. Open each migration script, clear the Active checkbox, and click Update.
  2. Determine which CI classes encountered issues. Retrieve the XML backup files for those classes, along with the XML backup for the CI Relationships table.
    These are the same backup files created before starting the migration.
  3. Navigate to each corresponding out-of-the-box class and delete all migrated records to prevent conflicts during restoration. To delete the records:
    1. In ServiceNow, go to System Definition > Tables.
    2. Locate the relevant CI class, for example, DB2 Subsystem.
    3. Open the record, switch to the Global application scope, and click Delete All Records.
  4. Import the XML backup files to restore data for each affected custom class. To import the XML for custom classes:
    1. Search for the custom class. Type the name of the class and add .list to it.
    2. Expand the Column options menu and select Import XML.
      Note: Ensure that no filters are applied to the tables during import.
    3. Choose the downloaded backup file and click Upload.
  5. Import the CI relationship table to restore data for each affected custom class. To import the CI relationship table:
    1. In ServiceNow, search for cmdb_rel_ci.list.
    2. Expand the Column options menu and select Import XML.
      Note: Ensure that no filters are applied to the tables during import.
    3. Ensure that no filters are applied to the tables during import - add as note.
    4. Choose the downloaded backup file and click Upload.
  6. After you finish restoring the affected classes, reactivate the scheduled scripts to continue the migration. See Migrating data from existing custom classes to out-of-the-box classes.