User Guide › Administration › Content Transfer › Supported Entities › Contracts › Contracts Transfer and Content Transfer Conflicts

Contracts Transfer and Content Transfer Conflicts

When there is a name conflict, the content transfer wizard provides the solution to rename the contract in the local environment and then create the new contract. However, for a sync conflict, when the contract was updated in both source and local environments, no resolutions are provided. To recover from such a conflict the recommended solution is as follows:

1. Purge the contract in the source environment.
2. Sync the environments by transferring the contract from the local to the source.
3. Reapply the changes you wish to transfer in the source environment based on the changes that were already done in the local.
4. Transfer the contract from the source environment to the local environment.

Another option is to purge the contract in the local environment and then select the contract again to be transferred. This option is not recommended because it involves manual intervention in the local environment (which may act as the production environment) and because it requires a full recalculation of the contract in the local environment.