This version of the software is currently available only to customers in the Controlled Availability (CA) program.

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

To migrate Smart IT data

  1. Register a Smart IT source system.
    1. Register a source Smart IT system.
      register_source_system.png

      For the Smart IT source system, in the Schemas tab, make sure that you specify the logical names of Business and System schemas as Business and System:
      register_source_system_2.png

    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.
      register_target_1.png

      For the Smart IT target system, in the Schemas tab, make sure that you specify the logical name of the schema as
       Default:
      Postgres system.png

    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.
      triggers.png
    3. On the Set Trigger page, select the Disable Trigger check box and specify the database AR administrator credentials to run the Disable Trigger option.
      image-2024-4-16_12-15-27.png
  4. Configure file system connections for the Smart IT source system and target system.
  5. Create a copy of the existing Template Smart IT migration pack:
    1. Select Data Migration > Migration Packs. The imported template BMC migration packs are listed.
    2. Select the Template Smart IT migration pack and select Action > Copy.
    3. Select the source and target data dictionaries for the respective systems:

      Source data dictionary

      Data dictionary connecting to the source Smart IT system registered as Relational database in BMC Helix Data Manager.

      Target data dictionary

      Data dictionary connecting to the target system registered as Relational database in BMC Helix Data Manager.

    4. Enter the details and click Copy Migration Pack.

  6. Clear down target system data:

    Do not perform this step if you are migrating your BMC Helix ITSM: Smart IT data to version 22.1 or later.

    Prior to the import of data from the source system, sample data must be removed.

    1. Copy the Template SmartIT 2x.x Clear Down migration pack for your target system.
    2. Create and execute a deletion job on the target system.
      This automatically backs up any data prior to deletion so that it can be restored if needed.

  7. Migrate the Forms and the Relational Tables data:

    Important

    Do not migrate the Forms data if you are migrating your BMC Helix ITSM: Smart IT data to version 22.1 or later. However, you must migrate the Relational Tables data.

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

      Important

      Use the Template Upgrade SmartIT Forms 18.05 and above to 21.3 migration pack to migrate the Forms data.

      1. Run the export job.
      2. (Optional) Copy files from source to target file system.
      3. Run the import job.
        For more information, see Running-and-reviewing-migration-jobs.

    2. Migrate the Relational Tables data from the source system to the target system by performing the following steps:

      Important

      Use the Template Upgrade SmartIT 18.05 and above to 21.3 migration pack to migrate the Relational Tables data.

      1. Run the export job.
      2. (Optional) Copy files from source to target file system.
      3. Run the import job.
        For more information, see Running-and-reviewing-migration-jobs.
  8. (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:
      Tenant ID qualification.png
    5. Create a new data filter by specifying the actual tenant ID in the qualification.
      The following image shows an example:
      Data filter with actual tenant ID.png
    6. After applying the export filters to all the required nodes, run data migration job by using the Multi Tenant template.

  9. After you complete the migration, 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.

    Important

    If you are migrating both Smart IT and Openfire data, enable the foreign keys after you migrate Openfire data.

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. Select the source and target data dictionaries for the respective systems:

    Source data dictionary

    Data dictionary connecting to the source Openfire system registered as Relational database in BMC Helix Data Manager.

    Target data dictionary

    Data dictionary connecting to the target system registered as Relational database in BMC Helix Data Manager.

  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. 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 run the postmigration scripts

Important

Run the postmigration scripts only if you are migrating Smart IT data on a Oracle or a PostgreSQL database. If you are migrating data on a Microsoft SQL Server database, do not run any postmigration script. 

  1. Copy the Post Migration Data Update Template SmartIT pack in BMC Helix Data Manager tool.
    For steps, see Creating-a-migration-pack-for-your-systems.
  2. Set the source and the target data dictionary as SmartIT Relational Database target.
  3. On the Home page, click on the target system icon and click Administrate.
    postmigration_1.png

  4. In the Administration tab, open the Data Updates tab and click Run Data Updates.
    postmigration_2.png

  5. In the Create Data Update Job dialog box, select the target system and the postmigration template.
    postmigration_3.png

  6. Click Create New Data Update Job.
  7. In the Track Data Update Jobs tab, click Run All Scripts.
    postmigration_4.png

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.3 migration pack.
  3. Open Export Template > Included Forms tab.
  4. Select the SHR:SchemaNames form in the list and click Enable All 2022-05-31_14-19-12.pngbutton.
  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.

    filter_data_1.png

    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.
    shr_form_mapping.png
    The Data Mapping window opens.
  9. Open the Mapping tab, and set the Match On Fields field value to InstanceId.
    shr_2.png 

Related topic

Running-your-migration-project

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*