The Policy/PolicyDetail/Service/ServiceDetail version attributes and the policy "revision" property and the service "policyRevision" property are the values in question.
CA API Gateway: All Releases
Do one of the following options:
OPTION #1: In the bundle XML file, set the policyRevision and version attributes to 0 before performing the migrateIn operation.
NOTE: Policy revision history doesn't get migrated, so version conflicts are not problematic if you choose this option. As long as there are no changes to GMU (where we decide to migrate the policy revision history), this course of action is acceptable.
OPTION #2: Make no changes to the policyRevision and version attributes before performing the migrateIn operation.
NOTE: The migrateIn will automatically reset these attributes.
After the migrateIn operation, the policyRevision attribute will be set to 1 (even if you set the value to 0) and policy attribute will be set to 0.