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

AND

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

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.

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:

<XmlableEntry>
<Key>ListNamesToIgnoreForAzure</Key>
<Value>FormServerTemplates|SiteAssets</Value>
</XmlableEntry>

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.

If you want to migrate lists created using a third party custom list template and the Base Template ID is not available in the ListTemplateTypes, do the following:

1.Navigate to ApplicationSettings.xml, located by default in the folder  C:\Users\<USER>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - SharePoint Edition.

2.Open ApplicationSettings.xml in a text editor.

3.Navigate to the ListNamesToIncludeForAzure entry. The default code block is shown below.

<XmlableEntry>
<Key>ListNamesToIncludeForAzure</Key>
</Value>
</XmlableEntry>

4.In the Value element, insert the internal names of the lists and document libraries to be included for Azure migration.

If multiple lists and libraries are provided, they must be separated by the '|' character, as shown below.

<Value>TestLibrary1|TestLibrary2</Value>

5.Save and close ApplicationSettings.xml.