User mapping

Cloud copy's User mapping allows you to replace users at the destination.

You may want to replace users or groups if they are invalid (i.e., orphaned users or groups or unresolved users or groups). A user or group can be invalid if they do not exist in the destination's Azure Directory.

Index

• How-to
• Default behavior
• Unresolved users or groups
• Import and export
• Considerations

How-to

1. Follow the steps to Copy an entire team as a new team or Copy channels into an existing team.
2. Select the User mapping tab when you get to the copy options page.
3. Use the search fields under Source users and groups to find the users you want to map at the source.
4. Use the search fields under Destination users and groups to match your source user to a destination user.
5. Once you finish creating your mapping, follow the steps to finalize your Cloud copy operation with your new user mapping settings.

Default behavior

Users and groups at the source site are automatically mapped to existing users and groups at the destination. You can find more about automatic mapping in the article, Users and groups association (automatic mapping).

Unresolved users or groups

Cloud copy allows you to resolve orphaned users and groups by mapping to Unresolved users and groups. Follow the steps in the How-to above to map unresolved users or groups to a specific user or group at the destination.

In most cases, your destination will support adding an orphaned user to a Person or group field such as Modified by in your teams' associated SharePoint sites. Only a few exceptions will cause Cloud copy to become unable to preserve unresolved users at the destination.

Cloud copy can preserve orphaned users because it uses the same technology as the migration tool's Insane mode.

When Cloud copy finds some elements only supported in Normal mode in a list or library, it migrates that whole list or library in Normal mode. When this happens, your users and groups unavailable in your destination's Active directory are not preserved. In that situation:

• The Modified by and Created by user fields will be filled with the migration account. You will get a warning in your Migration report.
• Any item with a custom Person or Group field will fail to migrate. You will get an error in your Migration report.

Considerations

• 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 ShareGate migration tool.

• 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 not to be provisioned properly.