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

Running an import migration job

After the export is complete, you must return to the migration job to create the import job.

To create an import job for on-premises to on-premises migration

To migrate your data from an existing on-premises system to a new on-premises system, create an import migration job after you perform the data export.

For on-premises to on-premises migration, the files are available locally. Use the BMC Helix Data Manager tool on the target system to create and run the import migration job.

Perform the following steps:

  1. Download and copy the Form Deletion Set With UDM_Forms.cmt file before you create the import job:

    1. Download the Form Deletion Set With UDM_Forms.cmt file from the HDM Metadata folder on the FTP location - ftp.bmc.com.
      For steps to access the HDM Metadata folder, see the topic Downloading-the-installation-files.
    2. Copy the Form Deletion Set With UDM_Forms.cmt file to the <HDM_Installation_directory>/BMC Software/Helix Data Manager/Metadata folder.
    3. In BMC Helix Data Manager WorkBench, select Configuration > Import HDM Meta Data.
    4. Click Scan to scan the metadata directory for .hdm files to import.
      Metadata files you placed in the Metadata directory are listed.
    5. Select the Form Deletion Set With UDM_Forms.cmt file, and click Import Meta Data.
    6. Click Import on the confirmation dialog box to confirm.
      The Form Deletion Set With UDM_Forms.cmt file is imported into the HDM.
  2. Complete one of the following steps:
    • If no import jobs have been created in the view, click Create Import Job to open the Create Import Job dialog box.
    • If an import job has already been created, click the plus button on the left of the Import tab to open the dialog box.
  3. If you are not using a shared file system, select the file system and perform a scan to ensure that the files are available for import.
    If you are using a shared file system for your export and import, the majority of details for the import job are automatically selected.
    You can find the data package in the file system you configured per the installation instructions. The package will be created in the packages folder. The folder name will be shown as the job name. If an existing folder has the same name in the packages folder, a three-character suffix is applied.
  4. Copy this folder and all of its files the packages folder on the target file system.
  5. Click Scan File System to trigger BMC Helix Data Manager to read the data package definition from the target file system.
  6. Click Next.
    The final step for creating an import job appears.
    import_job.png
  7. Set the import job parameters. See To configure import job parameters.
  8. Click Confirm Data Import to create the import job and return to the migration job.
  9. Click the Start button to start the import process and track the progress on the Import Job page.
    For more information, see Viewing-and-monitoring-import-jobs.
  10. After you successfully run the import migration job, see Completing-postmigration-steps. 

To create an import job for Remedy on-premises to BMC Helix Innovation Suite Cloud migration

For Remedy on-premises to BMC Helix Innovation Suite Cloud migration, export the data from the source on-premises ITSM system by using the on-premises BMC Helix Data Manager tool, copy the data to the target BMC Helix ITSM cloud, and run the import job on the target BMC Helix ITSM cloud by using the Development staging server BMC Helix Data Manager tool. 

Perform the following steps:

Before you begin

  1. Run the clear-down pack on the target development staging server.
    For more information about running the clear-down pack, see Run the clear-down pack.
  2. Scan the file system to view the exported global and environment data packages and migration pack.
  3. Import the migration pack to the BMC Helix Data Manager tool installed on the target development staging server.
    1. Select Configuration > Import HDM Meta Data.
    2. Click Scan.
    3. Select the migration pack metadata file, and click Import Meta Data.
    4. Click Import on the confirmation dialog box to confirm.
  4. When you import the migration pack, the source data dictionary is also imported to the development staging server BMC Helix Data Manager.
    Perform the following steps to link the data dictionary:
    1. Navigate to Discovery & Analysis > Discovered Data Dictionaries and select the source data dictionary.
    2. Under Linked Systems, select the registered Remote source system.

To run the import job

  1. Import the data from the data packages:
    1. Select Configuration >Configure File System Connections.
    2. Click the Defined File Systems tab, click the Data Packages tab below, and select the data package.
    3. From the Action menu located at the bottom right of the list of data packages, select Import Data Package.
    4. Click Confirm Import.
  2. Set the import job parameters. See To configure import job parameters.
  3. Click Confirm Data Import to create the import job and return to the migration job.
  4. Click the Start button to start the import process and track the progress on the Import Job page.
  5. Review and fix any import errors.

To complete the postmigration steps

  1. Complete an analysis of the form count.
    For more information about form count analysis, see Getting-form-counts.
  2. After you successfully run the import migration job, see Completing-postmigration-steps. 

For end-to-end process of Remedy on-premises to BMC Helix Innovation Suite Cloud migration, see Migration process for Remedy on-premises to BMC Helix Innovation Suite Cloud.

To configure import job parameters

Set the following values for the import migration job:

Option

Description

Import Job Name

If performing more than one import, we recommend assigning a unique name to your import job.

Import Threads

The number of simultaneous imports that BMC Helix Data Manager will perform. Increasing threads can improve your import times but will place additional load on your infrastructure.

Incremental Import

This setting indicates whether this is an import of Incremental data. For more information, see Running-a-delta-data-incremental-migration-job.

Form Deletion Check

Select Form Deletion Set With UDM_Forms.cmt as the deletion list.

This setting is only available for incremental imports and allows you to select the Form Deletion Template, which will identify the forms that should be checked for deletion.

Import Next Id

Use this option to import and update the Next IDs of the forms to be migrated. Next ID stores the unique ID of the latest created record in a form.

Important

The Import Next Id option is available when you are migrating data from a source BMC Helix ITSM system to a target BMC Helix ITSM system.

Best practice

  • We recommend that you use the same option used during export.
  • We recommend that you use the Import Next Id - INCLUDED option to make sure that the correct Next ID is set on the target BMC Helix ITSM system.

You can select the following options to import Next IDs:


    • NONE - Use this option if you do not want to update or import the Next IDs for any forms in the target system.
    • ALL - Use this option to import and update the Next IDs for all the forms present in the target system.

    • INCLUDED - Use this option to import and update the Next IDs for the forms that are included in the migration pack used for migration.

      Click here to see the list of the forms that are not included in any of the migration packs.

      Ticket Generator form

      Dependent Form

      CFG:BusTimeTagGenerator

      CTM:Support Group On-Call

      CFG:CFG PBB TicketNumGenerator

      CFG:Broadcast

      CFG:CFG ScriptTagNumGenerator

      CFG:Scripts

      CHG:CFG Ticket Num Generator

      CHG:Infrastructure Change

      CTM:CFG PTTicket Num Generator

      CTM:People Template

      HPD:CFG Ticket Num Generator

      HPD:Help Desk

      PBM:CFG KDBTagNumGenerator

      PBM:Solution Database

      PBM:CFG KE TicketNumGenerator

      PBM:Known Error

      PBM:CFG PI TicketNumGenerator

      PBM:Problem Investigation

      RMS:CFG Ticket Num Generator

      RMS:Release

      SRD:CFG DefinitionNumGenerator

      SRD:ServiceRequestDefinition

      SRD:Cart TicketNumGenerator

      SRD:ServiceRequestGroup

      SRD:Package TicketNumGenerator

      SRD:SRDPackage

      SRM:CFG TicketNumGenerator

      SRM:Request

      WOI:CFG TicketNumGenerator

      WOI:WorkOrder

      AAS:ConfigurationTicketNumGenerator

      AAS:Activity

Application Identifiers

Use this option to control the prefixing of request IDs, ticket numbers, SLA IDs, and group IDs. These settings are typically used only in a consolidation scenario.

User Cache Import Action

Use this option 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.

Where to go from here

Completing-postmigration-steps

Reviewing-the-data-package-contents

Running-a-delta-data-incremental-migration-job

For end-to-end process of Remedy on-premises to BMC Helix Innovation Suite Cloud migration, see Migration process for Remedy on-premises to BMC Helix Innovation Suite Cloud

 

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