Defining Migration Rules
When defining any migration rule, these are the basic fields that you may need to set up.
Field | Description |
|---|---|
Source Category | The category that drives the migration. This field is set when you create a new migration and it cannot be edited. |
Target Category | The category that receives the migration. This field is set when you create a new migration and cannot be edited. |
Migration Type | The type of migration rule that you want to perform. For more information, see Types of Migration Rules. |
Sequence | If you have more than one migration rule with the same Source category, you may want them to be applied in a specific order. You can use this field to specify the sequence of the migration rules. |
Offset Length | Offset and Length determine the position within the Source Category code that will be used for the migration. These are only used for standard migration types, and the manner in which they are used is slightly different for each type. (For more information about migration types, see Types of Migration Rules.) See the topic on Offset and Length for more information. |
Do Not Overwrite | Select this option to keep an existing value without overwriting it during the migration process. For example, a Copy Code migration for A to B is defined and Do Not Overwrite is selected. If the B value is initially empty and the user selects a value in A, the migration takes place and copies the value to B. Now, if the user selects another value for A, it is not copied to B (since the B value is no longer empty). The user must clear the B value before setting the value of A. |
Active | Select this option to enable the migration. Inactive migrations are ignored by the system. |
In addition to the above fields, certain types of migrations may require you to set up some additional data. This information is discussed in the section corresponding to those types.