Migrating Smart IT data

After you perform the data migration for BMC Helix ITSM, perform the Smart IT data migration and then perform the Openfire data migration.

Before you begin

• Make sure that you have migrated your BMC Helix ITSM data.
• Make sure that you have downloaded and imported BMC Helix ITSM: Smart IT migration pack.
• Make sure that you have downloaded and imported Openfire migration pack.

To migrate Smart IT data

1. Register a Smart IT source system.
   1. Register a source system.
   2. Create a BMC Helix Data Manager user.
   3. Test system connectivity and get database character set details.
   4. Discover the source system.
2. Register a Smart IT target system.
   
   1. Register a target system.
   2. Create a BMC Helix Data Manager user.
   3. Test system connectivity and get database character set details.
   4. Discover the target system.
3. Disable foreign keys in the Smart IT target system by using the Disable Trigger option.
   
   1. In the BMC Helix Data Manager, navigate to the System Configuration page for Smart IT target system.
   2. On the System Configuration page, click Actions and select Enable/Disable Triggers.
   3. On the Set Trigger page, select the Disable Trigger check box and specify the database administrator credentials to run the Disable Trigger option.
4. Configure file system connections for the Smart IT source system and target system.
5. Copy the Smart IT migration pack to your Smart IT source system and target system.
6. Migrate data from the source system to the target system by performing the following steps:
   1. Run the export job by using Smart IT migration packs.
   2. (Optional) Copy files from source to target file system.
   3. Run the import job by using Smart IT migration packs.
      For more information, see Running-and-reviewing-migration-jobs.
7. Copy the template Smart IT migration pack to the Smart IT source and target systems.
8. Run the data migration job by using the Default template.
9. (Optional) For multi-tenant migration, perform the following steps:
   
   1. Change the filters in the Multi Tenant template in the migration pack with the correct tenant ID that you want to migrate from the source system.
   2. Select the Multi Tenant export template.
   3. Select the nodes that have data filter applied to the nodes.
   4. Delete the Qualification tenant_id = '1111' data filter.
      The following image shows an example:
      
   5. Create a new data filter by specifying the actual tenant ID in the qualification.
      The following image shows an example:
      
   6. After applying the export filters to all the required nodes, run data migration job by using the Multi Tenant template.

To migrate Openfire data

1. Register an Openfire source system.
   1. Register a source system.
   2. Create a BMC Helix Data Manager user.
   3. Test system connectivity and get database character set details.
   4. Discover the source system.
2. Register an Openfire target system.
   
   1. Register a target system.
   2. Create a BMC Helix Data Manager user.
   3. Test system connectivity and get database character set details.
   4. Discover the target system.
3. Configure file system connections for the Openfire source system and target system.
4. Copy the Openfire migration pack to your Openfire source system and target system.

5. Migrate data from the source system to the target system by performing the following steps:

   1. Run the export job by using Smart IT migration packs.
   2. (Optional) Copy files from source to target file system
   3. Run the import job by using Smart IT migration packs.

   For more information, see Running-and-reviewing-migration-jobs.

6. Enable foreign keys in the Smart IT target system by using the Disable Trigger option.
   Make sure that you do not select the Disable Trigger check box and specify the database administrator credentials to enable the foreign keys.

Postmigration tasks

To migrate custom data from the SHR:SchemaNames form

If you have created a custom class in the source system, the data of the custom class is stored in the SHR:SchemaNames form. The HDM utility does not migrate data stored in this form. You must manually enable the migration of the SHR:SchemaNames form to migrate the custom data.

Perform the following steps to migrate the data from the SHR:SchemaNames form:

1. On the navigation bar, select Data Migration > Migration Packs.
2. Select the Template SmartIT 18.05 or Above to 21.05 migration pack.
3. Open Export Template > Included Forms tab.
4. Select the SHR:SchemaNames form in the list and click Enable All button.
5. Get the entry Id of the custom class ID from the SHR:SchemaNames form.
6. Click Add Data Filter and create a Custom Qualification as follows:
   $Entry-Id$="entryId"
   where entryId is the custom class ID of the SHR:SchemaNames form.
   
   
   
   Steps to get the entry ID:
   1. Open the SHR:SchemaNames form and search record.
   2. Click Report.
   3. Click Create New Report.
   4. Select Type as AR System.
   5. Add Entry-Id field in the report and click Save Record.
   6. Click Run Report.
      The Entry-Id is displayed.
7. Click Apply Data Filter.
8. Open the Import Template tab. Ssearch for the SHR:SchemaNames form and click Form Mapping.
   
   The Data Mapping window opens.
9. Open the Mapping tab, and set the Match On Fields field value to InstanceId.
    

Related topic

Running-your-migration-project