Migrating documents between use case type versions

Use the document migration functionality to move existing documents from a source version to the Active target version of the same use case type.

Migrating documents

To migrate documents:

  1. Specify the source version that currently contains the documents.
  2. Specify the Active target version to which the documents must be moved.
  3. Provide category mappings from the source version to the target version.
  4. Run the migration.
  5. Review the total number of migrated documents in the migration response.

Migration validation rules

Review these validation rules before starting a migration. The migration process verifies version compatibility and category mappings to ensure that the source and target versions meet the required criteria.

  • The target version must be in the Active status.
  • The source version and target version must belong to the same use case type.
  • The source version and target version cannot be the same version.
  • Each source category can be included only once in the mapping list.
  • All source categories specified in the mapping must exist in the source version.
  • All target categories specified in the mapping must exist in the target version.
Note: The migration process validates version status, use case type compatibility, and category existence. The migration process does not validate entity data or table data.