During migration of asset management data, most of the asset management objects (e.g., Purchase Records, Licensed Products) are migrated without checking for duplicate objects in ZENworks 11 SP3 Asset Management. This can lead to the following outcomes if there are objects in ZENworks 11 SP3 Asset Management that match objects being migrated from ZENworks Asset Management 7.5 (see Section B.1, Duplicate Object Details for what constitutes a duplicate of each object type):
If the migration process is restarted due to errors, the ZENworks Asset Management 7.5 data has already been partially migrated. Because of the partially migrated data, the already migrated objects are rejected and the migration utility reports duplicate key violations.
If you are migrating to ZENworks 11 SP3 Asset Management you can fix the duplicates and then restart the migration utility, making sure to turn off the setting. However, restarting migration might result in loss of data. If this possibility is not acceptable, we recommend that you restore the ZENworks Asset Management 7.5 and ZENworks 11 SP3 Asset Management database backups, resolve the duplicates, then run the migration utility again.
If the objects are duplicates and the ZENworks 11 SP3 Asset Management version of the object is not in a subfolder, the migration utility produces an error. Some or all of the duplicate objects that the migration utility was processing (e.g., licenses) are not moved to ZENworks 11 SP3 Asset Management.
If the objects are duplicates but the ZENworks 11 SP3 Asset Management version of the object is in a subfolder, the migration utility adds the object to ZENworks 11 SP3 Asset Management. You end up with two objects in ZENworks 11 SP3 with matching names, but in different folders. The exception to this is Contracts, which does not allow duplicate Contract ID’s in ZENworks 11 SP3 Asset Management, even in subfolders.