By default, when Azure migration is enabled:
·If a library contains both supported and unsupported objects:
§for optimal performance, supported objects will be migrated first using the Azure 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 SupportFileSizeInMBUsingMigrationPipeline 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 Azure Pipeline.
It is possible to migrate individual lists and document libraries that are supported by the Azure Pipeline using CSOM instead of the Azure Pipeline, even if Use Azure Office 365 Upload is enabled on the Copy Options > List Content Options dialog.
To exclude individual items from Azure 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 the Azure 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 one of the following folders:
§For Microsoft Vista, Windows 7, Windows 8, Windows 10: <Drive>\Users\<USER>\AppData\Roaming\Metalogix\Metalogix Content Matrix Console - SharePoint Edition.
§For Microsoft Windows 98, Me, 2000, 2003 or XP: <Drive>\Documents and Settings\<USER>\Application Data\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.
4.In the Value element, insert the internal names of the lists and document libraries to be included for the Azure Pipeline during migration.
If multiple lists and libraries are provided, they must be separated by the '|' character, as shown below.
5.Save and close ApplicationSettings.xml.
The EnvironmentSettings.xml file includes configurable thresholds for Azure/SPO Container 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 Azure when the lower threshold is met.
·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 determing batch size.
Refer to the topic Configuring Azure SPO Pipeline Settings information on changing Azure/SPO Container batch sizes.