While the default options are recommended for the majority of users, CloudM Migrate gives users the ability to customise their migration experience. The following are the advanced options available to those migrating to Google Workspace.
- Archive Inbox Email - Do not place migrated email from the inbox into the inbox within G Suite. Instead the email will have a label of 'Migrated Email' applied.
- Apply Inbox Label to Sub-Folders - When a message from the source system was in a folder in the inbox, create the message with both 'Inbox' and 'Folder Name' labels. Set to False to just create the folder label.
- Modify Sent Address - For sent messages, if the sender does not match the email address of the destination account, modify it to match. This is to allow for sent items to display correctly in the G Suite interface. Default is true.
- Email Transfer Delay - Specify the number of milliseconds to wait between sending messages.
- Email Import Thread Count - Set the number of threads that will be used per-user to migrate email to Google Workspace.
- Maximum Batch Count - Specify the maximum number of messages in a single batch. Specify 0 to let the tool automatically allocate batches. Only applicable for immediate migrations.
- Use Limited Scopes – for email migrations use Limited Scopes. This requires the following scopes to be enabled : 'https://www.googleapis.com/auth/gmail.labels' and 'https://www.googleapis.com/auth/gmail.insert'
- Explode Message Labels - By default, if an email message is contained within a folder structure the label applied to that message will be the same as the folder structure (e.g. 'Personal Folders/My Folder/My Other Folder'). Setting this option to true will create a label for each of the folders (e.g. for the case described, labels of 'Personal Folders', 'My Folder' and 'My Other Folder' will be applied).
- Create Sub Labels - Create all sub-labels for labels within a message. For example, if a message has the label 'toplevel/midlevel', create both 'toplevel' and 'toplevel/midlevel' labels. This is specifically designed for use with nested labels.
- Migrate to 'My Contacts' - Migrate personal contacts to the 'My Contacts' group rather than only to 'All Contacts'.
- Send Individual Contacts - This should generally be left to true, while slower than batch importing its much more reliable.
- Force Appointment Acceptance - Set this to true to force all appointment recipients' attendance as confirmed.
- Force Busy Status - Force busy status when appointments have been tentatively accepted.
- Appointment Privacy - Set the visibility of all appointments. Original will use the privacy setting from the source system, while the other settings will override the original setting and set the specified visibility.
- Maximum Attendees - Set the maximum number of attendees for any migrated appointments.
- Default Calendar Timezone - Set the default calendar timezone to use for recurring appointments which have no timezone set in the source system and where the target Google calendar is in UTC.
- Send Individual Events - Send appointment events as individual items rather than as a batch. Performance is slower than in batches, but may help with some rare issues with rate limiting.
- Color Categorized Appointments - If the appointment had a category in the source system, apply a colour to all appointments of that category.
- Appointment Attachment Document Sharing - When migrating appointment attachments to Drive, choose whether the attachment should be shared with the appointment attendees.
- Migrate Attachments - Migrate appointment attachments to Google Drive and share with attendee.
- Migrate Attachments Folder - Migrate appointment attachments to the specified folder when 'Migrate Attachments' is enabled.
- Exclude Appointment Attachment Extensions - Specify the list of file extensions of attachments that will not be migrated. Leave empty to migrate all attachments.
- Use Cached Item Mappings - Use cached item mappings when migrating to Drive. (Not applicable for Google to Google migrations).
- Preserve Modified Date - Attempt to preserve the modified date during a migration.
- Allow Non-Google Sharing - Allow permissions to be added for users without Google accounts by sending notification emails to those users. Note this can result in many emails being sent to any non-Google addresses.
- It's important to note that a Google account can be set up using any address. You can have a yahoo.com, outlook.com etc Google account email address. Therefore, if you have not enabled this setting, and you see yahoo, outlook or other seemingly non-Google addresses in your permissions post-migration, this will be why.
- Allow Alternate Item Ownership - 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. Normally this should be set to false unless a change in ownership is permitted and has not been performed by using address mappings.
- Maximum Results Per Request – the limit on the number of results returned when listing files using the Google Drive API.
- Batch Permissions - Use batching to provide faster, but potentially more error prone, Google Drive migrations.
- Skip Post Processing of Existing Items - When running delta migrations on previously migrated items, skip post processing of existing items. This affects patching of permissions, parent folder change, starred and last updated date. Items that have been explicitly updated will still be processed. Setting this option is potentially dangerous and it is recommended that it should only be enabled on the expressed instruction from a member of the CloudM Support Team.
- Convert Text - Where possible, convert text and word documents to the Google Documents format.
- Convert Spreadsheets - Where possible, convert spreadsheets to the Google Documents format.
- Convert Presentations - Where possible, convert presentations to the Google Documents format.
- Convert Drawings - Where possible, convert drawings (*.wmf) to the Google Documents format.
- Convert OCR - Where possible, convert images using OCR.
- Shared Drive File Permissions - When adding permissions to files within Team Drives choose where these permissions will be applied. Choose from 'File' (the default), 'Root' (where all permissions will be applied on the Team Drive itself and thus inherited down the whole tree) or 'None' (no permissions will be applied)
- Shared Drive Folder Permissions - Team Drive folders cannot directly have permissions. Choose whether to apply permissions that apply to folders from the source at the root of the Team Drive, or not at all.
- Shared Drive Same Domain Migration Operation - When migrating from a Google Drive folder into a Team Drive choose whether to copy the files, or to move them. Note in the case of a move, the skeleton folder structure of the source folder will remain.
- Migrate Shared Drive Members - If this option is enabled CloudM Migrate will get get shared drive members and their permissions from the source, run their email addresses through configured domain replacements and assign them as members to the destination shared drives. If the list of Shared Drive Members (after domain replacements) is intertwining with the list of Shared Drive Default Managers - we will prioritize the list of members, meaning that it won't remove the Shared Drive Members from the destination, even if their email addresses were also in the 'Shared Drive Default Managers' list and 'Remove Shared Drive Default Managers' was enabled. If a member had an organizer role on the source shared drive, it will assign them an Manager role on the destination.
- Shared Drive Default Managers – optionally, specify a list of existing user email addresses that will be assigned as Managers to Shared Drive being migrated to. These Manager accounts will then be used to improve the performance of the migration. In the default case the Google Workspace admin user account will be used to perform the migration to Shared Drive, but specifying multiple users here improves throughput by utilizing multiple organizer accounts simultaneously.
- Remove Shared Drive Default Managers - Enable this option to remove any users specified in Default Managers.
- Check Users/Resources/Groups Exist - Set this to false if you do not want to check if users, groups or resources exist in G Suite (useful for testing exporting without creating accounts in G Suite).
- Create Users/Resources/Groups - If users, groups or resources (supported source systems only) are not present within the Google domain, create them. If users have not been pre-created within the Google system then this can be set to true to have the migration tool create the users. If the users have not been pre-created and this is set to false then the migration process will fail. Note: Setting this to true requires that the Admin SDK is enabled for the Google domain and also that all details are provided for each user, including name, given name, family name and password. Failing to provide any of these details will cause the creation process to fail for that user. It is generally recommended that users are pre-created in the Google domain before processing with the tool. For resources and groups, only the Resource/Group Name (and Import/Export Names) are required.
- Check Services Enabled - When running the 'Check Users' action, also check if the selected Google services for that user are enabled.
- Change Password On Login - Force users to change their password on next login.
Transfer and Performance
- Migration Base URL 1.0 - The base URL for email migration using v1 of the email migration API. This should only be changed for specialized migration scenarios and for normal migrations should not be altered.
- Migration Base URL 2.0 - The base URL for email migration using v2 of the email migration API. This should only be changed for specialized migration scenarios and for normal migrations should not be altered.
- Timeout - The time in milliseconds that the tool has to complete sending a transaction to Google before an error occurs. This should be set high enough so that large amounts of data can be sent (further description is available in ‘Migration Strategies’). If a transaction fails using the provided timeout, it will be re-attempted using a larger timeout. While errors occur this will continue with increasing lengths of timeout, up to the retry count. It is better to set this to a very high value to ensure requests get through.
- Maximum Batch Count - The number of items that will be sent in a batch when transferring contacts and calendar items.
- Retry Count - The number of times a transaction with the Google servers will be retried if it fails. Note: A transaction could fail for one of a few reasons. If the transport layer fails, that is a transaction could not get through to the Google servers or the transaction times out, then the transaction will be attempted again until the retry count is met – with an increasing timeout value each time. Another possible reason for failure is that the client is sending too many requests per second. In this case, an exponential backoff system is employed where the tool waits for a period before retying any failed transactions (or parts of transactions).
- Lock Retry Count - The number of times a failed distributed lock will be attempted before aborting.
- Modify Request - Leave at the default unless instructed by support.
- Drive Locks From Listed Users - Use only users from the user list to obtain locks for Drive files when migrating in multi-server configurations. You must always perform migrations with the same user list at any one time to use this option or duplicate items will be migrated.
- Multi-Server Drive Migration - Use distributed locking to allow for Drive migrations to be performed from multiple servers. This can be disabled if using only one server for migration.