About Exchange settings template options

Migrate Exchange mail content

Enabled by default

When enabled, all recommended settings for Exchange email migration to Google Workspace are turned on.

Migrate mail

Enabled by default

When enabled, Exchange email content is migrated and these settings are turned on:

• Add inbox label to subfolders–If a folder is a subfolder of Inbox, migrated messages have 2 labels: Inbox and the name of the subfolder. 
• Include settings (see below).

Include settings

Enabled by default

When enabled, these settings are turned on:

• Include filter settings
• Include signature
• Include vacation settings

Accelerate old messages

We recommend using this setting for very large or archival mailboxes. If you're unsure, do not use this option.

When enabled, the migration performance is modestly increased.

To accelerate email data before a certain date:

1. Check the Restrict insert by date box.
2. Next to Insert before date, enter a date.

If a user has actively switched to their new Gmail account, you can use the setting to prevent notifications for the user’s migrated mail. We recommend, however, that you migrate the majority of old messages before, not after, the user switches to Google Workspace.

Important: When used with dual delivery (where email messages are delivered to the legacy mail server and the user’s new Google Workspace account), the Accelerate old messages setting can cause message duplication and might separate existing email threads.

Related topics:

• Users.messages.import (Used when the option is not enabled)
• Users.messages.insert (Used when the option is enabled)

Include mail in In-Place Archives

When enabled, messages in users' Exchange archive mailboxes (online archives) are migrated to Google Workspace. Specify the locations in the mapping. For details, go to Create & manage a mapping. 

You have the option to:

• Make migrated archive mail only visible in Google Vault (not Gmail).
• Make attachments of archived mail uploaded to Google Drive only visible in Google Vault. If you turn on this setting, large email attachments are visible in Vault (not Drive).
• Archive folder to label handling—This determines how archive folders appear in Gmail. You have the option to:
  • Migrate archived mail without labels—Select this option if you don’t want archived messages to be specially labelled. Archived mail is migrated without any labels.
  • Merge archive folders with mailbox folders—Select this option if you want to merge archived messages back into the user's inbox. Creates labels by folder name, whether the folders are archived or not. Archived and nonarchived mail appears in the user's inbox with labels attached.
  • Create separate labels under an archive label—Select this option if you want users to access their archived messages in Gmail, but want to be able to separate the archived and nonarchived mail. Creates a label for archived messages in the user's inbox.

    If you select this option, you must enter a value in the Archive label name field. Both the value in this field and the existing folder name are attached as labels.

Upload the attachments of large messages to Drive

Enabled by default

When enabled, any attachments that are 25 MB or larger are uploaded to Google Drive and not attached. You have the option to:

• Specify the name of the Drive folder where you want the attachments to be uploaded (Drive folder name field).
• Specify a smaller attachment size in MB (Message size threshold field). Any attachments larger than the specified size are moved to Drive.

Migrate tasks

Enabled by default

When enabled, tasks and task folders migrate to Google Tasks.

You also have these suboptions:

• Migrate to the default task list—If you do not choose this suboption, then your tasks migrate as a separate task list.
• Migrate task due dates (disabled by default)—You can choose to migrate the date by which the task is due. If you select this suboption, you must enter a time zone in Task due date timezone.

Migrate calendars

Enabled by default

When enabled, these settings are turned on:

• Migrate calendar events
• Get attendee responses for non-organizers
• Add events to resource calendars
• Use all super admins to write resource calendar events (see below)
• Upload calendar event attachments to Drive (see below)
• Migrate calendar permissions

Use all super admins to write resource calendar events

Enabled by default

When enabled, all super administrator accounts in your organization are used to transfer calendar resources to your Google Workspace account. Using multiple super administrator accounts improves migration speed and can help avoid quota issues.

For details, see Monitoring points for Exchange.

Upload calendar event attachments to Drive

Enabled by default

When enabled, migrated calendar event attachments are uploaded to Drive.

In the Event attachment folder name field, you can specify the name of the Drive folder where you want to upload the attachments.

You have the option to skip system event attachments (see below).

Skip system event attachments

When enabled, .ics (iCalendar) and .vcf (vCard) files that are attached to calendar events are skipped.

Set default organizer

When enabled, a default email address is used when the organizer of an event doesn’t have a valid email address. If you enable this setting:

• In the Default organizer field, enter an email address. The email address replaces any organizer's address that's invalid.
• (Optional) To add a suffix that’s attached to events with a default organizer, enter the suffix in the Event subject suffix field. 

Migrate contacts

Enabled by default

When enabled, contacts are migrated.

Map well-known phone number labels

Enabled by default

When enabled, instead of creating custom labels for phone numbers, well-known phone number labels are mapped.

Migrate public folders

Enabled by default

When enabled, Exchange public folders are migrated to Google Groups.

Exclude Exchange mail folders

Exclude Exchange mail messages

Exclude Exchange archived mail messages

Exclude Exchange calendars

Exclude Exchange calendar events

Exclude Exchange contacts

Mail folders & messages

• Created Date–Date and time item in Exchange mailbox was created
• Date Received–Date message was received
• Date Sent–Date message was sent
• From–Message sender
• Google Workspace Migrate path–Exchange folder path
• Item Class–Type of message (for details, go to ItemClass)
• Subject–Message subject
• Title–Folder name
• Well Known Folder Name–Common mail folders, such as Drafts or JunkEmail

Calendar data

• All day event–Events scheduled for all day
• Created date–Date when event was created
• Event start time–Scheduled start time of event
• Event end date–Date the event ends
• Last modified date–Date event was last modified
• Title–Name of calendar event

Contacts data

• Created date–Date contact was created
• Last modified date–Date contact was last modified
• Title–Name of the contact

To use a filter:

For common examples, go to Examples of filters.

Exclude Exchange public folders

Exclude Exchange posts

Public folders

• Title–Folder name

Posts

• Created Date–Date post was created
• Title–Folder name

To use a filter:

For common examples, go to Examples of filters.

• Property–Well Known Folder Name
• Operator–Equals
• Value–Enter the folder name.

  For details about well-known folder names for your version of Exchange, consult your Microsoft documentation. 

To exclude mail messages in folders, check the Exclude Exchange mail messages box.

To exclude the folder itself, check the Exclude Exchange mail folders filter.

• Property–Google Workspace Migrate path
• Operator–Contains
• Value–Enter a path for the Exchange folder. When formatting the path:
  • Use #mail followed by the folder hierarchy.
  • Separate nested folders with # (for example, #mail#subfolder).
  • To filter the messages of a single user, begin the path with the username (for example, username%40example.com #mail#subfolder).
  • Special characters are HTML-encoded.

• Property–Date Received or Date Sent
• Operator–Before or After
• Value–Select a date or enter a date in YYYY-MM-DD HH:MM format.

Map users

Enabled by default

When enabled:

• Users are mapped according to the identity mapping associated with the bridge.
• Your identity mapping should include users who are the same on the source and target environments. You can omit these users if the Allow unmapped users setting is enabled (details below).

Allow unmapped users

When enabled, user permissions on the source domain (including permissions belonging to users that aren’t specified in an identity mapping) are transferred to the files on the new domain.

Users with permission to access files and folders on the source domain retain access after the migration. However, the permissions are not transferred to users on the target domain. 

Note the following points:

• If your organization doesn't allow sharing with users outside of the organization, enabling this setting might cause errors.
• If you want to transfer permissions to the new users on the target domain, use an identity mapping. For details, go to Create & manage an identity mapping.

Domain mapping

When enabled, Google Workspace Migrate automatically maps source domain usernames to target domain usernames (for example, user1@ on your source domain becomes user1@ on your target domain). If you enable this setting:

• In the Source domain field, enter the source domain.
• In the Target domain field, enter the target domain.

Note:

• Using this setting requires that the domain-relative usernames of the source and target domain are identical.
• If you’re using an identity mapping, Google Workspace Migrate first checks that mapping for a new username. If it doesn’t find a new username, Google Workspace Migrate uses this setting to generate one.