The Migration Readiness Scan is an optional but highly recommended feature, especially when you've made numerous changes to your CloudM Migrate configuration. This scan helps identify potential issues before they impact your migration. You can only run one Migration Readiness Scan at a time.
What the Scan Includes
The Readiness Scan performs several crucial checks:
- Configuration Settings Review: It examines where changes have been made to general and advanced migration settings (i.e., those differing from the default values) and suggests any potential issues these settings could cause.
- Platform Connection Verification: It scans both your Source and Destination platforms to ensure that all connections work properly.
- Limitation Flagging: It flags any additional limitations or potential conflicts, allowing you to resolve issues before your migration begins.
Exporting the Readiness Report
Once the scan is complete, you can easily export the results:
- Select the Export option.
- The report will be exported in CSV format and saved in your computer's Downloads folder.
Readiness Scan for Google Drive Migrations
Google Drive to Google Drive migrations can be particularly complex due to the intricate nature of Drive permissions, ownership, and folder structures. CloudM Migrate provides many options to configure these migrations to your specific needs.
Here are some common scenarios that benefit from a Readiness Scan:
- All your users are moving from one domain to another.
- Some of your users are moving from one domain to another, and you want to migrate only the items belonging to the migrating users.
- All your users are moving, but you need to rename users and groups.
- Some of your users are migrating now, and some will migrate later.
Depending on how you configure CloudM Migrate, some scenarios require specific configuration options and may also necessitate careful mapping of addresses and domains. In all cases, you need to ensure that all appropriate users, groups, mappings, and settings have been configured correctly for your migration. The Drive Readiness Test, which is included as part of the overall Readiness Scan, is designed to help you verify your configuration.
One of the key functions of CloudM Migrate during a Google Drive to Google Drive migration is to ensure the fidelity of the folder structure from the perspective of the migrating user. In some cases, this might involve creating folders that do not belong to the original user (for example, if a user is not being migrated). If you change settings or perform migrations with one setting followed by another, duplicate folders can be created. The Drive Readiness Test inspects your domains, users, groups, the user list, address replacements, and your configuration settings, highlighting any potential issues with the configuration. You should run a Drive Readiness Test before performing a Google Drive to Drive migration to ensure you achieve the desired results.
Your domains, users, groups, and settings will be scanned, and any issues will be reported directly in the user interface. Additionally, detailed reports are available in CSV format, allowing you to inspect individual items that have been flagged.
By default, if you have any warnings from the Drive Readiness Test, you will not be able to start the migration. This can be overridden with a checkbox if you are certain the warnings will not affect your migration. However, it is strongly recommended to check all warnings and inspect the reports thoroughly to ensure your configuration is absolutely correct before proceeding.
Tests Performed by the Drive Readiness Test
The Drive Readiness Test performs checks across several critical areas:
Configuration Settings
Some configuration settings in CloudM Migrate should only be used in specialized scenarios. The Drive Readiness Test checks the usage of these settings and provides feedback on their expected results. It also flags settings that should not be combined. The settings checked include:
- Migrate All Drive Items:
- Behavior: This setting should normally be enabled. If set to false, only items owned by the migrating user will be migrated, and all folders within their folder structure will become owned by the migrating user. This is almost always not recommended.
- Warning: If this option is used and then subsequently disabled, and another migration is performed, duplicates will likely be created.
- Migrate Items Only from Listed Users:
- Behavior: When this is selected, files will be migrated only from the users specified in your user list. Folder structures within the migrated users' MyDrive will be maintained by transferring ownership of any folder not owned by any of the listed users to the migrating user first, to process the folder.
- Warning: If this option is used and then a migration is subsequently performed without it, and/or more users are added to the user list, duplicate folders for some users will be created. If you are migrating all your users, this option should not normally be used.
- Recommendation: If you do use this option, ensure that your user list, address replacements, and groups are fully correct before the first migration. Exercise extreme care with this setting, especially if migrating an entire domain.
- Migrate Contents of Non-Owned Folders:
- Behavior: Normally, files owned by other users will be migrated (as the owning user) if the file appears in the MyDrive of the migrating user and the migrating user owns the folder. This option will migrate all files within the migrating user's My Drive regardless of who owns the folder. Setting this to true will decrease performance substantially. This option may be required if you are migrating a subset of users but need copies of all items within their MyDrive regardless of ownership. It should normally be disabled.
- Warning: If this option is used and then disabled, and another migration is performed, duplicates will likely be created. This option cannot be used together with 'Migrate Items Only from Listed Users'.
- Allow Alternate Item Ownership:
- Behavior: Setting this option to true can cause ownership of items to change if the item owner is not present, is suspended, or has Drive disabled in the destination.
- Recommendation: Normally, this should be set to false unless a change in ownership is explicitly permitted and has not already been performed using address mappings.
- Overwrite Updated Documents:
- Behavior: If this is set to false, documents that have been changed in the source since the last migration will not be re-migrated on subsequent migrations. This setting does not affect permissions (permissions are always repatched) or deletion (if a file is migrated, then deleted at the source, and there is a subsequent migration run, it will remain in the destination).
- Recommendation: This should normally be enabled.
Source and Destination Sharing
Tests are made to ensure that items can be shared between source and destination domains. This test only checks that sharing is enabled but does not check for whitelisting of specific domains. If you have explicitly whitelisted domains for sharing, you can ignore any warnings here.
User List
The tests check that you have an entry in the user list for every user in the source domain. There may be scenarios where you are not migrating all users, but it is useful for this to be flagged. Any users that are in the user list but are not found in the source domain will also be flagged. If you are not migrating all users, it may be possible to ignore this warning.
Address Replacements
If you have used an address replacement file, it is recommended to provide replacements for all items so there is no ambiguity as to how an address will be replaced. The tests will ensure that if you have provided a replacement file, an entry is present for every user, group, and domain. See also [address replacements (Link to CloudM KB article)] for an overview of how address replacements are applied.
Domain Users
All users and groups in both source and destination domains are obtained, and the full list of users is checked (including the application of address replacements) to ensure that all users and groups in the source have a matching user or group in the destination. If you have not mapped all items, those that have not been mapped will be available in the CSV report generated by the tests. The test cannot ensure you have mapped users to the correct corresponding user in the destination; it can only ensure they have been mapped to a valid user.
Groups and Group Membership
As permissions can be allocated via groups within Drive, it is important to ensure all groups and group membership are correct. Groups and their membership can be migrated using CloudM Migrate, and it is recommended that this is done as a separate step, prior to data migration. The Drive Readiness Test will scan all groups in the source and destination, along with their membership, and ensure that everything matches up (taking into account any address replacements). Any items that do not match will be written to a CSV file with details of the inconsistent or missing items.
Reports
The Readiness Scan provides feedback directly in the user interface, and CSV files are written containing details of any items that do not match, are missing, or are inconsistent. You should thoroughly inspect all warnings and ensure that you have addressed any required issues.