Chat now with support
Chat with Support

Metalogix Content Matrix 9.3 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How Publishing Sites are Migrated to Communication Sites How MySites are Migrated How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Creating and Running a PowerShell Script 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 Migration Frequently Asked Questions
DB_Owner Permission 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 Migrating SharePoint On Premises 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 Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files 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 How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Import Pipeline Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using the Import Pipeline Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

How Navigation is Migrated

Metalogix Content Matrix can copy the navigation settings of a site as a part of a site migration or as a separate action. This includes the quick launch navigation (left-hand navigation) and the global navigation (top bar navigation). Navigation migration can be performed at the site, site collection, and MySite levels.

Metalogix Content Matrix can migrate the navigation settings, and node structure for the global and quick launch navigation. This includes preservation of any navigation that has been modified on the source, or doesn't inherit navigation from its parent site. The main restriction on navigation copying is that the site structure on the target side must be the same as the source side, in order for everything to be preserved. In cases where there has been some restructuring or if some of the endpoints for the navigation have not been migrated, these navigation links will not be created on the target, because there is nothing for the navigation to add (point at).

There are some basic limitations when migrating navigation:

·To be correctly migrated, the navigation content must exist on the target SharePoint side, in the same structure as it exists on the source. This means that in order for a site, list, or library's navigation listings to be migrated correctly to the target, the site, list, or library the navigation is pointing to must exist on the target SharePoint server. If not, the navigation item will not be migrated.

·When migrating navigation as a part of a site copy, Link Correction will be enabled by default. Specifically, the Enable Link Correction option will be enabled and grayed out, forcing link correction to be run. This is because Link Correction helps Metalogix Content Matrix correct and update any of the navigation links to point to the new correct target location. Without Link Correction being checked the navigation would not be able to correct the navigation links with the new data, which would result in the navigation failing to copy, or for the navigation to copy incorrectly.

·When migrating from a SharePoint 2013 source, if the Managed Navigation option is selected for either the global or quick launch navigation settings, Metalogix Content Matrix will migrate it as a Structural Navigation setting. This should still produce results that are similar to the source, but it will be listed under the Structural Navigation setting instead.

·Currently, if you are using the Office 365 OAuth with MFA Authentication, Navigation Links and Headings: Quick launch navigation (left-hand navigation) and the global navigation (top bar navigation) cannot be migrated and these options will be disabled.  You can, however migrate Tree View settings using this authentication type.

How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline

When a Team Site or MySite is migrated  to SharePoint Online using the Import Pipeline, documents that have been shared by a user will be visible in the SharePoint Shared by Me tab of that user, as well as on the Shared With Me tab of the user(s) with whom the document has been shared.


Connection icon

This functionality has been verified for a SharePoint 2016 and 2019 source:

·to migrate MySites to MySites (OneDrives) using  an Object Model (OM) source connection, either local or remote (through the Metalogix Extensions Web Service (MEWS)).


·to migrate Team Sites to Team Sites using one of the above source connection types, as well as Database and CSOM connections.

Current Limitations

Because of functionality not currently supported by Microsoft, the following limitations apply:

·Folders shared with users are not visible in Shared With Me tab after migration.

·Documents shared with an Active Directory Group or SharePoint Group  are not visible in the Shared With Me tab after migration.  Documents are only visible on this tab if they are shared with the user directly.

· Documents are not visible under the Shared With Me tab after a Modern OneDrive site is returned to classic OneDrive mode.

·Because the metadata for the Date Shared and Shared By columns on the Shared With Me tab must be migrated using CSOM (even if the  Use Import Pipeline box is checked), these columns will be blank after migration.

·The  Shared Time shows as the migrated time rather than the actual document shared time.

How Web Parts are Migrated

Metalogix Content Matrix can migrate web parts for:

·landing pages (default.aspx pages)

·web part pages

·publishing content pages, and

·list view pages.

Web parts can be copied as part of a normal migration copy or as a separate action.  

NOTE:  Currently, If you are using Office 365 OAuth with MFA Authentication, classic web parts can be migrated only if you are using the Import Pipeline.

Essentially, Metalogix Content Matrix reads the XML information of the web parts, processes the data, and moves it over to the target side, where the XML is then written out on the target location. Metalogix Content Matrix will automatically perform link correction on the data within the web part (the data for the settings), as a part of the migration.

In order for any custom or third party web parts to be properly migrated, these web parts must be manually installed or created on the target server before migration. Metalogix Content Matrix does not migrate the actual code of the web part, it only migrates the data within the web part. In order for an actual migration, the desired web part must first exist on the target SharePoint instance, otherwise the migration will fail.


Metalogix Content Matrix can preserve web part views, however, there are a few known issues with this. In the case of list view web parts, you need to make sure that the list being referenced has already been migrated to the target to ensure that the web part, and it's view, will migrate properly. If the list being referenced in the web part is within the scope of the migration, then Metalogix Content Matrix will make sure the list has been copied first, and will then copy web parts.

There is an additional web part view limitation when using the CSOM or Tenant connection adapter on the target, where Metalogix Content Matrix is unable to set the type of a web part view. The most common manifestation of this is to have a web part lose its calendar appearance during migration. However, the other properties of that view will still be preserved. The resulting outcome will be that the content within the web part will be correct, but it will not look the same as the source because the view type is different. This can be corrected by manually, after migration, by changing the web part view to match the same web part view on the source.

NOTE:  In some cases the web part view type may migrate correctly. This can only occur if the web part is using the same view type that it was using when it was first created. However, this behavior is not reliable.

There is also a web part limitation on migrating web part connections. Web part connections are connections that exist between web parts (one web part pointing to another web part, etc.). Metalogix Content Matrix is only able to migrate these web part connections if there is an OM connection type (through the use of the Local or Metalogix Extensions Web Service connections) on both the source and target SharePoint environments. Other connection types are unable to access this setting, meaning that if any other connection type is used on either the source or target, the web part connection setting cannot be preserved. This also means that this setting cannot be preserved when migrating to O365 environments.

Using the Import Pipeline to Migrate Web Parts

You can use the Import Pipeline to migrate the classic (not modern) web parts identified in the following table.

NOTE:  Web parts not supported by the Import Pipeline are migrated using CSOM.  However, if Web Part pages or Wiki pages contain non-supported web parts, these web parts will not be migrated.


Web Part Name


Blog Archive

Blog notification

Blog tools



Tools (community admin)

About this community

My membership

Whats happening

Content Rollup

Project Summary

Relevant Documents

Site Aggregator

Sites in category

Table of contents


XML viewer

Content By Query

RSS Viewer

Summary Link(s)


Document library

List View

Media and Content

Page Viewer

Picture Library SlideShow

Content Editor

Getting Started

Image Viewer

Script Editor

SilverLight web part

Social Collaboration


Analytics Hash Tag

Contact Details

Micro Feed

Note Board

Organization Browser

Site Feed

Site Users

User Tasks


XSlt List View


·The same limitations with web part views and connections that apply to CSOM connections also apply when using the Import Pipeline.

·Some web parts require 'Allow Custom Script' setting enabled for the target tenant.  If this is not set at least 24 hours before migration, these web parts will not be migrated.  Refer to the Microsoft article Allow or prevent custom script for details on enabling this feature.

·Closed web parts on the source will be migrated as closed on the target.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating