This section describes settings that are common to all source and destination platforms.
For more information about Address Replacements, please read the article.
- Replace Usernames – Replace any re-mapped usernames from the users tab, when migrating the items specified in 'Domain Replacement Types' in Common settings. If this option is disabled and replacements are required, explicit mappings for email addresses and domain names should be provided via the other settings in this section. Only addresses that belong to source domains are automatically mapped. When migrating from G Suite the source domains are automatically identified, but when migrating from other sources you should specify the domains in the next setting: Address Domain Replacements
- Address Domain Replacements - if migrating from one domain name to another, specify the domain names that should be replaced and the value with which they should be replaced with. For example, when migrating from example.com to domain.com, you should provide example.com and domain.com in this setting. If migrating from one GSuite domain to another, domain replacements are performed automatically.
- Address Replacements (File) – use this option to provide an explicit list of email addresses to be mapped as part of a migration. If performing domain consolidation or if you have other specialized requirements then this option can be used to map any source email address to any other address. Addresses should be mapped using a simple CSV file containing two columns, the first for the address to be replaced and the second the replacement address.
- Replace CSV Addresses Only - Perform email addresses and domain replacements from the CSV file specified in 'Address Replacements (File)' and do not attempt to perform replacements using any other method. This can be useful when partially migrating users from a source domain and only those specified in the CSV file should be replaced. Note that if you use this option you should be careful to specify all replacements, including domain names and group addresses in the CSV file. If an address or domain is not matched from the CSV and you have this option on, the address from the source will be left unchanged.
- Non Matched Address Replacement Behaviour - When 'Replace Usernames' is enabled, and when a CSV has been provided for address replacements, set the behaviour when an address has not been matched (and therefore replaced) from either the CSV file or from the users specified on the users tab. Either replace the domain name based on any domain mappings provided (or to the destination domain in the case of Google to Google), or leave the original address unchanged.
- All Calendars – Both Exchange and GroupWise can contain primary and secondary calendars for users. By default, all of these calendars will be transferred to the destination system, with the primary calendar being imported into the primary calendar and secondary calendars being created as secondary calendars within the destination system. Unless there is a specific reason to do so, it is recommended to leave this setting as true.
- Shared Calendar Information - if users have shared calendars with other users in the domain then this information can be transferred to the destination system. The rights of users with respect to shared calendars can be different between Exchange/GroupWise and the destination systems and as such the resultant rights that a user has may be slightly different. Importantly however, the nature of the access is not changed, so a user that only has read access in Exchange or GroupWise will of course only have read access within the destination system.
- Appointment Subject Tag – optionally specify a value that will be appended onto the end of all appointment subject titles. A space will be automatically inserted between the original appointment title and the tag. For example, if you specify ‘[Migrated]’ as the tag and the original appointment was titled ‘Meeting with Gregg’, then the resulting title will be ‘Meeting with Gregg [Migrated]’. Leave this option empty to keep the original appointment title.
- Prefix Common ID – prefix the common ID (the ICAL UID) when migrating appointments. Turn off when performing co-existence.
- Common ID Prefix Value – specify the prefix to use if prefixing the common ID. Keep constant through a migration.
- Send Calendar Sharing Notifications - Send notifications on calendar sharing change
- Address Book Groups – set to True to create groups based on users address books (GroupWise and Exchange only)
- Skip Quest Migration Manager System Contacts - do not process contacts that may have been created with Quest Migration Manager.
- Migrate Email From – sets the date to migrate email from. Only email from the date set (including the date) and later will be migrated.
- Migrate Email To – sets the date to migrate all email to. All email up to (and not including) the specified date will be migrated.
- Migrate Appointments/Tasks From – sets the date to migrate all appointments from. All appointments from the date set (including the date) will be migrated and anything earlier than that date will not. If any appointments are present as attachments to email messages and are earlier than the specified date these may still be migrated.
- Migrate Appointments/Tasks To – sets the date to migrate appointments to. All appointments up to the specified date (and not including) will be migrated. For Tasks, the due date must fall between the From and To dates.
- Migrate Documents From – sets the date to migrate documents from. Only documents from the date set (including the date) and later will be migrated.
- Migrate Documents To – sets the date to migrate all documents to. All documents up to (and not including) the specified date will be migrated.
- File Extensions/Mime Type Include – specify a list of file extensions/Mime types to filter files migrated from a file platform. By default all files are migrated.
- File Extensions/Mime Type Exclude – specify a list of file extensions/Mime types to exclude being migrated from a file platform.
- File Names Include - specify the list of wildcard patterns for file names, one per line, that will be migrated (*.* for all)
- Overwrite Updated Documents – enable delta migrations, where a re-migration will cause any items that have been modified (edited, moved, deleted etc) in the source since the last migration to be re-migrated and updated in the destination. In the case of migrations to Google Drive, this means that the item will be deleted and re-migrated and will result in a new ID or URL for the file. See this article for more information.
- Force Drive Remigrations Over Size – force drive re-migration of files of or over the specified size. See this article for more information.
- Filter Date Type – migrate files based on the selection and date ranges set for ‘Migrate Files From’ and ‘Migrate Files To’
Domain Replacement Types
- Choose which item types to perform domain replacements for. By default, all domain replacements are enabled apart from Email (as often aliases are kept in place). Replacements are always performed for documents.
Email Attachments to Drive
- Email Attachment Document Migration – choose whether to migrate email attachments to Drive.
- Email Attachment Document Sharing – choose the type of sharing that will be applied when migrating email attachments to Drive. When the sharing options are chosen, documents migrated from an email will be shared with the recipients of the email. Notification emails are not sent when migrating to Microsoft OneDrive.
- File Extensions – when migrating documents from Email attachments, migrate only documents which match the filters supplied here.
- All filters must be specified as *.ext
- Use *.* to match all files
- Add Document Links – when attachments are migrated to Drive from within an email message, add links to the migrated documents into the email body.
- Drop Migrated Attachments – when attachments are migrated to Drive, drop the migrated attachments from the email they originated from.
- Minimum Email Attachment Size – migrate only attachments of the specified size and over to Drive. To migrate all attachments, specify a size of 0.
- Migrate all Attachments for Oversized Messages – if an email is oversized, then migrate all attachments to Drive, regardless of size.
- Excluded Folders – specifies a list of folder names that will be excluded from the migration. Folder names should be specified one per line, and are case-sensitive.
- For subfolders, use forward slashes. Eg: Folder/Subfolder, Top Folder/Sub Folder
- If an email has multiple labels in Gmail and you exclude any one of those, then the email will not be migrated.
- Migrate Attachments – chose to migrate attachments. If false all email attachments will not be transferred to the destination system.
- Excluded Attachment Extensions – specify a list of file extensions to exclude attachments when migrating email. Leave empty to migrate all attachments. Attachments that match this list will be dropped before performing any other possible attachment operations.
- Migration Folders – choose to migrate all, or certain well-known folders only.
Note that when referencing special folders the following replacement tokens must be used, due to differences in the way these folders are identified in source platforms:
For example, to only include the subfolder
'test/subfolder', which resides in the inbox / mailbox folder (depending on source platform) you need to supply the following path:
- Modify Invalid Messages – choose to attempt to modify certain messages that would otherwise not be accepted by the destination system. This includes trimming over-sized messages and removing or renaming attachments which contain executables (for GSuite migrations). If you do not wish messages to be modified you should ensure this setting is set to False.
- Message Labels – specify a semi-colon delimited list of labels/categories to apply to migrated messages. Note that the label ‘Migrated’ is reserved within G Suite and will be created as ‘Migrated/Migrated’.
- Migrate Headers Only – use to migrate headers only for specialist scenarios. Supported from Exchange systems only.
- Archive Folder Structure – use this option to place all folders underneath a single folder. This also includes all special folders, so extra folders for the Inbox, Sent Items, etc. will be created underneath the folder specified by the following option.
- Archive Folder Structure Name – if ‘Archive Folder Structure’ is turned on, place all messages within a folder of the specified name.
- Label Modified Messages – apply a label or category to messages that have been modified. This includes messages which have had attachments removed due to them being oversized, or that have had documents migrated to Google Documents and the original removed from the message.
- Modified Message Label – the label or category to apply when ‘Label Modified Messages’ is turned on.
The following macros can be used with the label config options (Message Labels, Archive Folder Structure Name, Oversized Attachments Folder/Label, Top Level Folder) to label migrated items using fields from the migration configuration:
- Item Export Delay – wait this number of milliseconds between exporting items from a source system. This can be used to artificially slow a migration from a source system if required.
- Drive Thread Count – use this number of threads per-user when migrating items to Drive.
- Auto Restart Crashed Users – in very rare cases some GroupWise migrations may crash without the error being handled correctly by CloudMigrator. Set this option to true to have CloudMigrator restart the process and skip the item that previously failed. Do not enable this for normal migrations.
- Include Folders - when using Virtru to encrypt messages encrypt only those in the specified folders. Leave empty to encrypt all messages
- Include Categories - when using Virtru to encrypt messages encrypt those only tagged with the specified categories. Leave empty to encrypt all messages.