This technical note outlines an issue found with Project Duplication where contacts for merged users do not get modified to use the merged user when using the setting "merge users by comparing logins if matching IDs are not found". This setting checks for if login or Trusted Authentication ID match between environments for any users despite having different object IDs. This is necessary as login/trusted authentication ID must be unique to prevent a situation where two separate users would have to enter the same login to access Strategy and there is no way to distinguish them.
In Strategy 9.4.x Tutorial, steps to reproduce are below:
This is a known issue in Strategy Intelligence Server 9.x. Due to how duplication currently works the contacts are not correctly flagged to be modified to the new destination users Object ID leaving them as invalid in the metadata.
This is related to the issues seen in the following two tech notes:
Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release.