Edit

Permission settings in Migration Manager

  • Article

Review your settings to ensure that the same users with access to files, folders, and metadata will continue to have access after migration.

Migrate permissions

By default, Migration Manager migrates folders permissions. File permissions aren't migrated, and destination files inherit parent folder permissions.

File permissions migration can be enabled by Project settings:

project settings

Once enabled, the destination file permissions will be the same as they are in source. This ensures that migrated files are shared with the same users as before migration.

Note

Migrating file permissions may slow down your migration process.

Map identities

Identity Mapping is when you match the user and group identities that have access to your source environment and map those identities to Microsoft 365 user and group identities. This process is important to migration. If identities aren't properly set up prior to migration, it can result in users losing access to content. It can also result in information being incorrect at the destination.

Learn more about identity mapping for different cloud scenarios:

Note

When migrating Google shared drive permissions, we recommend you do the following:

  • Recreate a Microsoft 365 group that has the same memberships as the Google Drive group. You can either create a new group, or edit the group linked to the Team site which you designate as the migration destination of the Google shared drive.
  • In the Map identites setting, map the original Google Drive group of the shared rive to the Microsoft 365 group.