AppBridge Documentation : Preparation - File Share to G Suite Migration

In the Preparation phase of a File Share migration using Transformer, you will prepare for migration by:

Configuration - Settings Templates

Settings Templates are a persistent set of configured options that can be applied to Bridges to control migration.

Configuration - File Share Settings Template

The Default settings template is included with the Transformation Suite, and includes the set of recommended options for migration from a File Share environment. 

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 - Value Maps

There are two types of Value Maps that can be applied to Bridges migrating File Share environments: Location Maps and User Maps.

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

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 migrating between different 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 from a File Share to G Suite, as sharing rights and metadata cannot be migrated without them.

Configuration - File Share User Maps

User Maps used by migrations from File Share environments must be in the following format:

Source User
Target User
DOMAIN\usernameusername@targetdomain.com
DOMAIN\username2username2@targetdomain.com
DOMAIN\groupnamegroup@targetdomain.com

Location Maps

Location Maps transform the locations of objects migrating from a File Share environment.

Location Maps determine how source folder hierarchies are directed to user Drive accounts in the target environment. Location maps easily facilitate re-organization of the source folder hierarchy.

Best Practice: Location Maps should be used to direct content to specified Google Drives, as the target account will become owner of the content. Location Mapping ensures organizational content remains owned, managed and shared by administrators. Location maps can also be used to migrate individual users' local or network drives to their respective Google Drive storage.

Configuration - Migrate File Shares to My Drives - Location Maps

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

Source Location
Target Location
\\DOMAIN\File Share Root Folder\systemadmin@targetdomain.com#Drive#My Drive
\\DOMAIN\File Share Root Folder\Marketing marketingadmin@targetdomain.com#Drive#My Drive
\\DOMAIN\File Share Root Folder\User Drives\User1user1@targetdomain.com#Drive#My Drive
\\DOMAIN\File Share Root Folder\User Drives\User2user2@targetdomain.com#Drive#My Drive#FS Storage
  • In the above example, all content within the Root Folder which is not explicitly mapped will be migrated to, and consequently be owned by, the system admin's Drive account. 
  • The second string ensures that the Marketing subfolder will be directed to themarketingadminDrive account, and will not appear in the system admin's Drive.
  • The third and fourth strings map user1 and user2's personal drives from the source file share to their respective Drive accounts, with user2 choosing a specific folder within their Drive account to direct their File Share Drive content to.


Configuration - Migrate File Shares to Team Drives - Location Maps

Migrating to Team Drives requires the 'Migrate to Team Drives' settings template to be applied to the bridge. The Team Drives migration syntax is as follows:

Source Location
Target Location
\\DOMAIN\File Share Root Folder\systemadmin@targetdomain.com#Drive#Team Drives#Root
\\DOMAIN\File Share Root Folder\Marketingmarketingadmin@targetdomain.com#Drive#Team Drives
\\DOMAIN\File Share Root Folder\User Drives\User1user1@targetdomain.com#Drive#Team Drives
\\DOMAIN\File Share Root Folder\User Drives\User2user2@targetdomain.com#Drive#Team Drives#FS Storage
  • In the above example, all content within the Root Folder which is not explicitly mapped will be migrated to the "Root" Team Drive, of which the system admin must an Organizer or Editor. 
  • The second string ensures that the Marketing subfolder and it's child content will be migrated to a new Team Drive called "Marketing" which the marketingadmin account will be the Organizer of.
  • The third and fourth strings map user1 and user2's personal drives from the source file share to their respective Team Drives, with user2 choosing a specific Team Drive named FS Storage.

Configuration - Value Lists

There is only one type of Value List that can be applied to Bridges migrating File Share 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 Google Apps 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 and Owner metadata will be set to the desired user accounts.

 

Next: Execution - File Share to G Suite Migration