Microsoft 365 to Microsoft 365 (OneDrive/SharePoint) Considerations
When migrating files between Microsoft 365 tenants, Transend uses a combination of proprietary tooling and field-tested methodology to deliver maximum data fidelity. It is important to understand the various considerations when migrating data between OneDrive/SharePoint environments.
-
To execute a file migration, 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.
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.