File Migration
Transend supports file migration as a service only, and does not license software that supports file migrations for self-service usage at this time. File migrations between the following platforms are supported as either an Enterprise Professional Service or Express Migration Service:
- Google Workspace
- Google User (My) Drives
- Google Shared Drives
- Microsoft 365
- OneDrive
- SharePoint
- Windows file share
Permissions that migrate
Transend’s file migration software preserves file and folder sharing permissions in most cases, with select exceptions depending on the migration scenario and specific preferences.
- Direct permissions – permissions applied to a file. These permissions migrate to the target file.
- Inherited permissions – permissions applied to a folder and propagated to folders and files inside that folder. These permissions migrate to the target folders and files.
Note: Direct and Inherited permissions are maintained even if email addresses are changing during migration.
Permissions that do not migrate
The following permissions are supported through user or group provisioning (applying members to a drive) or resharing (resending) links.
- Membership permissions – permissions applied at the drive root. For user drives, this means the owner of the drive. In Google Shared Drives, this is via the Manage members dialog. In SharePoint document libraries, this is via the various default SharePoint groups at the site level. These permissions do not migrate, and instead are set when adding users or groups as members of the target drive or document library.
- Link permissions – permissions applied via a sharing link. These apply only to Microsoft 365. Google Workspace also has sharing links, but these are public links that aren’t associated with specific permissions.
Important considerations
The following file migration sharing/permissions considerations are important to understand:
To Google Drive:
To Microsoft OneDrive/SharePoint: