What Data is Merged?

What Data is Merged?

When merging two user profiles into one, you can choose which data is merged together:

• Course Enrollments. All enrollments will be moved from the source user to the destination user. If the two users are enrolled in the same courses, the highest score or most completed course will take priority during the merge. Please note that merging course data also merges training material tracking data, but does not merge the responses provided for by the source user in training materials (such as xAPI or SCORM) in order not to alter data validation. The user resulting from the merge will have to provide responses from scratch.
• Gamification. All badges, points, coins, and requests in the Rewards Marketplace will be moved from the source user to the destination user.
• Subscription Associations. Any subscription license assigned to the source user will be moved to the destination user. If the destination user does not belong to a branch with granted visibility for any license assigned to the source user, the merging of those licenses will be skipped and the license will still belong to the source user.
• Certificates. Any certificates obtained by the source user will be moved to the destination user. If both the source user and destination user have the same certificate, the most favourable (highest scoring certificate will be kept during the merge, and the other certificate will be deleted. This data is automatically merged if you merge course enrollments, otherwise, it is not merged.
• External Training. All external training records assigned to the source user will be moved to the destination user. This data is merged by default. You do not have the option to not merge it.
• E-Commerce Transactions. All e-commerce transactions from the source user will be moved to the destination user.  This data is automatically merged if you merge course enrollments, otherwise, it is not merged.
• User Profile Fields. All information from the source user profile will overwrite the information of the destination user profile, with a few exceptions:
  • Usernames will always be kept, never overwritten.
  • All source user branches will be merged with the destination user branches.
  • Managers and team members of the destination user will be kept

Important Notes about Merged Data

• Learning plan enrollments cannot be merged. While courses that are included in learning plans can have merged enrollments, the destination user will not be enrolled in the learning plans in which the source user is enrolled.
• Certifications are not merged automatically, they will be calculated for the destination user based on the status of the course that has been merged. The certification is triggered anytime the status is completed, merging a complete course to the destination user will trigger any related certifications and assign them accordingly.