Back to DriveShiftMigration workflow

A tenant-to-tenant Drive move, broken into controlled stages.

Use this page for the detailed product flow. The landing page stays clean; this route carries the operational depth.

01

Connect tenants

Validate the source and target Workspace tenant configurations before migration work begins.

02

Select folders

Browse the source Drive, select the folder to migrate, and choose its target destination.

03

Review the migration

Review folder contents, supported file types, permission mappings, warnings, and migration scope.

04

Migrate and review

Recreate the folder structure, copy supported files, apply mapped permissions, and review the final report.

Mock migration preview

Finance folder to target Workspace

Trial available

Source tenant

source.example.com

Validated
Finance
FY 2025
Reports
Forecasts
Shared Templates

Selected path: /Finance

Migrates to

Target tenant

target.example.com

Validated
Migrated Finance
FY 2025
Reports
Forecasts
Shared Templates

Selected path: /Migrated Finance

42

Folders discovered

1,284

Files discovered

386

Google-native files

29

Permission mappings

Credentials validated 29 mappings 5 warnings

Google-native handling

Google-native source fileExportTransferImport into target tenantNew target file ID

Permission controls

alex@source.com to alex@target.comOwner becomes WriterAdjusted
mia@source.com to mia@target.comEditor becomes WriterMapped
team@source.com to Viewer becomes Review required

42

Folders discovered

1,284

Files discovered

891

Files copied

343

Native files converted

812

Permissions applied

14

Warnings

7

Failed items

5

Unresolved links

Viewing illustrative `Summary` data. Real report content depends on tenant access, supported content, Google policies, and API limits.

Ready to validate with one folder?

Start with the bounded trial, then move to a folder-volume plan when your migration scope expands.

Login with Google