Mapping Users and Groups from the UI
If you chose to Map Users from the UI in the Permissions Options tab, source and target users must be mapped individually.
NOTE: Mappings are saved as separate .MLM files in the folder \\AppData\Roaming\Metalogix\Content Matrix Console - File Share Edition, and the mappings are specific to the particular mapping dialog (Field Types, Users, or Permissions.) they were saved from.
To map users from the UI:
NOTE: Content Matrix supports many-to-one (n:1) user mappings between source and target.
1.After checking Migrate users using explicit user mappings on the Permissions Options tab, select Map Users from UI and click the [Edit Users] button.
2.From the File drop-down at the top of the Active Directory Principal to SharePoint Principal Mappings window, select the appropriate option. Use the information in the following table for guidance.
|
If you want to ... |
Then... |
|---|---|
|
load mappings from a previously-saved Metalogix Mapping setting (.MLM) file |
·choose File > Load. AND ·Navigate to and open the mapping file to populate the Mappings dialog. |
|
save the mappings in the dialog as a Metalogix Mapping setting (.MLM) file. |
choose File > Save. |
|
set the current permission mappings in the dialog as the default permission mapping (regardless of the source/target connections being used) |
choose File > Use as Current Default. NOTE: the mappings that display in the dialog are saved to the local machine, so they are persistent whenever the application restarts. |
3.Use the information in the following table to determine the appropriate action to take.
NOTE: You can Filter items in each window to narrow displayed lists.
|
If you want to ... |
Then... |
|---|---|
|
manually map individual users or groups on the source to a target SharePoint user or group |
·From the source list, select the Item(s) that you want to map. ·From the target list, select a target Item. ·Click the Map icon. |
|
have Content Matrix automatically map source users/groups to target SharePoint users/groups |
·From the source list, select the Item(s) that you want to map. ·Click the Auto icon. NOTE: Content Matrix will only map users automatically if the source and target side names match, or if the emails match, and the source and target environments are using the same AD. |
The mappings you create will display in the bottom window. (Note that you can also Unmap individually-selected mappings in the bottom window or or Clear all mappings from the bottom window.
4.Click [OK] once all desired mappings have been made and return to the Configuration Options dialog.
Mapping Users and Groups from a CSV File
You can map users and groups in bulk by importing a CSV file that contains the mappings. This is especially useful if there are a very large number of users to map as it streamlines the process and significantly reduces the time it takes for mappings to load in the Console. User mappings can also be imported using PowerShell.
Existing mappings can also be exported to a CSV file.
NOTE: Mappings imported from CSV are saved as an .MLM file to \\AppData\Roaming\Metalogix\Content Matrix Console - File Share Edition\UserAndPermissionsMappings.
Formatting the CSV file
The CSV file for the bulk mapping matches each source user and group to the SharePoint target user. Use the entries Target URL, Source, Source Type (User or Group), Target and Target Type (SPUser or SP Group) for the first row. (This will allow Content Matrix to validate the entries).
EXAMPLE:
To map users and groups from a CSV file in the UI:
1.After checking Migrate users using explicit user mappings on the Permissions Options tab, select Map Users from CSV and click the [Import CSV] button.
You will be prompted to confirm that you want to overwrite existing mappings.
2.Select the CSV file you want to import.
A message displays indicating whether or not the mappings were imported successfully.
To map users and groups from a CSV file using Powershell:
If the PowerShell Snap-Ins have been added, you can use the cmdlet Import-FileShareUserMappings with the -CsvFilePath to import user mappings from a CSV file.
EXAMPLE:
Import-FileShareUserMappings -CsvFilePath C:\Users\spinstall\MappingUsingCSV\UserMappings.csv
To export existing user and group mappings from the Console to a CSV file:
1.From the File drop-down at the top of the Active Directory Principal to SharePoint Principal Mappings window, select Save Mappings.
NOTE: You do not have to wait for the mappings to load to save the file.
2.For Save as type, select CSV Files (*.csv) and specify a file name.
Mapping Permissions
You can map File Share roles into SharePoint permissions when you click the [Edit Permissions] button from the Permissions Options tab. Any Allow Rights or Deny Rights permissions on the source can be mapped to SharePoint permissions on the target, provided the user or group with the permissions has been mapped and exists in the SharePoint environment. Content Matrix does not create any SharePoint permission levels, and can only map roles into existing permissions.
Role mapping (permissions mapping) is only available if user mapping is enabled.
NOTE: Mappings are saved as separate .MLM files in the folder \\AppData\Roaming\Metalogix\Content Matrix Console - File Share Edition, and the mappings are specific to the particular mapping dialog (Field Types, Users, or Permissions.) they were saved from.
To map permissions:
NOTE: Content Matrix supports many-to-one permissions mappings between source and target.
1.From the File drop-down at the top of the File System Rights to SharePoint Role Mappings dialog, choose the appropriate option. Use the information in the following table for guidance.
|
If you want to ... |
Then ... |
|---|---|
|
load mappings from a previously-saved Metalogix Mapping setting (.MLM) file |
·choose File > Load. AND ·Navigate to and open the mapping file to populate the Mappings dialog. |
|
save the mappings in the dialog as a Metalogix Mapping setting (.MLM) file. |
choose File > Save. |
|
set the current permission mappings in the dialog as the default permission mapping (regardless of the source/target connections being used) |
choose File > Use as Current Default. NOTE: the mappings that display in the dialog are saved to the local machine, so they are persistent whenever the application restarts. |
2.Map source roles to SharePoint permissions as follows:
·From the left (File System) window, select the Item(s) that you want to map.
·From the right (SharePoint) window, select an available Item).
·Click the Map icon.
NOTE: You can Filter items in each window to narrow displayed lists.
The mappings you create will display in the bottom window. (Note that you can also Unmap individually-selected mappings in the bottom window or Clear all mappings from the bottom window.
3.Click [OK] once all desired mappings have been made.
Target Hierarchy Options
The Target Hierarchy Options tab lets you specify the hierarchical structure of migrated content on the target SharePoint environment.
To configure Target Hierarchy - Subsite options:
NOTE: This option is only available when migrating File Share content as a SharePoint site.
1.If you want to migrate source content into SharePoint sub-sites based on the source File Share's folder structure, select Migrate files to sub-site based on Source directory structure.
NOTE: If you also want Content Matrix to use the configured permissions migration settings that have been set in the Permissions Options tab, check the Copy permissions (based on configuration in Permissions tab) box.
2.For Set new site template, select from the list of available SharePoint site templates from the drop-down.
NOTE: If the target hierarchy is being configured as a separate action (that is, via the Paste Hierarchy option), you will also have the option to enable the Use Import Pipeline option. For a full migration, these options are available as either Folder Options or File Options.
To configure Target Hierarchy - Document Library options:
1.For Migrate to Sub-Folders, select how you want File Share content to be migrated into sub-folders in a SharePoint document library. Use the information in the following table for guidance.
|
If you want to ... |
Then ... |
|---|---|
|
migrate all files into the document library on the target without creating any sub-folder structure |
select Do not use folder structure NOTE: When this option is selected, all files will be migrated to the root of the library, even if there is an additional folder structure on the source. |
|
migrates any sub-folders into a SharePoint document library based on the existing folder structure in the source File Share |
select Migrate files to sub-folder based on source directory structure. If you also want to migrate permissions to this new hierarchy structure based on options set in the Permissions Options tab, check the Copy permissions (based on configuration in Permissions tab) box. |
2.If you want Content Matrix to truncate long folder paths or names to avoid migration errors when the SharePoint character limitation (255) is exceeded:
a)Make sure the Truncate long path is checked.
b)If different than the default (200), enter a Max Length Before Overflow value, which determines the folder path length that when reached, will trigger the overflow logic processing. You may adjust this value, but make sure it does not exceed 255.
c)If different than the default (5) enter an Overflow Folder Name Length value, which determines the number of characters (from the first position) that will be used from each source folder name to construct the folder name in the Overflow. You may adjust this value, but make sure it does not exceed 255.
3.For Document Library - Set document library name from:, select which SharePoint document libraries the source contents (files and folders) will be migrated into on the target SharePoint instance. Use the information in the following table for guidance.
NOTE: These options are only available when migrating content as a SharePoint site or document library.
|
If you want to ... |
Then ... |
|---|---|
|
create a SharePoint document library with a specified name |
·select Custom Library Name AND ·if different from the default, enter a text you want to use for the library name. |
|
create a SharePoint document library and name it based on the name of the source root directory/folder (For example, if a source folder for the migration is named "Root1" and this folder contains two sub folders ("Child1" and "Child2"), then when this option is selected, the top level migrated site ("Root1") will have a document library called "Root1," and each sub-site will have a document library named after their source folders. In other words, the site "Child1" will have a document library called "Child1" and the site "Child2" will have a document library called "Child2.") |
·select Source root directory name. NOTE: This option is only available when migrating content as a document library, or if pasting hierarchy and is disabled if the Use Import Pipeline option is checked. |
|
create a SharePoint document library that uses the same name as the source folder containing the documents |
select Source leaf directory name. |
4.For Migrate to Document Set, select how you want to migrate File System content into SharePoint Document Sets. Use the information in the following table for guidance.
NOTES:
·When connected to SharePoint Online, if you have chosen to Use Import Pipeline, these options are disabled because it is not supported. See Objects and Actions Supported Using the Import Pipeline.
·Please see Microsoft's Document Sets planning page for more basic details on document sets.
|
If you want to ... |
Then ... |
|---|---|
|
migrate content into SharePoint Document Sets based on a specified name |
·select Migrate to Document Set based on name in text: AND ·enter the name you want to use for the Document Set. |
|
flatten the hierarchical structure of source content and convert it to a Document Set |
select Flatten folder hierarchy and convert to Document Set. |