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

Data mapping

When a migration pack is created, a data mapping is automatically created between the forms in the relationship set between the source system and the corresponding forms in the target system.

BMC Helix Data Manager's automated data mapping expert maps a source form to a target form and then attempts to map all source and target fields. When the source and target applications are identical, all fields are mapped.

If there are data model differences between the source and target system, such as new forms and fields, some fields may fail to be mapped. This is common in the case of an ITSM application upgrade where the new version has multiple new forms, fields, and changes to enumerated values.

The data mapping rules that BMC provides for the out-of-the-box ITSM application versions contain rules about how to handle the data model changes when moving between different ITSM versions. You can extend these data mapping rules to handle your application customizations.

The BMC Helix Data Manager Runtime can apply a range of transformation and data enrichments when performing data migrations. For example, you might want to use an upgrade as an opportunity to change the Operational Catalog. BMC Helix Data Manager can convert your live and historic data to the new Operational Catalog using data enrichment.

BMC Helix Data Manager Workbench allows you to fully configure the migration and transformations that are applied to data during a data migration.

The Data Mapping page gives you access to the following functions:


 

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