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

Creating a migration pack for your systems


To create a migration pack that you can use migration in your environment, you can copy the template BMC migration packs and apply them to your locally discovered data dictionaries.

Important

The migration pack created for your systems will not include your custom forms and might have data mapping issues that you must resolve for a fully successful migration. See Adding-your-custom-forms-to-a-migration-pack and Identifying-data-mapping-issues.

Before you begin

  • Register the source and target BMC Helix ITSM systems.
  • Discover the source and target data dictionary.
  • Import the BMC Helix Data Manager template migration packs.

Copying a migration pack from a template

Select any existing migration pack as a template. The data mappings, enrichments, and migration trees are used as a template to create a new migration pack for any two source and target data dictionaries you select.  For example, if you use the BMC Helix Data Manager Upgrade migration pack for out-of-the-box BMC Helix ITSM 7.6.04 to BMC Helix ITSM 9.1 as a template for your upgrade, then all of the data mappings and transformations necessary for a successful upgrade are copied to the migration pack for your local systems.

BMC Helix Data Manager also attempts to map your customized fields in your source and target systems. Any custom or unexpected forms or unmappable fields are flagged for review.

After copying the pack, you can override or extend any aspect of the data migration configuration.

Creating a new migration pack

You can create a new migration pack to migrate a set of related data. A relationship set is used to describe the data set that will be migrated.

BMC Helix Data Manager performs automated field-level mapping based on field IDs and data types. This automated mapping will not include special data mapping rules required for an upgrade scenario.

Any unmappable fields are flagged for review.

You may override or extend any aspect of the data migration after the pack is built.

To copy a migration pack to use for migration

  1. Select Data Migration > Migration Packs. The imported template BMC migration packs are listed.
  2. Select the template migration pack that you want to use for your migration, and select Action > Copy.
  3. Select the source and target data dictionary you discovered from your local systems, and click Copy Migration Pack.You can specify the following options when creating a migration pack:

    Option

    Description

    Name

    Specify the name of the new Migration Package.

    Source Data Dictionary

    Specify the source data dictionary.

    Target Data Dictionary

    Specify the target data dictionary.

    Migration Trees

    You can select any of the following options:

    1. Copy Migration Trees - This option is used to copy the migration trees from the template migration package.
    2. Use Relationship Set - You can use this option to copy the migration packs with relationship sets. If this option is set, the packs added manually will not be copied.

    Options

    Remove Unused Form Mappings: This option is used to copy only the form mappings linked to the migration node.
    If this option is set to True, only the form mappings linked to the migration node will be copied and the other form mappings will not be copied.
    By default, this option is set to False. We recommend you to set this option to False.  

  4. When the copy process is complete, click View Migration Pack to view the migration pack created for your source and target systems
  5. To modify the migration pack:

    1. Select your copied migration pack.
    2. Click the Pen icon.
    3. Set the Status to Published.
    4. Click the Save icon.

    You are now ready to perform data migrations using this migration pack, which is tailored for your applications.

 

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