In this case, sync is not working Found objects by sAMAccountName with value 'username'
CN=username,OU=RemovedUsers,DC=test,DC=contoso,DC=org Unable to synchronize user CN=username, OU=Users,OU=Tier 2,OU=Admin,DC=test2,DC=contoso1,DC=org (SQL ID: 380) as it already exists in the target AD and the 'skip' user option is selected for this configuration.
This occurs when there is an account in the target Domain with the same "samaccountname" or "cn''...
In this case the recommendation is:
NOTE:
When you reset a profile, all objects that were previously pushed into SQL by the profile will be removed. If this includes devices, you will be prompted to confirm their removal, as this is not typical.
If you reset a profile without removing the objects "pulled" into the target by that profile, consider the relink and "Mark as ready to sync" options on the Matching Options settings page.
Resetting a profile is uncommon, especially if you are already performing production syncs. It is recommended to perform profile resets during the preparation or testing phase.
Resetting a user profile will also cause the passwords (legacy password sync) to be written to the target. If the user has changed their password in the target, it will be overwritten, which could lead to unintended consequences.