AppBridge Documentation : Value Map - Users

User mappings allow for conversion of source domain user references to user references that are valid in the target domain. User mappings are essential to enterprise migrations because they are required to preserve source environment ACLs through migration. 


Note: User Mappings will modify user accounts in all locations where users are referenced, including role assignments and metadata.


A user mapping is a simple two-column sheet, which maps user accounts from the source domain to the target.  To set up a user mapping, simply input the user or group with the correct syntax as it appears in the source environment in the first column, and the target Google user or group in the second column. 


The above sheet is a custom user mapping which maps several file system users and groups to their equivalent Google Drive users and groups. The permissions for each user in the first column will be applied to the the target domain user account in the same row.

Note: When creating mappings, always create the file in .csv format. Furthermore, AppBridge recommends using Google Sheets or another spreadsheet application to create, edit, or view .csv files to preserve formatting.




The created .csv file can now be uploaded to the Migration Platform and applied to bridges as a user mapping.

Mapping Users with a Domain Mapping

If you utilize a standard naming convention for users (<first name>.<last name>; <first initial>.<last name>; <first initial>_<last name>; etc.) in the source and target domains, then users can be mapped without uploading a user mapping. 


To utilize a domain mapping, you must edit your Settings Template. Domain mappings are located under the User Mapping package listing for each migration type.

In advanced scenarios, users can also be mapped via regex. The regex patterns for some common migration cases are outlined below:


Common Regex String Formats: :

File Share to Drive:

Format: {0}@<newdomain>
Pattern: <DOMAIN>\^([a-z0-9._%+-]+)
Google Apps to Google Apps:
Format: {0}@<newdomain>
Pattern: ^([a-z0-9._%+-]+)@<olddomain>

SharePoint to Drive:
Format: {0}@<newdomain>
Pattern: \|([a-z0-9._%+-]+)@<sharepointurl>


Note: all values inside the <> angle brackets are simply placeholders to demonstrate format, and must be replaced by actual values.