About conflicts with existing data when importing

When unica_acsesutil imports data into the system tables (for example, session info, triggers, or custom macros), it checks whether each object already exists on the target system.

The check is done based on internal object ID. That is, for campaigns, if the internal campaign ID is not unique, unica_acsesutil asks if the campaign should be overwritten. If you choose to overwrite the campaign, unica_acsesutil removes all data associated with the existing campaign on the target server, and then imports the new campaign. Similarly, when importing offers, unica_acsesutil checks the internal Offer ID for uniqueness.

If an object with the same ID already exists, you have the option to skip that object in the import process or to replace the existing object.

If you know that a conflicting object (such as a campaign, session, or offer) already exists on the target system prior to import, you should consider deleting the object before running the import, to avoid being prompted to resolve the conflict.