In the Preparation phase of a Box.com 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 - Settings Template
The Default settings template is included with the Transformation Suite and includes the set of recommended options for migration from a Box 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 Box 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 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.
Configuration - User Maps
User Maps used by migrations from Box.com environments must be in the following format:
Location Maps transform the locations of objects migrating from a Box environment.
Location Maps determine how source folder hierarchies are directed to user Drive accounts in the target environment. Location maps easily facilitate the reorganization 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 the 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 - 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:
- In the above example, all content within the All Files 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 the marketing admin Drive 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 to their respective Drive accounts, with user2 choosing a specific folder within their Drive account to direct their source content to.
Configuration - Value Lists
There is only one type of Value List that can be applied to Bridges migrating Box 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 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 - G Suite 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 and Owner metadata will be set to the desired user accounts.