Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - SharePoint Edition User Guide

Introduction Entering the License Key Metalogix Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to SharePoint Online Using the Import Pipeline Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to SharePoint Online and SharePoint 2019 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 Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Document Sets are Migrated How Navigation is Migrated How MySites are Migrated How Managed Metadata, Terms, and Term Stores are 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 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 Incremental Migration 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 Migration Frequently Asked Questions About Us

Migration Limitations When Using Office 365 OAuth with MFA Authentication

The following migration options are currently not supported when Office 365 OAuth with MFA is used as the Authentication Type,  and they will be disabled.

NOTE: If your SPO tenant is configured for Multi Factor Authentication and it is important for you to migrate these objects, you will need to use Office 365 Web Browser Authentication instead. Office 365 OAuth/Standard/ADFS Authentication does not work in an MFA-configured environment.

·Navigation Links and Headings: Quick launch navigation (left-hand navigation) and the global navigation (top bar navigation).

NOTE: Tree View settings will be migrated.

·The following List Settings:

§Survey Options (under list settings for Survey List)

§Browser enabled InfoPath form templates (that is, they will not be browser-activated at the target)

·Web Parts

·Nintex Forms

·Nintex Workflows

·SPD 2010 style workflows.

NOTE: Even if the options are checked, SPD 2010 style workflows and Nintex workflows will not be migrated for Office 365 OAuth with MFA Authentication.  SPD 2013 style workflows, however, will be migrated.

Preserve Workflow Options

·Content type InfoPath forms

·List and Site level content type information management policies.

Migrating to SharePoint Online Using the Import Pipeline

Metalogix Content Matrix currently has limited support for migration using the Import Pipeline.

By default, when the Use Import Pipeline option is checked on the List Content Options tab, Metalogix Content Matrix will try to use the SPO Provided Azure Containers when migrating to a SharePoint Online tenant.  However, if you want to use Azure Private Containers, once the Azure Storage Connection String has been added to the EnvironmentSettings.xml file, it will populate the Azure Storage Connection String field of the List Content Options tab and you may select this option.

For detailed information on additional system and configuration requirements for using the Import Pipeline, please see:

·Configuring Settings for Migrations Using the Import Pipeline


·the Metalogix Content Matrix Performance Optimization Guide PDF document included in the installation ZIP file, which includes instructions for configuring Azure Private Containers.

Excluding Individual Items from a Migration Usng the Import Pipeline

It is possible to migrate individual lists and document libraries that are supported by the Import Pipeline using CSOM instead of the Import Pipeline, even if Use Import Pipeline is enabled on the Copy Options > List Content Options dialog.

To exclude individual items from Import Pipeline migration:

1.Navigate to ApplicationSettings.xml (located by default in <Drive>\Users\<USER>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - SharePoint Edition) and open it in a text editor.

2.Navigate to the ListNamesToIgnoreForAzure entry. The default code block is shown below:


3.In the Value element, insert the internal names of the lists and document libraries to be excluded from using the Import Pipeline during migration.

If multiple lists and libraries are provided, they must be separated by the '|' character, as shown in the default code block above.

4.Save and close ApplicationSettings.xml.

Objects and Actions Supported Using the Import Pipeline

Supported Objects

The following is a list of objects that can be migrated using the Import Pipeline:



EXCEPTION:  If the scope contains unsupported lists, the lists themselves will migrate over the CSOM connection, but the migration of alerts for these lists will fail, as CSOM connections do not support the migration of alerts.



·Custom lists

·Discussion boards, including versioning for discussion topics and replies (as opposed to non-Azure migrations, which do not migrate discussion topic versions).

NOTE:  Featured Discussion and Best Reply metadata is currently not supported.

·Document libraries

·Issue tracking


·Managed metadata (also known as taxonomy fields) in lists and libraries

If using a SharePoint 2010 Database connection as the source, then before migrating lists and libraries containing managed metadata using the Import Pipeline, all affected metadata must already be migrated to the target (using a non-database connection) and the source and target GUIDs of all affected metadata must already be mapped. For information about mapping GUIDs, see GUID Mapping.

·Project tasks

·Surveys with single or multiple responses

NOTE:  Currently, if you are using Office 365 OAuth with MFA Authentication, Survey Options for a Survey list are not migrated.


·large files (up to 2 GB) for all source connection types except Remote Object Model (MEWS), which supports files up to 500 MB

NOTE:  Metalogix Content Matrix uses the value specified for the key SupportedFileSizeInMBUsingMigrationPipeline in the configuration variable file EnvironmentSettings.xml to determine the maximum file size to migrate using the Import Pipeline.  The value of this key is 400 by default, but may be increased (to a value in megabytes) to accommodate large files.  Keep in mind, however, that the larger the file, the more available memory will be consumed, and if the value of this variable exceeds the maximum supported size the migration is likely to fail.  

In order to perform any of the supported migration actions using the Import Pipeline, the applicable options must be checked on the Copy Options Dialog > List Content Options tab.


Unsupported Objects

Migration using the Import Pipeline currently does not support:

·.aspx files

·InfoPath forms

·SharePoint 2007 Publishing Images libraries (which migrate as Asset Libraries over CSOM unless part of an override)

See also How Metalogix Content Matrix Handles Objects Not Supported for Import Pipeline Migration.


Supported Actions

The following is a list of actions that are currently supported for Import Pipeline migration:

·Paste Site Collection

·Paste Site as Sub Site

·Paste All Site Content

·Paste MySites

·Paste List as Folder

·Paste List Content > All List Items and Folders (to an empty document library only, Full Copy mode only)

·Paste Folder

·Paste Folder Content > All List Items and Folders

·Paste Site Objects > Alerts*

·Paste List Objects > Alerts*

* If the scope contains unsupported lists, the migration of alerts for the unsupported lists will fail.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating