Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to O365 Using the Azure Pipeline/SPO Containers Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files Adding PowerShell Snap-Ins for the Application Framework Content Matrix PowerShell Commandlet List
Metalogix.System.Commands Metalogix.SharePoint.Commands Metalogix.Jobs.Reporting.Commands Metalogix.SharePoint.Migration.Commands
Modifying Content Matrix Configuration and Settings Configuring Content Matrix for Distributed and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and Later Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using Azure Item Count at Target is Increased When Migrating Using the Azure Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Azure Pipeline Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

How Users and Permissions are Migrated

Metalogix Content Matrix can migrate SharePoint permissions. Permission migration is broken down into two pieces: permission levels, and user/group permissions. This section will review how to migrate permissions for users/groups.  Metalogix Content Matrix can migrate site, list and item level permissions from one SharePoint instance to another.

There are two methods of migrating permissions. The first method is to copy permissions as a part of a migration action by selecting them in the Copy Options dialog, and the second method is to copy them to a target node using the context (right-click) menu as a separate action.

When talking about permissions in SharePoint it is important to keep in mind that there are three different aspects of permissions to be considered when doing a migration. They are as follows:

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

NOTE: Custom permission levels (Roles) cannot be migrated to target SharePoint 2010 environments if the target is using a Native Web Service (NWS) connection type.

·Securable 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. Metalogix Content Matrix can migrate permissions on securable objects at the SharePoint site, list, folder, and item levels.

·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 secured object, they would need to have the same or higher permission rights as the permissions on the object. Users can also have access to a secured object if they are a part of a group that has access through its assigned permission level.

When permissions are migrated, an algorithm is used to find the best matching permission level (role) on the target, as compared to the source. For example, if a permissions level exists on a source SharePoint environment, and permissions are migrated to the target, Metalogix Content Matrix will look on the target for the closest matching role. Whatever the closest permission level is (by included permissions) will be the permission level that is used on the target. In the case that permission levels (roles) are also migrated, these migrated permission levels will be used, because these created roles will have the closest matching permissions when compared to the existing permissions on the target. If permission levels are not copied, the closest matching permission level will be used instead.

NOTE : Whenever Metalogix Content Matrix copies content, it will migrate the user groups that are associated with the migrating content, provided they have not already been copied to the target server.

Limitation when Migrating Modified Permissions Levels

If you modify a built-in permissions level on the source and you are migrating permissions to a subsite using a CSOM connection on the target (which includes any SharePoint Online target connection), these modifications will not be reflected on the target site and the following message will be logged:

You cannot customize permission levels in a web site with inherited permission levels.

This issue will not occur:

·using  a local or remote Object Model (OM) target connection.

OR

·when the target is a site collection, regardless of the connection type.

Migrating Access Request Settings

Access Request Settings is an option within a site's permissions that allows SharePoint to specify a specific user's (usually the site administrator's) email and/or contact information. This happens when another user is requesting authorization to access that site, and is done through a link on the site in question. When enabling this checkbox, you should take into account the following considerations:

 

Connection icon

The only supported target environment for this setting is SharePoint on-premesis 2013 or later, and the only supported adapters are the Object Model (OM) and the Metalogix Extension Web Service (MEWS) adapters. CSOM connections are not supported.

·This setting is only supported when performing the following actions: Paste Site Collection, Paste Site as Subsite, and Paste Site Content > All Site Content. This option is not supported for any other migration actions.

·Allow access requests must be enabled in the Access Requests Settings options on the target.

·In order to manage email triggers, the following flags have been added to the product's ApplicationSettings.xml file: EnableAccessRequestItemsNotifications (set to 'False' by default) and NotificationEmailAddress (set to 'CM@CM.CM' by default). The following table describes what flag values to set to achieve the desired outcome:

Desired Outcome

EnableAccessRequestItemsNotifications setting

NotificationEmailAddress setting

An email is to be sent to the user whose email is specified in the Access Request Settings options on the target.

True

Any valid or invalid email address.

An email is to be sent to a different email address than the one specified in the Access Request Settings options on the target.

False

The email address of the intended recipient.

No notification emails are to be sent.

False

Any invalid email address (CM@CM.CM by default).

Preserving Automap Authorship Columns

Metalogix Content Matrix can preserve the Authorship fields for any data it migrates. These four main metadata fields will be preserved by default for SharePoint 2010 and later. Please see Connecting to SharePoint for more specific details on the different SharePoint connection types.

EXCEPTION:   When migrating to a target SharePoint 2010 instance using the NWS connection, items that have a "Pending" status will migrate Authorship data for major (not minor) versions only, and Authorship data will not be migrated for items that have a "Rejected" status.

If migrating to SharePoint 2007 (MOSS 2007 or WSS 3.0) these fields will only be preserved in cases where the OM connection is used on the target (through a local or extensions web service connection). In the case where the Native Web Service (NWS) connection is used on a SharePoint 2007 target, the Automap Authorship Columns feature is available. This feature is only available when migrating to a SharePoint 2007 target, using the NWS adapter.

Connection icon

If an OM connection to the target SharePoint 2007 instance is not available, a Native Web Service (NWS) connection must be used instead. Unfortunately when the NWS connection is used to the target SharePoint 2007 instance, it is not able to access these Authorship fields. This is because these four fields are special system fields in SharePoint, and need to be accessed in a different way, which is not possible with the NWS connection. However, even in cases where the NWS connection is used to connect to the target, Metalogix Content Matrix does have another method it can use to migrate a copy of this data, and this is through the Automap Created/Modified Meta Info check-box option.

The Automap Created/Modified Meta Info check-box option is available in the Mapping Options section of the copy options dialog, but is only available if a NWS connection has been made to the target SharePoint site. The option is hidden for the other connection types, as the other connection will automatically preserve the Authorship data.

When selected this option will write the Authorship data into four newly created field columns. The new columns that are created on the target side are: Created (Migration), Created By (Migration), Modified (Migration), and Modified By (Migration). After these new columns have been created, Metalogix Content Matrix will copy the original Authorship data into them, and the actual Authorship columns on the target will be populated with the migration account and the time of the migration. Using this method allows for the NWS connection to create a copy of the source side Authorship data on the target, despite its limitation for not being able to access those actual fields.

The columns for the original Authorship fields will be filled with the migration account data and migration time. In order to see the four new Authorship "Migration" fields on the target, the current View of the content on the target side would need to be changed/modified to include them.

This feature should work for most data, however, there are some cases that it may not work correctly for. Some files, such as Microsoft Word files, store the Authorship data in a slightly different manner, and as a result the metadata values for these fields may not always be preserved in the additional columns.

Related Documents