Created by Drew Wallin, last modified on Oct 13, 2017
Location Maps are used to specify the new locations that source content will migrate into. Content can be directed to a new location on the target by using a Location Map, sending mapped objects and all child content (unless otherwise specified) to a specified new location.
Note: Without a location mapping, all content ends up in the same hierarchical position in the target location after migration.
A location mapping .csv is a simple two-column sheet. The first column is filled in with a source location path, and the second column with the target location path. Each column is formatted according to the syntax requirements of the connection type.
Note: treat all identities in a location mapping as case-sensitive. In some cases, bridges may not run correctly if the mapping is case-incorrect.
Note: The folder division syntax varies depending on the environment. In Drive folder path strings, subfolders are separated with a hash (#) instead of the backslash (\) used in Windows file system folder path strings.
The above example shows the location mapping format and syntax for a File Share to G Suite - My Drive migration case. The Google admin account which is used to gain visibility and access across the target domain has access to each of the user Drive accounts in the second column, and can send data from the source connection file share to each user Drive and subfolder within the domain.
Note: the location mapping will not create target locations by default, so all locations specified in the location mapping CSV must already exist, or the settings template must be configured to "Create Target Locations".