Using the Migration Readiness Scan
The Migration Readiness Scan is an optional but highly recommended feature. It is particularly useful when you have made significant changes to your CloudM Migrate configuration, as it helps identify potential issues before they impact your live migration.
Limitation: You can only run one Migration Readiness Scan at a time.
What the Scan Includes
The Readiness Scan performs several crucial checks to ensure a smooth transition:
- Configuration Settings Review: Examines changes made to general and advanced migration settings (those differing from default values) and flags potential conflicts.
- Platform Connection Verification: Scans both Source and Destination platforms to ensure all connection strings and permissions are functional.
- Limitation Flagging: Identifies known platform limitations or environmental conflicts that may hinder data transfer.
Readiness Scan for Google Drive Migrations
Google Drive to Google Drive migrations are uniquely complex due to intricate permission inheritance, file ownership, and nested folder structures. The Drive Readiness Test (included within the general scan) is specifically designed to prevent common pitfalls such as duplicate folders or broken sharing links.
Common Scenarios Benefiting from a Scan:
- Full domain-to-domain migrations.
- Partial migrations (moving specific users while retaining their items).
- Migrations involving user or group renaming.
- Phased migrations (migrating users in batches).
Tests Performed by the Drive Readiness Test
1. Configuration Settings
The scan checks for "specialized" settings that, if used incorrectly, can cause unintended results. Key settings monitored include:
| Setting | Recommended State | Risk / Behavior |
|---|---|---|
| Migrate All Drive Items | Enabled | If disabled, items not owned by the user may have ownership forcibly changed or cause duplicates in future runs. |
| Migrate Items Only from Listed Users | Disabled (for full migrations) | Useful only for subsets. Using this for full migrations without careful mapping leads to folder duplication. |
| Migrate Contents of Non-Owned Folders | Disabled | Enabling this significantly decreases performance. Cannot be used with 'Migrate Items Only from Listed Users'. |
| Allow Alternate Item Ownership | Disabled | Only enable if you explicitly want to reassign ownership for suspended/missing users. |
| Overwrite Updated Documents | Enabled | Ensures changes made at the source during the migration period are synced to the destination. |
2. Environment & Mapping Checks
- Source and Destination Sharing: Verifies that external sharing is enabled on both domains. Note: This does not check specific domain allowlists.
- User List Consistency: Flags any user in the source domain not present in your migration user list.
- Address Replacements: Ensures that if an address replacement file is used, every user, group, and domain has a corresponding entry to avoid mapping ambiguity.
- Group Membership: Scans groups and members to ensure they exist in the destination. CloudM recommends migrating groups as a separate step before data migration.
Reviewing and Exporting Results
By default, you cannot start a migration if the Drive Readiness Test returns warnings. While this can be overridden via a checkbox, it is strongly recommended to resolve all issues first.
How to Export the Readiness Report:
- Wait for the scan to complete in the CloudM Migrate interface.
- Select the Export button.
- The report will download as a CSV file to your local Downloads folder.
Detailed CSV reports contain specific item-level information for flagged users or folders, allowing for granular troubleshooting.