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.
- Click Copy.
- Selected the action you want to perform from the Copy menu and connect to a source and a destination.
- Click in the top right corner.
- 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.
Note: If you wish to create mappings for many users click here.
Users and groups are automatically mapped with existing users and groups on the destination site. You can find more about automatic mapping in the Users and groups association article.
Users and groups that are set to inactive in Active Directory cannot be resolved in SharePoint and will be considered unresolved during the migration.
The users and groups you do not specify in your mappings are mapped automatically by the application.
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.
ShareGate Desktop will preserve orphaned users while migrating in Insane Mode to Microsoft 365. To ensure that the mapping of the unresolved users and groups is applied, the migration has to be run in Normal Mode, otherwise, ShareGate Desktop will consider the users as resolved since they can be preserved in Insane Mode.
For the Modified By and Created By user fields, unresolved users and groups will be replaced by the migration account when they are not mapped (you will get a warning in your migration report).
Import and Export
You can import or export from/to SGUM ( ShareGate User Mappings file type). This will allow you to save your mappings for future use.
Note: When migrating from SharePoint to Microsoft 365, if 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.