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

Running an export migration job

Run the export migration job to export data from the source system.

To export data 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 export migration job to export data from the source system. For on-premises to on-premises migration, the files are available locally. Use the BMC Helix Data Manager tool on the source system to create and run the export migration job.

Perform the steps in the section To create the export job.

After you complete exporting the data, perform the import of the data on the target system. See Running-an-import-migration-job.

To export data 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:

  1. Perform a data export of global and environment data from your source on-premises BMC Helix Data Manager system to create data packages.
    Perform the steps in the section To create the export job.

    Important

    We recommend you to use Environment-all setting to perform the migration.

  2. Export the migration pack from the source on-premises system.

  3. SFTP the exported data packages and migration pack to your FTP location for file transfers, and then download them to the defined file system on the target development staging server. 

    Important

    Copy the files from the FTP location within seven days of the transfer because they will be deleted from the server after seven days.

After you complete exporting the data, perform the import of the data on the target system. See Running-an-import-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.

To create the export job

  1. From the navigation bar, select Data Migration > Migrate Data.
    Alternatively, from the Home page, click the source system and select Export Data from the menu.
    The Create Migration Job dialog box appears.
    The following image shows an example:
    MigrateData.png

  2. Select the systems from the Export Data From System and Import Data To System lists.

    Important

    To migrate data to a Smart IT target system that runs on Oracle database, select the Oracle migration set. 

  3. Confirm the migration pack, export template and file systems that will be used for the migration job. (See Setting-up-migration-packs-mappings-and-templates.)
  4. Click Next to proceed.
    Typically, no parameters need to be populated for the Environment Upgrade Template; however, if you have customized this template, you may be prompted to enter parameters.
  5. If required, provide the parameters, and click Next.
  6. Review and confirm the details for the Migration Job.
    The following image shows an example:
    nextID_export.png
    The following details may be configured:
    • Migration Job Name—We recommend setting this to a unique name for your migration.
    • Delimiter - Field to add custom delimiter value. Keep this field blank if you are running the migration for the first time. Use a custom delimiter only for the forms where the migration of the form fails due to errors in parsing the records. For more information, see Troubleshooting-data-import-issues.
    • Export Threads—The number of threads that will be used to perform the export. More threads can improve export performance but will place a greater load on the infrastructure. Insufficient resources can cause failures during the export process.
      There is no hard-and-fast rule for the number of threads that will provide you with the optimal performance. We recommend starting with one thread for the initial migrations to test the load on your system.

    • Export Next Id - Use this option to export 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 Export Next Id option is available when you are migrating data from a source BMC Helix ITSM system to a target BMC Helix ITSM system. 

      In older versions of BMC Helix Data Manager, an SQL postmigration script handled the Next ID processing, but it is no longer required if you use the Export Next Id option. 

      Best practice
      We recommend that you use the Export 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 export Next IDs:

      • NONE - Use this option if you do not want to export the Next IDs for any forms in the source system.
      • ALL - Use this option to export the Next IDs for all the forms present in the source system.

      • INCLUDED - Use this option to export the Next IDs for the forms that are present 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

    • Export Mode
      • Tree (the default)—Migrates data by using the tree structure defined in the migration pack.
      • Flat—Exports all data for all unique forms in the migration pack. This includes orphaned or junk data in your system but can give faster migration times. Flat mode export will not be used for a form that has parameters or to the children and parents of these form
  7. Click Confirm Migration to create and display the migration job.

  8. (Optional) Click Customize to display the following view where you can disable forms from the scope of the migration or set chunking for a specific form in the tree.
    The following image shows an example:
    CustomizeMigration.png
    Chunking allows you to break up large forms into chunks. These chunks must be a minimum of 500,000 records. This can reduce the database load when exporting very large tables.

    Important

    If you have selected the Chunk option when migrating data from a source Microsoft SQL database to a target Microsoft SQL database, you will see the following warning on User table when you import the data:

    User Cache import is not successful

    Ignore these warnings.

  9. When you have completed any changes, click View Migration Job to open the migration job.
    The following image shows an example:
    ViewMigrationJob.png
  10. Click Start Export to start the export process.
    The export job appears, and you can monitor the progress.
    For more information about the export process, see Viewing-and-monitoring-export-jobs.
  11. If the Next ID value of the source field is greater than MAX INT(2147483647) value, the export job will display warnings after completion:
    1. If the form with the Next ID error is present in the migration pack, the following warning is displayed on the Errors & Warnings tab:
      Next Id is incorrect for <Form Name>
    2. If you have selected Export Next Id = ALL, and the form is not present in the migration pack, the following warning is displayed on the Summary tab:
      Next Id is incorrect for some forms Please refer logs for more info.
      Check the logs and troubleshoot the Next ID issues.

Related topics

Troubleshooting-data-import-issues.

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*