ShareGate Desktop carries your associated permissions during a migration, and will attempt to preserve their integrity from the source to the destination whenever possible.
This article explains what happens to your permissions during different scenarios when running a Copy Content migration, and how your users are associated between your source and destination.
Users and groups Association
This includes People and Group metadata fields, such as Modified by.
Users and Active directory (security) groups are matched with what's available in the destination's active directory.
SharePoint Groups are copied at the destination and populated with users if the source user can be resolved at the destination.
How we resolve users from the source to the destination
We look at the whole account name available, for matches to users at the destination through the SharePoint people picker.
Once we have a list of potential matches for your user, we go through the list of values below (in the specified order). We consider the account a match when we find the same values for one of these properties:
- Exact same account name
- Same normalized account name (without claims header)
- Same login and domain
- Same login
- Same login and domain (source login read from display name - this can happen when importing from file system because the account name is set as the display name)
- Same login (source login read from display name - this can happen when importing from file system because the account name is set as the display name)
- Same email address
- Same display name
- PrincipalType is not set or is a Security Group and same display name without domain
Note: If you're using any kind of redundant word in the account name, or if you have certain users that have multiple matching names, you might have to create a company-wide user mapping file to resolve that problem. You can extract the user information from your Active Directory, and use that data to generate a mapping file with PowerShell.
Permissions on Documents, Folders, and List Items
By default, we try to preserve the permissions as they are on your items.
If there are inherited permissions at the source, we will let them inherit the permissions from the list or library at the destination.
To keep the list or library permissions from the source, you must copy the entire list or library using Copy Structure.
You can chose not to keep the custom permission on your items using the Configuration menu in Copy Options. This will simply restore inheritance on all the items at the destination.
Note: Custom permissions are only copied for the items they are associated with. If you uncheck preserve custom permissions in your Copy Options, you will have to re-copy the items with the associated permissions again should you decide you want the permissions (you can't just copy permissions separately at a later time). Incremental copy will not bring over new permissions from the source since the permission change doesn't leave a timestamp (modified) on the item in SharePoint.