In the Preparation phase of a G Suite (formerly Google Apps) migration using Transformer, you will prepare for migration by:

Configuration - Settings Templates

Settings Templates are a persistent set of configured options applied to Bridges. Settings Templates can be created to change migration behviour.

Configuration (simple) - Settings Template

The Default settings template is included with the AppBridge Transformation Suite (ATS), and includes the set of recommended options for migrations between two G Suite environments. 

For simple configurations using the Default settings template, you can proceed to the Configuration - Value Maps section. You will choose the Default template during configuration of Bridges.

Configuration (advanced) - Settings Template

There are many options available in the Settings Template for migrations between two G Suite environments.

For a detailed list of all settings, please consult the Settings - G Suite to G Suite Migration documentation, and create a Settings Template that meets your migration requirements.

Configuration - Value Maps

There are three types of Value Maps that can be applied to Bridges when migrating G Suite environments: User Maps, Location Maps and URL Maps.

A header column is not required for Value Maps or Value Lists.

Documents uploaded using Shard accounts will have the Creator set to the shard account. Modified information and Owner will be set to the desired user accounts.

Creating Value Maps

Please see the Value Maps documentation for instructions on how to create or upload a Value Map.

User Maps

User Maps transform user and group references within objects when migrating between G Suite environments.

User Maps facilitate the transformation of sharing rights assigned to users and groups, creation and modification metadata, and other references that include a username. 

Best Practice: User Maps should be used when migrating between G Suite environments, as sharing rights and metadata cannot be migrated without them.

Configuration - User Maps

User Maps used by migrations between G Suite environments must be in the following format:

Source Email
Target Email
username@sourcedomain.comusername@targetdomain.com
username2@sourcedomain.comusername2@targetdomain.com
group@sourcedomain.comgroup@targetdomain.com

Location Maps

Location Maps transform the locations of objects when migrating between G Suite environments.

Location Maps determine the new target owner for source objects and facilitate re-organization of the folder hierarchy.

Best Practice: Location Maps should be used when migrating more than a single user between G Suite environments, as they define the target locations that source user objects will be migrated to.

Note: User Maps and Location Maps appear similar at first glance because the root location of a G Suite account is the username of the user that owns it.

While they may appear similar, each type of mapping performs a different task.

Configuration (simple) - Location Maps

Location Maps must be configured using the Transformation Suite Location Maps syntax. If you are simply migrating all Google Apps from your source users to your new target users, your Location Maps must be in the following format:

Source Location
Target Location
username@sourcedomain.com#*username@targetdomain.com
username2@sourcedomain.com#*username2@targetdomain.com

Note: For a detailed explanation of the Location Maps syntax for G Suite, please see the Configuration (advanced) - G Suite Location Maps section. 

Configuration (advanced) - Location Maps

The Location Maps syntax supports many possibilities for mapping source locations to target locations. The following table defines all possible syntax combinations supported by G Suite Location Maps:

Source Value
Target Value
Description
username@sourcedomain.com#*username@targetdomain.comMigrates all Apps and their contents from username@sourcedomain.com to username@targetdomain.com
username@sourcedomain.com#Driveusername@targetdomain.comMigrates the Google Drive App from fromusername@sourcedomain.com to username@targetdomain.com
username@sourcedomain.com#Drive#FolderA#*username@targetdomain.com#Drive#FolderBMigrates the contents of FolderA (but not FolderA itself) from username@sourcedomain.com's Drive to FolderB in username@targetdomain.com's Drive.
username@sourcedomain.com#Drive#FolderAusername@targetdomain.com#DriveMigrates FolderA and all contents from the root of username@sourcedomain.com's Drive to the root of username@targetdomain.com's Drive.
username@sourcedomain.com#Mailusername@targetdomain.comMigrates the Gmail App from username@sourcedomain.com to username@targetdomain.com
username@sourcedomain.com#Calendarusername@targetdomain.comMigrates the Google Calendar App from username@sourcedomain.com to username@targetdomain.com
username@sourcedomain.com#Sitesusername@targetdomain.comMigrates the Google Sites App from username@sourcedomain.com to username@targetdomain.com
username@sourcedomain.com#* Filters the source location from the migration. All child objects will also be filtered from the migration unless explicitly mapped on a separate row in the location map.  

URL Maps

URL Maps transform URL links within objects when migrating between G Suite environments. 

Best Practice: URL Maps are only required when transforming URLs in Google Sites that are out of scope of the migration.

Configuration - URL Maps

URL Maps used by migrations between G Suite environments must be in the following format:

Source URL
Target URL
Any valid source URLAny valid target URL

Configuration - Value Lists

There is only one type of Value List that can be applied to Bridges migrating G Suite environments: Shard Sets.

Creating Value Lists

Please see the Value Lists documentation for instructions on how to create or upload a Value List.

Shard Sets

Shard Sets increase the pool of user accounts that can be used to write objects to Google Drive, and are required to migrate more than 50,000 objects to a single user's Google Drive account.

Best Practice: If any user's Google Drive account is expected to own more than 50,000 objects after migration, a Shard Set must be applied to the Bridge that is using the Location Map containing that user. If a Shard Set is not applied, migration speed and long term performance will degrade significantly.

Configuration - Shard Sets

Shard sets are a single column list of email addresses corresponding to the target domain G Suite user accounts that will be used for the migration pool.

Documents uploaded using Shard accounts will have the Creator set to the shard account. Modified information and Owner will be set to the desired user accounts.

Email Address
username@targetdomain.com
username2@targetdomain.com

 

Next: Execution - G Suite to G Suite Migration