First tab: True Dupes 

Second tab: Collective Conflicts 

These duplicates have the same filename as an asset in the Acquia DAM. You can choose one of three options to resolve these duplicates. This action will apply to all assets in this tab. 

• Skip: The conflicted asset or assets will be ignored and not uploaded.

• Rename: The conflicted asset or assets will be renamed with an additional _1, _2, etc. added to the filename.

• Upload_as_is: The conflicted assets will be uploaded with no changes, but they’ll become conflicted assets in the DAM. These conflicts can be resolved on the Uploads page or in the Admin app. 

Third tab: Filename Conflicts

These are files within the hard drive or S3 transfer that have the same filename. You can choose one of three options to resolve the duplicates. This action will apply to all assets in this tab.

• Skip: We will upload one of the files – the one with the largest file size – and the remaining conflicted asset or assets will be ignored and not uploaded.

• Rename: The conflicted asset or assets will be renamed with an additional _1, _2, etc. added to the filename. 

• Upload_as_is: The conflicted assets will be uploaded with no changes, but they’ll become conflicted assets in the DAM. These conflicts can be resolved on the Uploads page or in the Admin app. 

What are duplicates in an asset migration?

When using the Acquia Asset Migration Service, you will receive a CSV report about duplicate assets before those assets are ingested into your DAM. The next step is deciding what to do with the duplicates.

The CSV report will have multiple tabs.

First tab: True Dupes 

There are assets that are both filename and exact bit-by-bit replicates. These files will not be uploaded, because the site will not allow that level of duplication on bulk import. You do not need to do anything with these assets. 

Second tab: Collective Conflicts 

These duplicates have the same filename as an asset in the Acquia DAM. You can choose one of three options to resolve these duplicates. This action will apply to all assets in this tab. 

• Skip: The conflicted asset or assets will be ignored and not uploaded.

• Rename: The conflicted asset or assets will be renamed with an additional _1, _2, etc. added to the filename.

• Upload_as_is: The conflicted assets will be uploaded with no changes, but they’ll become conflicted assets in the DAM. These conflicts can be resolved on the Uploads page or in the Admin app. 

Third tab: Filename Conflicts

These are files within the hard drive or S3 transfer that have the same filename. You can choose one of three options to resolve the duplicates. This action will apply to all assets in this tab.

• Skip: We will upload one of the files – the one with the largest file size – and the remaining conflicted asset or assets will be ignored and not uploaded.

• Rename: The conflicted asset or assets will be renamed with an additional _1, _2, etc. added to the filename. 

• Upload_as_is: The conflicted assets will be uploaded with no changes, but they’ll become conflicted assets in the DAM. These conflicts can be resolved on the Uploads page or in the Admin app.