Google Drive to Microsoft 365 (OneDrive/SharePoint)
Default behavior
User Drives
When migrating files between from Google User (My) Drive to OneDrive, the Copy operation only migrates files that meet specific conditions:
- The file lives in a user’s source My Drive
The following includes conditions when files are not migrated:
- Files that are in the “Shared with me” folder
- Files that are owned by the migrating user, but live in another user’s My Drive
- Files that contain corruption or content that Microsoft or Google defines as sensitive material and will not accept during migration
- Files or folders that contain sharing restrictions or permissions precluding migration access
Considerations
Transend’s file migration software preserves file and folder sharing permissions in most cases.
The following considerations are important to understand when migrating files from Google Drive to Microsoft 365 (OneDrive/SharePoint):
-
For permissions 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.
Ownership
Ownership of data in OneDrive is defined by the user who owns the drive. This is an inherited property that cannot be changed. Drives are migrated between pairs of source and target users, and this generally leads to the expected ownership structure after the migration.
Ownership of data in SharePoint is defined by the membership of the site’s Owners group. Ownership is defined during the provisioning process, when creating the target sites.
Advanced details
The following documentation provides granular details related to preserving file and folder sharing permissions during migration. This documentation includes scenario specific examples that define expected behavior for select common and edge cases.