About Box settings template options

You can migrate Box content to your users' 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. See below for details about the templates.

Migrate to My Drive

Expand section  |  Collapse all & go to top

Migrate Box content

Migrate folders	Enabled by default When enabled, Box folders are migrated to Google Drive folders.
Migrate files	Enabled by default When enabled, Box files are migrated to Drive files. Optionally, you can: Check the Migrate versions box to migrate versions of file. Check the Pin revisions box to to apply Drive’s Keep forever tag to file revisions (uncheck the box to not pin any versions).  To limit the number of revisions that are pinned, enter a number in the Max pinned revisions field. The tag is applied to the specified number of revisions, beginning with the most recent.
Migrate collaborations	Enabled by default When enabled, Box collaborations are migrated as Google permissions.
Allow email invitations	When enabled, users inside and outside your organization that are assigned permissions for a Drive folder or file are sent an email notification.

Filter Box content

Note: String-based filters are not case-sensitive.

Exclude Box folders Exclude Box versions Exclude Box collaborations

When enabled, you can use filters to exclude content from your migration. Click Select Property and choose a filter property. Complete the filter conditions.  (Optional) To set multiple filters, click Add filter and repeat the steps above.  (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.  (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box. After you enter all filters, click Create a new template, enter a template nameCreate.

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

Migrate to shared drives

Expand section  |  Collapse all & go to top

Migrate Box to shared drives

Migrate folders	Enabled by default When enabled, Box folders are migrated to shared drive folders.
Migrate files	Enabled by default When enabled, Box files webs are migrated to shared drive files. Optionally, you can: Check the Migrate versions box to migrate versions of file. Check the Pin revisions box to to apply Drive’s Keep forever tag to file revisions (uncheck the box to not pin any versions).  To limit the number of revisions that are pinned, enter a number in the Max pinned revisions field. The tag is applied to the specified number of revisions, beginning with the most recent.
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 Go to Restricted permissions.
Allow email invitations	When enabled, users outside of your organization who are assigned permissions for shared drives are sent an email notification.

Filter Box content

Note: String-based filters are not case-sensitive.

Exclude Box folders Exclude Box versions Exclude Box collaborations

When enabled, you can use filters to exclude content from your migration. Click Select Property and choose a filter property. Complete the filter conditions.  (Optional) To set multiple filters, click Add filter and repeat the steps above.  (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.  (Optional) To include children of excluded objects in the migration, uncheck the Exclude children box. After you enter all filters, click Create a new template, enter a template nameCreate.

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

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