About settings template options

Google Workspace to Google Workspace migration

You can migrate Google Workspace content to your users' Google My Drive or shared drives. Each settings template has options that you can enable, depending on how you want your data to appear after a migration. Make sure you use the correct settings template for your migration. 

Default

Expand section  |  Collapse all & go to top

Migrate Drive content

Migrate folders

Enabled by default

When enabled, Drive folders are migrated.

Migrate files

Enabled by default

When enabled, Drive files are migrated.

Check the Migrate revisions box to migrate versions of files.

Migrate Google Docs

Enabled by default

When enabled, Docs are migrated.

Migrate Google Sheets

Enabled by default

When enabled, Sheets are migrated.

Migrate comments

Enabled by default

When enabled, comments are migrated. Applies to Drive platform-specific files.

Migrate sharing permissions

Enabled by default

When enabled, sharing permissions are migrated along with the objects to Drive.

If enabled, you can choose to migrate sharing permissions and enable the Allow email invitations setting (off by default). If you do so, users inside and outside your organization who are assigned permissions for a Drive folder or file are sent an email notification.
Migrate Mail content

Migrate mail

Enabled by default

When enabled, Gmail content is migrated.

To migrate Gmail settings, check the Include settings box. If enabled, you can choose to include these settings, which are on by default:

  • Include autoforwarding settings
  • Include delegate settings
  • Include filter settings
  • Include forwarding settings
  • Include IMAP settings
  • Include POP settings
  • Include send as settings (migrates the signature for the primary Gmail account)
  • Include vacation settings

Check the Accelerate old messages box and the migration performance is modestly increased.

If you turn on this setting, you can check the Restrict insert by date box and specify a date in the Insert before date field. Email data that’s dated before 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 large or archival mailboxes. If you're unsure, do not use this option.

Learn more about Gmail APIs:

Migrate tasks

Enabled by default

When enabled, Google Tasks and Task folders are migrated.
Migrate Contacts content

Migrate contacts

Enabled by default

When enabled, all the migration options for Contacts are turned on.
Migrate Calendar content

Migrate calendars

Enabled by default

When enabled, all the migration options for Calendar are turned on.

Migrate calendar permissions

Enabled by default

When enabled, Calendar permissions are migrated.

Upload calendar event attachments to Drive

Enabled by default

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

Exclude Google Drive folders

Exclude Google Drive files

Exclude Google Docs

Exclude Google Sheets

Exclude Google permissions

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

  1. Check the box to select the type of content you want to filter.
  2. Click AND, then select And or Or filter logic.
  3. Click Select Property and choose a filter property.
  4. Complete the filter conditions.

    String-based filters are not case sensitive unless indicated.

  5. (Optional) To create a set of filters, click Add Group and repeat steps 1–4.
  6. (Optional) To add another filter, click Add Filter and repeat steps 1–4.
  7. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box.

    Excluded objects show as skipped transactions in the transaction log. If you check the box, you won't see excluded objects in the log.

  8. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
  9. After you enter all filters, click Create new template, enter a template nameand thenCreate.
Filter Mail content

Exclude Gmail labels

Exclude Gmail messages

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

  1. Check the box to select the type of content you want to filter.
  2. Click AND, then select And or Or filter logic.
  3. Click Select Property and choose a filter property.
  4. Complete the filter conditions.

    String-based filters are not case sensitive unless indicated.

  5. (Optional) To create a set of filters, click Add Group and repeat steps 1–4.
  6. (Optional) To add another filter, click Add Filter and repeat steps 1–4.
  7. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box.

    Excluded objects show as skipped transactions in the transaction log. If you check the box, you won't see excluded objects in the log.

  8. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
  9. After you enter all filters, click Create new template, enter a template nameand thenCreate.

To migrate only messages that have a specific label, use 2 filters: 

  1. Check the Exclude Gmail labels box and enter the following:
    • Property–Title
    • Operator–Does not equal
    • Value–Label name
  2. Check the Exclude Gmail message box and enter the following:
    • Property–Labels
    • Operator–Not contains
    • Value–Label name
Filter Contacts content

Exclude Google Contacts

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

  1. Check the box to select the type of content you want to filter.
  2. Click AND, then select And or Or filter logic.
  3. Click Select Property and choose a filter property.
  4. Complete the filter conditions.

    String-based filters are not case sensitive unless indicated.

  5. (Optional) To create a set of filters, click Add Group and repeat steps 1–4.
  6. (Optional) To add another filter, click Add Filter and repeat steps 1–4.
  7. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box.

    Excluded objects show as skipped transactions in the transaction log. If you check the box, you won't see excluded objects in the log.

  8. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
  9. After you enter all filters, click Create new template, enter a template nameand thenCreate.
Filter Calendar content

Exclude Google Calendar

Exclude Google Calendar events

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

  1. Check the box to select the type of content you want to filter.
  2. Click AND, then select And or Or filter logic.
  3. Click Select Property and choose a filter property.
  4. Complete the filter conditions.

    String-based filters are not case sensitive unless indicated.

  5. (Optional) To create a set of filters, click Add Group and repeat steps 1–4.
  6. (Optional) To add another filter, click Add Filter and repeat steps 1–4.
  7. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box.

    Excluded objects show as skipped transactions in the transaction log. If you check the box, you won't see excluded objects in the log.

  8. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
  9. After you enter all filters, click Create new template, enter a template nameand thenCreate.
User mapping

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 later on this page).

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 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.

Migrate My Drive to shared drives

Expand section  |  Collapse all & go to top

Migrate to shared drive

Migrate folders 

Enabled by default

When enabled, My Drive folders are migrated to shared drive folders.

If enabled, you can choose to Migrate Google Drive folders with restricted permissions (off by default). Child folders that have been assigned fewer permissions than the parent (as specified in the mapping) are migrated. If turned off, those folders are skipped.

File migration approach

Enabled by default

Select either Migrate files or Skip files. If Migrate files is enabled, you can choose to:

  • Migrate revisions (on by default)
  • Migrate Google Docs (on by default)
  • Migrate Google Sheets (on by default)
  • Migrate comments (on by default).
  • Migrate Google Drive files with restricted permissions (off by default)

Migrate folder permissions

Enabled by default

When enabled, folder permissions are migrated to the target shared drive.

Restricted permissions are not migrated. Go to Restricted permissions.

Migrate file permissions

Enabled by default

When enabled, file permissions are migrated.

Restricted permissions are not migrated. Go to Restricted permissions.
Filter Drive content

Exclude Google Drive folders

Exclude Google Drive files

Exclude Google Docs

Exclude Google Sheets

Exclude Google permissions

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

  1. Check the box to select the type of content you want to filter.
  2. Click AND, then select And or Or filter logic.
  3. Click Select Property and choose a filter property.
  4. Complete the filter conditions.

    String-based filters are not case sensitive unless indicated.

  5. (Optional) To create a set of filters, click Add Group and repeat steps 1–4.
  6. (Optional) To add another filter, click Add Filter and repeat steps 1–4.
  7. (Optional) To identify objects that are excluded by your filter, uncheck the Exclude from crawl box.

    Excluded objects show as skipped transactions in the transaction log. If you check the box, you won't see excluded objects in the log.

  8. (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box.
  9. After you enter all filters, click Create new template, enter a template nameand thenCreate.
User mapping

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 later on this page).

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 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.

Related topic

Set up or select a settings template


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

true
Search
Clear search
Close search
Google apps
Main menu
18098742273645242880
true
Search Help Center
true
true
true
false
false