Google Workspace 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.

  Note that source addresses that are not mapped will retain their original addresses, which are by definition valid in the global Google namespace. Such addresses will be migrated, which may not match expectations.

• 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.

• When performing a Move operation, sharing links are preserved and continue to work for recipients of the link. Because the file and URL remain the same, nothing changes for recipients. With the Copy operation, sharing links will need to be sent out to users again because Google doesn’t know who the links have been sent to.

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 should be mapped to the primary email address.

• 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.

• 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