Users and groups often must be mapped to existing users and groups on the destination site in order for everything to work as intended. The most common case is for permissions, but there can be other cases (for example, a workflow can assign a task to a user).
All the users and groups will be automatically mapped with existing users or groups on the destination site with the same account name (without considering the domain). If no match is found, the mapping will be done by display name. For example, domain1\john will be automatically mapped with domain2\john, since the account name is the same. Also, domain1\john will be automatically mapped with domain2\john-doe if both users’ display name is "John Doe".
- To change the default behavior or to specify mappings for users or groups that can’t be mapped either by account name or by display name, you can set your own users and groups mappings. Get started by clicking on Map users and groups.
- This will open the users and groups mapping window. In the left pane, search (1) for users or groups from your source that you wish to map to the destination. To use the search button (2), you must begin typing the name of the User or Group (even just one letter will work) and click the button. A list of all the Users or Groups found will then populate below the search pane.
- Drag and drop them to an available slot in the left side of the mapping.
- In the right pane, search for users or groups from your destination that you wish to map the source users or groups to.
- Drag and drop the destination users or groups to the desired mapping slot. The image below shows a user mapped to another one. Every reference to the user on the left in the source objects (either in permissions, groups, workflows, etc.) will be changed to the user on the right during the migration.
Unresolved users or groups
You can set a user or group to replace any user or group that existed at the source but doesn’t exist at the destination. A common scenario is between SharePoint environments where some users in the source have left the organization and don’t exist on the destination site.