Creating an import template

You can create multiple import templates for a migration pack to provide multiple options for importing data without needing to create multiple packages.

To create a new import template

1. From the navigation bar, select Data Migration > Migration Packs.
2. Select a migration pack.
3. Click the Import Template tab.
4. Click the Info sub-tab.
   

1. Select one of the following options:

   • Copy to New—Copies the existing template settings and disabled forms or tables.
   • Create New Template—Creates a new template carrying forwards none of the configuration settings.

   A new template with default settings is created, and its Status is set to Draft. The list of the configured templates appears.

2. Select each template you want to rename or reconfigure, and make the changes.
   You can configure the following details for an import template:

   Option	Description
   Name	The unique name for the import template for this migration pack.
   Status	The status of the import template, only available templates are available for import operations.
   Description	A brief description of the import template shown when creating a new Import Job
   ID Transformation	This option enables AR System identifiers to be optionally transformed during a data migration. Options are: None—No transformation will be applied Simple—All identifiers will be transformed User Selection—Users may select the transformation to be applied Custom—Enables different transformation options to be applied to each of the classes of identifier. For more information, see Identifier-transformation-considerations.
   Incremental Import	An incremental import is one where more than one data migration is being performed between the same source and target systems using the same customer's data set. For example, several weeks before go live you may perform an existing migration to your new upgraded production system and then a final migration of only the changed data over the final cutover weekend. The second migration should be run as an incremental migration. An incremental import will only include records that are modified after a selected date and time. A date range or qualification parameter filtering data on the Last Modified Date must be applied to all root nodes of the migration tree. Incremental migrations have a beneficial impact on end to end migration time. This option may be set to Yes or No.
   Form Deletion Check or Table Deletion Check	This option will only take effect if the template is performing an incremental update. BMC Helix Data Manager will check whether any records in the target system do not exist in the source system and remove them as part of the migration. This deletion only occurs within the data set being migrated. For example, if you are migrating a specific ITSM company than only records belonging to that company on the target system which do not exist in the source system will be deleted. Data belong to other companies is not affected.
   User Cache Import Action	This option allows you to import the user cache data from the User form. During export, the user cache is exported from the source system as a form action when processing the User form. User Cache Import Action allows you to import or ignore the user cache in the import template and import job. You can select the following options: IGNORE - Use this option to ignore the user cache data while import. CREATE - Use this option to create new user cache data. MODIFY - Use this option to modify the user cache data. CREATE AND MODIFY - Use this option to create new and modify existing user cache data. By default, the value for a new pack is CREATE AND MODIFY.

3. Click Save Changes.

To enable, disable, or delete import templates

• To change the status, select the new value from the list, and click Save Changes.
  Only import templates that are set to a Status of Available can be selected by operators running data migrations.

• To delete a template, select it from the list, and click Delete Template.