Chat now with support
Chat mit Support

Content Matrix 9.10 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration Promotion of First Level Subsites to Site Collections MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration Link Correction StoragePoint Content Migration
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
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
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment 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 Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to 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 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

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.

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 Configuration Settings for Migrations Using the Import Pipeline for information on changing batch sizes and other Import Pipeline configuration settings.

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

Migrating individual Lists/Libraries Created from Third Party Custom List Templates Using the Import Pipeline

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

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen