Applying field mappings to a data migration


The Enable Field Mapping option in the Data Migration Settings dialog box allows you to apply field mappings to data migration. When you select the Enable Field Mappings check box, the Mappings button becomes active. Using this feature, you can map source fields to a destination field or a keyword.

You can also save mappings to a file for reuse later, to save time and reduce errors. You can load the saved mapping file instead of entering the mapping values again. When you save a mapping, the form name, the server where the form resides, and the data file name are saved.

You can auto-map all fields according to the field ID or the field name used in Developer Studio. You can remove any of these generated mappings or add mappings.

Consider these conditions when using field mappings:

  • Field mapping in Migrator does not work with data files such as .arx files.
  • Migrator does not perform any validations on field mappings.
  • A source field can be mapped only once.
  • A destination field can be mapped to more than one source field.

To apply field mappings

  1. In the Data Migration Options dialog box, select the Enable Field Mappings check box.
  2. Click the Mappings button.
  3. In the Field Mappings dialog box, enter the mappings you want to use for the data migration.
    • To auto-map field IDs or field names, click Auto Map IDs or Auto Map Names.
    • To add a mapping, click Add Mapping.
    • To delete one or more mappings from the Current Mappings list, select the mappings, and click Delete. To remove all of the mappings, click Delete All.
    • To save a mapping, select the mapping and click Save.
    • To load a mapping you have saved, click Load and select the mapping.
  4. Click OK.

 

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