Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
After you connect to Google, add the tasks (Drives) to scan and assess.
Select Add Drives and choose a method: to look for new users in Google Drives, target a single source path, or bulk upload the source paths using a CSV file. You can choose to automatically start scanning or do it later. However, all tasks must be scanned before you can migrate them.
After adding the tasks, highlight one or more tasks, and then select Scan from the menu bar if you haven't already.
After the scan completes, a table summary provides an at-a-glance overview of the source content and scan status.
Review the scanned tasks. Search for specific text, use a filter to refine the list, or download summary and detailed reports for further troubleshooting.
Important
The total number of rows (tasks) in the scan list cannot exceed 50,000.
Download reports
Scan summary report and Scan detailed reports are available to assist you in troubleshooting. Download the generated reports to investigate any possible issues that might block your migration.
Check the status code in Scan summary report to address task-level errors. For file-level errors, refer to the failure code (ResultCode) in the Scan detailed report.
Important
A Ready to migrate status doesn't mean every item passed the scan. Review item-level failures and unsupported content. Orphaned Google files aren't scanned or included in reports, so reconcile the required source inventory separately and decide how to handle excluded content.
Drives with large amounts of data
After scanning, use the reports to identify large drives and plan their migration with the content owners.
A migration task (Google Drive) shouldn't exceed 100,000 items or 1 TB of data. To enable faster transfers, Google Drives with large data sets should be divided into smaller migration tasks based on their root folders.
To split a Drive into multiple migration tasks, follow these steps:
- Inventory the required subfolders and any files stored directly in the Drive root. Plan a destination for each task that preserves the intended folder structure. Subfolder tasks don't cover files stored directly in the root.
- In Migration Manager's scan list, remove only the original whole-drive task after your replacement plan accounts for all required content. Don't delete the source Drive or its files in Google Workspace.
- Select Add Drives from the command bar.
- In the side panel that appears, select Multiple specific Drives.
- Download and edit the provided CSV template to divide the user into multiple tasks. For example:
LargeDrive01@contoso.com/folder01LargeDrive01@contoso.com/folder02LargeDrive01@contoso.com/folder03LargeDrive01@contoso.com/folder04
- Save the updated CSV file and upload it to create the divided migration tasks.
- Scan the replacement tasks and reconcile their coverage with your inventory. When you assign destinations, preserve each subfolder's intended location. For example, map
folder01andfolder02to separate destination folders rather than unintentionally combining their contents in one folder.
Important
If required files remain directly in the Drive root, don't remove the whole-drive task until you have a migration plan that covers them. Avoid overlapping source tasks or conflicting destination paths. Resolve any coverage gaps before starting migration.