Unable to Migrate Because Content Manager Reports Object with Same Name Already Exists

When running a migration task, the Content Manager reports an error in the run history details that an object with the same name already exists, and the migration is unable to continue. If you then query the Content Manager database, you cannot find the object.

This problem occurs only when the Content Manager is a Microsoft SQL Server database, and is caused by the existence of an object in the Content Manager database that contains a variant of one of the characters in the object name. For example, the object you are migrating contains the Unicode character U+00A2 (cent sign), and an object with the Unicode character U+FFE0 (full-width cent sign) exists in the database.

To resolve the problem, do one of the following before migrating:

In the Content Manager database, delete the object that is stopping the migration.
Recreate the Content Manager database using the collation sequence Latin1_General_CI_AS_KS_WS instead of Latin1_General_CI_AS.
By creating the Content Manager database using a collation sequence that includes width-sensitive characters (_WS), you will avoid conflicts with objects that contain both half-width and full-width variants of the same character in their names.