Running an export migration 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:
   

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:
   
   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-by-using-custom-delimiter.
   • 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 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:
   
   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.
9. When you have completed any changes, click View Migration Job to open the migration job.
   The following image shows an example:
   
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.

Related topics

Troubleshooting-data-import-issues-by-using-custom-delimiter