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

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.


·Classic (not modern) web parts

NOTE:  For a list of supported web parts, requirements, and limitations, see Using the Import Pipeline to Migrate Web Parts.

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

How Content Matrix Handles Objects Not Supported for Migrations Using the Import Pipeline

By default, when Import Pipeline migration is enabled:

·If a library contains both supported and unsupported objects:

§for optimal performance, supported objects will be migrated first using the Import Pipeline, then unsupported objects will be migrated using CSOM


§objects that are unsupported will be identified as such in the log file.

NOTE: You have the option of overriding the default behavior so that if a library contains both supported and unsupported objects, the entire library will migrate using CSOM.  To do this, change the value of the  key AllowPartialPipelineMigration in the configuration variable file EnvironmentSettings.xml from true to false.

·If a file exceeds the size specified for the key SupportedFileSizeInMBUsingMigrationPipeline in the configuration variable file EnvironmentSettings.xml, it will be migrated in chunks using CSOM.

CSOM Migration Limitation

When a CSOM connection is used, while item IDs for other types of lists can be preserved, library document IDs (and by extension, lookup columns, which rely on these IDs)  are not preserved on the target.  Document ID preservation is only supported for objects migrated using the Import Pipeline.

See also Preserving SharePoint List Item IDs with a CSOM Connection Type.

How Content Matrix Determines Import Pipeline Migration Batch Sizes

When migrating using the Import Pipeline, the EnvironmentSettings.xml file includes configurable thresholds for batch sizes in both number of items (200 by default) and size (1000 MB by default).  Content Matrix determines the size of a batch to upload to SPO when the lower threshold is met.

For example:

·If a library has 20 documents, each of which is 100 MB, Content Matrix will use the size threshold and will create two batches of 1000 MB.

·If a library has 1000 documents, each of which is 1KB, Content Matrix will use the item threshold and will create five batches of 200 items.

NOTE:  If more than one version of an item is being migrated, Content Matrix will count each version as a separate item when determining batch size.

Refer to the topic Configuring Settings for Migrations Using the Import Pipeline for  information on changing batch sizes.

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 C:\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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating