Migrating CMDB Data to Jira Service Management

Precision Bridge can be used to migrate CMDB class definitions (including attributes) to your Jira Asset module in addition to the migration of the configuration items themselves.

The migration should be completed in the following steps:

1. Create the project for migrating the class definitions and attributes to the Asset object types and attributes

2. Execute the project

3. Create a new project for migrating the configuration items using the created object types and attributes that will be presented in Precision Bridge as forms and fields, available for mapping.

If you need to migrate the hierarchical structure of your source CMDB when migrating the class definitions, it is recommended to create a mapping for the top-level "base" class, and then create a mapping for its attributes. Further mappings should then be created for each subsequent level followed by the attributes for them. 

As Cherwell does not have a hierarchy and so no top-level "base" class, it is recommended to manually create this in Jira prior to migration as described in detail in this article. The migration project then only requires a single mapping for the configuration item types and one for the attributes. To create the object type in Jira with the "base" object type as the parent, you should set the "Parent Object Type Id" field in the mapping to the Object Type Id of the "base" object type, either through an Assignment mapping or a lookup.

Within the mapping for the attributes, it is recommended to use a Filter by Inclusion within Source Filtering to restrict the records migrated to those of the classes at the same level.

Similarly, the migration to the Jira Asset Object Type should use the Filter by Inclusion within Source Filtering to ensure that only the classes that inherit from the previous level classes are migrated in the mapping.

For asset relationships, there is a function GENERATE_GSM_OBJECT_ARRAY that can build an array of child objects where the current record indicates the parent. This can then be assigned to the Object relationships attribute in the Object Type in Jira.

It is recommended that you use a dedicated mapping for adding the relationships as the objects types being related to need to have been created in Jira through the previous mappings.

Re-running the Project

It is possible to re-run the project to pick up any changes or additional object types and attributes. Existing objects/attributes will be updated and new ones created.

There is one caveat though. Due to API restrictions, it is not possible to change the names of existing objects nor change the value of the inherited flag. These field mappings will be ignored if an object is being updated.