Onboarding | Project Phases | Best Practices | Glossary of Key Terms

File Migration Methodologies

Transend’s file migration methodologies are designed to ensure an efficient cutover, with an optimized user experience. As a result, we offer two file migration methodology options for User Drives, and a Single-pass methodology for Shared/Company Drives.

  • User Drives: OneDrive, Google User (My) Drives, Dropbox user accounts
  • Shared Drives / Company Drives: SharePoint, Google Shared Drives, Dropbox company/shared accounts

User Drive methodologies

Staged Migration

For most projects, this is the recommended file migration methodology.

The Staged Migration methodology is designed to ensure the most recent files (modified within the last 12 months) are migrated to target user drives in advance of the cutover. This ensures that after the cutover is performed and users first log into the target drive (just after the cutover), files modified within the last 12 months are already there. Once the cutover is performed, Transend then proceeds to migrate all remaining files from the source.

  • Stage-1 – Files modified within the recent 12-month period (migrated pre-cutover)
  • Cutover – Update DNS records to change mail routing to target (Users “Go Live” in target)
  • Stage-2 – Stage-1 delta job (migrated post-cutover)
  • Stage-3 – Files modified more than 12 months ago (migrated post-cutover)

Important duplication considerations:

When performing a Staged migration, the following duplication considerations are important to understand:

  • If a source file’s body is modified by a user after Stage 1 but before Stage 2, the most recent version of the source file will be migrated to the target and will override the previously migrated version, so only the most recent version of the source file exists in the target.
  • If a source file is renamed or moved to a different folder after Stage 1, but before Stage 2, the file will be duplicated in the target.

Note: the Staged file migration option was added to Transend’s offering July 21, 2025.

Single-pass migration

Alternatively, Transend can perform a Single-pass file migration after the Cutover and the mailbox migration (if in scope) is completed.

  • Cutover – Update DNS records to change mail routing to target (Users “Go Live” in target)
  • Mailbox migration – Completed in full (if in scope)
  • Single-pass file migration – Perform Single-pass migration of all user files in scope

The benefit of the Single-pass migration is to ensure mail routing is updated as quickly as possible, so that users can begin working out of the new platform ASAP, or you’re not able to prevent users from renaming/moving source files during migration and want to eliminate the potential of duplication. The downside is that it takes longer for the migration to complete after users are “live” in the target platform.

Shared Drive methodology

When migrating files/folders between Shared Drives (Google Shared Drives, SharePoint, Dropbox, Local file share), Transend performs a Single-pass file migration after the Cutover. The sequence of events is as follows:

  • Cutover – Update DNS records to change mail routing to target (Users “Go Live” in target)
  • User account migration deltas (mailbox & drive) – Completed in full (if in scope)
  • Single-pass Shared Drive file migration – Perform Single-pass migration of all Shared Drive files in scope

Note: File/folder sharing permissions are not migrated between Shared Drives. It is recommended after the Shared Drive migration is complete customers recreate sharing permissions by adding members to the appropriate Shared Drives and/or folders.

Other Considerations

The following considerations are important to understand so you can communicate expected file migration behavior to users.

Copy operation

By default, Transend will create replicas of source files and copy them into the target drive. Files will continue to exist in the source drive after migration. All files will be migrated into the target drive as Microsoft file formats.

Note: The only exception is the available Move operation when migrating between Google Workspace tenants. The Google Drive-to-Google Drive Move operation requires additional fees.

Sharing Permissions

Unless it is specifically defined otherwise in your Project Plan, it is Customer’s responsibility to recreate file and/or folder permissions in the target after the file migration has completed.

Transend does not migrate file/folder sharing permissions between Google Shared Drives and/or SharePoint document libraries (only available in Enterprise Professional Services projects).

Select file and folder sharing permissions can be migrated between User Drives (My Drive/OneDrive), to be defined in your Project Plan. Shortcuts must be recreated in the target by Customer.

If your Project Plan defines that sharing permissions are to be preserved in target User Drives, the following considerations are important to understand:

Platform specific considerations:

Microsoft OneDrive notifications

By default, Microsoft 365 sends email notifications to users when files they own in OneDrive are shared with external users. If permissions are maintained when migrating files to OneDrive, this can cause a notification storm being sent to the OneDrive owner during migration.

To prevent this notification storm during migration, Transend will temporarily disable notifications in the target tenant by running a PowerShell command to disable the “NotifyOwnersWhenItemsReshared” setting.

When your project is complete, Transend will re-enable the “NotifyOwnersWhenItemsReshared” notification setting back to its original state. If you do not want Transend to temporarily disable notifications in your tenant, please contact your project manager.