Microsoft 365 Drive Migration User Guide

Migrating to a Google Workspace tenant

Important considerations

• To migrate, a given source address must map to an address that exists in the global Google namespace, which includes all domains associated with all Google tenants and gmail.com addresses.

• Only addresses that exist in the global Google namespace can be migrated. Attempting to add a non-Google address requires sending an email invitation, and only 50 such invitations can be sent per day per day.

• Permissions can be surfaced by Microsoft APIs as UPNs, primary email addresses and aliases. As a best practice, format the translation table so each of these identifiers resolves to a valid address in the Google target tenant.

• Source link permissions are not supported.

• The Can't download permission is not supported. This property only exists when granting permissions on a SharePoint folder.

Examples

Migrating to a Microsoft 365 tenant

Important considerations

• To migrate, a given source address must either map to a valid object in the target tenant or have a domain part that is external to the target tenant.

• Permissions can be surfaced by Microsoft APIs as UPNs, primary email addresses and aliases. As a best practice, format the translation table so each of these identifiers resolves to the primary email address in the M365 target tenant.

• Source link permissions are not supported.

• External users are added to a folder or file’s ACL with a link permission, but the link needs to be mailed to the external user manually.

• The Can't download permission is not supported. This property only exists when granting permissions on a SharePoint folder.

• Only Unified (Modern) groups can be added to a file’s ACL in Microsoft 365. Attempting to add other types of groups results in an error.

Examples