Content Matrix 9.11 - File Share Edition

File Options

If you have chosen to migrate folders or files, complete the File Options tab as described below.

To configure File Options:

1.If you want documents within a folder to be migrated, make sure the Include Files box is checked

NOTE:  This option cannot be unchecked if the migration was initiated for individual files.

2.For Replace invalid characters in file names with: select the character that you want to use as a substitute for any characters disallowed by SharePoint.

3.If you imported a modified metadata file and want to migrate custom metadata, check the Migrate external metadata box.

NOTE: This option will be enabled only if metadata has been imported from a  CSV file and the file system connection uses the same source path URL specified in the CSV file.

4.If you imported an SCM report and want to migrate the Matches column, which contains the search terms that were used to identify sensitive content, check the Migrate matches column box.

NOTE: This option will only be enabled if a Quest Sensitive Content Manager (SCM) report has been imported and the file system connection uses the same source path specified in the CSV file.

5.If you want to have a MigrationSourceURL column created on the target, check the Migrate source path column box.  

NOTE: If the Migrate external metadata box is checked, this option will be disabled because a column for the source path Urls specified in the CSV file is always created on the target.

6.Select the action that you want Content Matrix to take If a file with the same name already exists on the target.  Use the information in the following table for guidance.

7.Select the Content type options to use when setting the content type for any files that are migrated to SharePoint.  Use the information in the following table for guidance.

8.If you are migrating at the file (not folder) level want to migrate to a SharePoint Online target using the Import Pipeline, check the Use Import Pipeline box and either:

·keep the default option - SPO Provided Azure Containers

OR

·select Azure private containers (if configured), and enter the Azure Storage Connection String in the following format:
DefaultEndpointsProtocol=https;AccountName={your account name};AccountKey={your account key}

NOTES:  

·When using Azure private containers, you also have the option to Encrypt Azure jobs.  (When using SPO Provided Azure Containers, jobs are always encrypted.)

·Azure/SPO containers do not support migration to document sets. This option will be disabled if a Migration to Document Set option is selected on the Target Hierarchy tab.

·If you are copying files as part of a folder migration, this option will instead appear in the Folder Options tab of the configuration dialog. This option only appears in the File Options tab for the Paste Files action.

Mapping Field Types

You can create field type mappings for files and folders that are being migrated from a File Share to SharePoint when you click the [Edit Field Mappings] button from the Folder Options or File Options dialog.  Mappings are applied to a specific content type on the SharePoint target, which is determined within the migration's configuration options.

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 configure field type mappings:

NOTE: Content Matrix supports one-to-one field type mappings between source and target.

1.From the File drop-down at the top of the Source Fields to Content Type Fields dialog, choose the appropriate option.  Use the information in the following table for guidance.

2.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.

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.To save the mappings in the dialog as a Metalogix Mapping setting (.MLM) file, choose File > Save.

4.Click [OK] once all desired mappings have been made and return to the Configuration Options dialog.

Permissions Options

With respect to SharePoint migrations, it is important to keep in mind that there are three different aspects of permissions to be considered:

·Roles - These are also known as permission levels, and are a collection or rights that can be assigned. In SharePoint it is possible to create custom permission levels (or custom roles).

·Se curable Objects - These are basically permissions or rights that can be assigned to an object in SharePoint. Only users or groups that have the same level of permissions or higher can access the content holding these permissions.

·Principals - These are permission roles that are assigned to a user or group. In order for a user or group to have access to a securable object, they would need to have the same permission rights or higher as the permissions on the object. Users can also have access to secured object if they are a part of a group that has access through its assigned permission level.

Content Matrix can migrate the Principals, but is currently unable to migrate SharePoint Roles or Securable Objects.

In the migration process Content Matrix does not actually create any permissions, but instead it maps the roles between the File Share source and the SharePoint target using its Permissions Mapping dialog. Any permissions that are not included in permissions mapping will not be migrated to the SharePoint target environment.

NOTE:  If you want to use a custom role on the target you must add it to the target before migrating permissions. However, this does not guarantee that it will be used. If another role on the target has a closer match with the permission from the source, it will be used instead.

To configure Permissions Options:

1.To enable all user and permissions migration options, including the ability to edit users and any user mappings that have been configured:

a)Check the Migrate users using explicit user mappings box.

b)Follow the instructions for Mapping Users and Groups.

2.If you want to explicitly map source file system permissions to target SharePoint permissions:

a)Check the Migrate permissions using explicit permission mapping box.

b)Select the applicable option.  Use the information in the following table for guidance.

c)Click [Edit Permissions] and follow the instructions for Mapping Permissions.

3.If you want Content Matrix to compare permissions on the source with the available permission levels on the target and automatically map permissions that are not explicitly mapped, check the Migrate permissions auto-mappings box.  Permissions will be mapped as follows:

Mapping Users and Groups

You can set user and group mappings for migrating content from the Permissions Options tab. This allows you to preserve authorship metadata as well as help integrate the File Share users with the SharePoint permissions model. In some cases, it is possible for users to be automatically imported into the SharePoint environment, however, this is only possible if the File Share source and the target SharePoint environment are working from the same Active Directory (AD). If this is not the case, then users would need to be mapped into SharePoint user accounts on the target, and these accounts must already exist in order for them to be mapped from the source.

NOTE:  If the Author or Editor of any file to be migrated is Builtin\Administrators or BuiltIn\Users, you must explicitly map the account to a user account in SharePoint for permissions to be applied on the target. (There is no SharePoint equivalent to a BuiltIn account, so if it is not explicitly mapped it will not be recognized as a valid user and permissions will not be applied.)

All user and group mappings are globally set, so once a mapping is created it will always be used unless removed or overwritten.

You can map users and groups:

·individually, from the UI

OR

·in bulk, from a CSV file.