{"id":4249,"date":"2016-07-20T14:19:30","date_gmt":"2016-07-20T08:49:30","guid":{"rendered":"http:\/\/www.vyapin.com\/blog\/?p=4249"},"modified":"2021-05-14T13:27:17","modified_gmt":"2021-05-14T13:27:17","slug":"preserve-the-user-value-during-document-migration-to-sharepoint","status":"publish","type":"post","link":"https:\/\/www.vyapinsoftware.com\/blog\/preserve-the-user-value-during-document-migration-to-sharepoint","title":{"rendered":"Are you migrating documents to SharePoint? Preserve user value!"},"content":{"rendered":"

This article describes the steps involved in preserving the users during SharePoint content migration<\/a> <\/strong>using Vyapin\u2019s XPlica product<\/strong>. XPlica will help you preserve the user(s), if the user(s) are still available in the organization and replace the user(s) with any other alternate user, if the user is no longer with the organization.<\/p>\n

The users \/ groups assigned in source SharePoint will be automatically mapped by XPlica with the existing users \/ groups on the target SharePoint site during migration. The mapping will be done automatically based on the properties listed below (in the same order), if it finds a match in property value.<\/p>\n

# Account name<\/em><\/p>\n

# Email address<\/em><\/p>\n

# Display name<\/em><\/p>\n

For example,<\/p>\n

    \n
  1. SOURCEDOMAIN\\john will be automatically mapped with TARGETDOMAIN\\john, since the account name is the same.<\/li>\n
  2. SOURCEDOMAIN\\john will be automatically mapped with TARGETDOMAIN\\johnson, if both users\u2019 email address is “John@DOMAIN.COM”.<\/li>\n
  3. SOURCEDOMAIN\\john will be automatically mapped with TARGETDOMAIN\\john-doe, if both users\u2019 display name is “John”.<\/li>\n<\/ol>\n

    One of the biggest challenges for an organization is to retain the original author or contributor to the various digital assets created by employees, even after they leave the organization. Their contribution in the SharePoint must be retained or archived, even when the organization is upgrading their SharePoint environment. It is plenty more of work for IT Administrators (or other business users) who are performing the content migration to keep track of such users\u2019 contribution in SharePoint when migrating to a new SharePoint environment. To simplify such migration challenges, XPlica provides an ability for IT Administrators to map such employees \/ users who are not available in Active Directory with any one of the available or current users who have inherited their role.<\/p>\n

    For example, <\/u><\/p>\n

    \u2018John Doe\u2019 has left the organization, obviously XPlica won\u2019t find the user in Active Directory<\/strong><\/a>, since the user account would have been deleted or disabled. What happens next? By default, \u2018John Doe\u2019 will be mapped to the user who is performing the migration.<\/p>\n

    The immediate question is \u201cHow do I replace a user who has left the organization with another user in SharePoint, instead of mapping it to the user (or service account) performing migration by default)?\u201d<\/p>\n

    You can use the \u2018All Unresolved Users\u2019 macro in \u2018User \/ Group Mapping\u2019 template in XPlica to map such unresolved users from source SharePoint with a particular user account in target as stated below:<\/p>\n