See things differently? This article reflect Sharegate Desktop version 7.0 or greater. Manually update to the latest version or download the legacy Migration manual on our version page.
Map Users and Groups allows you to replace users that are not valid to existing ones on the destination site so everything works as intended.
- Once you have selected the action you want to perform from the Migration menu and connected to a source and a destination, select Mappings.
- Select the Users and Groups tab.
- Search for the user or group in the source and destination
- Drag and drop them in the appropriate spot.
- Click Save
Users, groups, and emails are 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 is 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".
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.
Sharegate can preserve orphaned users while migrating to Office 365 if a new user is assigned at the destination. To ensure that the defined mapping is applied, the migration has to be run in Normal Mode, otherwise Sharegate will use the default behavior.
You can import or export from from/to .sgum (Permission Level Mappings file type). This will allow you to save your mappings for future use.
- If when migrating from SharePoint to Office 365 you notice some users do not resolve when mapped, it is possible that they did not change their password at first login - causing them to not be provisioned properly.