Understand Exchange settings templates

See below for details about options in the default Microsoft® Exchange settings template.

Settings template options

Open all   |   Close all

Migrate Exchange content
Setting Enabled by default? Details
Migrate Exchange mail content When enabled, all recommended settings for Exchange email migration to G Suite are turned on.
Migrate mail 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 two labels: Inbox and the name of the subfolder. 
  • Include settings
Include settings When enabled, these settings are turned on:
  • Include filter settings
  • Include signature
  • Include vacation settings
Accelerate old messages  

When enabled, the migration performance is modestly increased.

If you turn on this setting, you have the option of checking the Restrict insert by date box and specifying a date in the Insert before date field. Email data that’s dated prior to the Insert before date is accelerated during a migration.

Enabling this setting can cause data duplication and prevent message threading in certain circumstances. For example, if a user sets up email forwarding to their new Gmail account, forwarded messages are duplicated during a migration. Forwarded messages appear separately, rather than as part of an email thread. 

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

Learn more about Gmail APIs: Users.messages: import (used when the option is not enabled) and Users.messages: insert (used when the option is enabled). 

Include mail in In-Place Archives  

When enabled, messages in users' Exchange archive mailbox are migrated to G Suite. 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—Archived mail is migrated without any labels. Select this option if you don’t want archived messages to be specially labelled.
    • Merge archive folders with mailbox folders—Labels are created by folder name, whether they are archived or nonarchived folders. Archived and nonarchived mail appears in the user's inbox with labels attached. Select this option if you want to merge archived messages back into the user's inbox.
    • Create separate labels under an archive label—Creates a label for archived messages in the user's inbox. 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.

      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 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 When enabled, Exchange tasks and task folders are migrated to Google tasks. You have the option to Migrate to the default task list. If this option is not selected, the tasks migrate as a separate task list. 
Migrate calendars 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 When enabled, all super administrator accounts in your domain are used to transfer calendar resources to your G Suite account. Using multiple super administrator accounts improves migration speed and can help avoid quota issues.

For details, see Watchpoints and best practices for Exchange.

Upload calendar event attachments to Drive 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.

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.
  • (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 When enabled, all the migration options for contacts are turned on.
Map well-known phone number labels When enabled, well-known phone number labels are mapped instead of custom labels being created.
Migrate public folder content
Setting Enabled by default? Details
Migrate public folders When enabled, Exchange public folders are migrated to Google Groups.
Filter Exchange content
Setting Enabled by default? Details

Exclude Exchange mail folders

Exclude Exchange mail messages

Exclude Exchange archived mail messages

Exclude Exchange calendars

Exclude Exchange calendar events

Exclude Exchange contacts

  When enabled, you can use filters to exclude content from your migration.
  1. To choose a filter property, click Select Property.
  2. Complete the filter conditions. 
  3. (Optional) To set multiple filters, click Add filter and repeat the steps above. 
  4. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box. You’ll see excluded objects as skipped transactions in the transaction log. If you check the box, you won’t see excluded objects in the log. 
  5. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
  6. When you have entered all filters, click Create a new template, enter a template nameand thenCreate.

Exclude well-known Exchange mail folders

You can exclude common mail folders, such as Drafts or JunkEmail, by specifying the folder: 

  1. From step 2 above, check the Exclude Exchange mail folders box.
  2. Under Select Property, select Well Known Folder Name
  3. Under Select Operator, select Equals
  4. In the Enter a value field, enter the common mail folder name. The following folders are supported:
    • ConversationHistory
    • DeletedItems
    • Drafts
    • JunkEmail
    • SentItems
    • SyncIssues
  5. (Optional) To enter another folder, click Add filter, select OR from the list, and repeat steps 2–4.

Exclude mail messages in folders

You can exclude mail folders by specifying the folder path: 

  1. From step 2 above, check the Exclude Exchange mail messages box.
  2. Under Select Property, choose G Suite Migrate path
  3. Under Select Operator, choose Contains
  4. In the Enter a value field, enter a path for the Exchange folder (for example, useremail#mail#projects%20items). Make sure:
    • The string begins with useremail#mail#.
    • Nested folders are separated with a #.
    • Special characters are HTML-encoded.

Note: If you exclude mail messages, when you migrate data, Gmail creates a label out of the folder.

Filter public folder content
Setting Enabled by default? Details

Exclude Exchange public folders

Exclude Exchange posts

 

When enabled, you can use filters to exclude content from your migration.

  1. To choose a filter property, click Select Property.
  2. Complete the filter conditions. 
  3. (Optional) To set multiple filters, click Add filter and repeat the steps above. 
  4. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box. You’ll see excluded objects as skipped transactions in the transaction log. If you check the box, you won’t see excluded objects in the log. 
  5. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
User mapping
Setting Enabled by default? Details
Map users When enabled, any identity mapping associated with the bridge is followed.  
Allow unmapped users  

When enabled, all user permissions are migrated, including users who aren’t specified in the user mapping.

Note: If your domain does not allow sharing with users outside of the domain, enabling this setting might cause errors.

Domain mapping  

When enabled, G Suite 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, G Suite Migrate first checks that mapping for a new username. If it doesn’t find a new username, G Suite Migrate uses this setting to generate one.

Related topic

Use a settings template