Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to O365 Using the Azure Pipeline/SPO Containers Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files 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 and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies 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 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 Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations 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 on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using Azure Item Count at Target is Increased When Migrating Using the Azure Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Azure Pipeline Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

How Document Sets are Migrated

When migrating from SharePoint 2010 or later, as long as the Copy List Items and Documents option is selected, Metalogix Content Matrix will automatically copy existing Document Sets.  You also have the option of copying snapshots (versions) of both the Document Sets themselves and the files stored within them.

Note that you can also configure copying options to apply new Document Sets to libraries, lists, folders, and documents as part of a migration.

Connection icon

When a CSOM target connection is used, Document Set version history migration does not preserve associated managed metadata, users and groups, or lookup fields.  These limitations do not apply, however, when an Object Model target connection is used.

How Navigation is Migrated

Metalogix Content Matrix can copy the navigation settings of a site as a part of a site migration or as a separate action. This includes the quick launch navigation (left-hand navigation) and the global navigation (top bar navigation). Navigation migration can be performed at the site, site collection, and MySite levels.

Metalogix Content Matrix can migrate the navigation settings, and node structure for the global and quick launch navigation. This includes preservation of any navigation that has been modified on the source, or doesn't inherit navigation from its parent site. The main restriction on navigation copying is that the site structure on the target side must be the same as the source side, in order for everything to be preserved. In cases where there has been some restructuring or if some of the endpoints for the navigation have not been migrated, these navigation links will not be created on the target, because there is nothing for the navigation to add (point at).

There are some basic limitations when migrating navigation:

·To be correctly migrated, the navigation content must exist on the target SharePoint side, in the same structure as it exists on the source. This means that in order for a site, list, or library's navigation listings to be migrated correctly to the target, the site, list, or library the navigation is pointing to must exist on the target SharePoint server. If not, the navigation item will not be migrated.

·If the Native Web Service (NWS) connection type is used on the target, the navigation will still be able migrated, however, the navigation order cannot be preserved. This is because SharePoint's NWS connection does not allow for the ordering to be set through its methods. The NWS connection type can be used on the source, because this limitation only applies if the NWS connection is used on the target side.

·When copying navigation from a SharePoint 2003 (SPS 2003 or WSS 2.0) source, only the quick launch settings and structure can be copied. The global navigation cannot be copied because in SharePoint 2003 the global navigation on (or top bar navigation) is reserved for links to create new sites and other administration functionality. This administration functionality exists in a different location in later version of SharePoint, so this issue is non-existent with SharePoint 2007 and later.

·When migrating navigation as a part of a site copy, Link Correction will be enabled by default. Specifically, the Enable Link Correction option will be enabled and grayed out, forcing link correction to be run. This is because Link Correction helps Metalogix Content Matrix correct and update any of the navigation links to point to the new correct target location. Without Link Correction being checked the navigation would not be able to correct the navigation links with the new data, which would result in the navigation failing to copy, or for the navigation to copy incorrectly.

·When migrating from a SharePoint 2013 source, if the Managed Navigation option is selected for either the global or quick launch navigation settings, Metalogix Content Matrix will migrate it as a Structural Navigation setting. This should still produce results that are similar to the source, but it will be listed under the Structural Navigation setting instead.

How Web Parts are Migrated

Metalogix Content Matrix can migrate web parts for:

·landing pages (default.aspx pages)

·web part pages

·publishing content pages, and

·list view pages.

Web parts can be copied as part of a normal migration copy or as a separate action.  

Essentially, Metalogix Content Matrix reads the XML information of the web parts, processes the data, and moves it over to the target side, where the XML is then written out on the target location. Metalogix Content Matrix will automatically perform link correction on the data within the web part (the data for the settings), as a part of the migration.

In order for any custom or third party web parts to be properly migrated, these web parts must be manually installed or created on the target server before migration. Metalogix Content Matrix does not migrate the actual code of the web part, it only migrates the data within the web part. In order for an actual migration, the desired web part must first exist on the target SharePoint instance, otherwise the migration will fail.

The migration of web parts does not require the use of the Object Model (OM) connection type on the target (through the use of the Local or Extensions Web Service connections). The SharePoint Native Web Service (NWS), SharePoint Client Object Model (CSOM), and the Office 365 Tenant (Tenant) connection types can be used to migrate web parts. While there are a few limitations for the NWS, CSOM/Tenant connection adapters (mainly around web part views), in regards to web part, both the web part zone and ordering should be preserved.

Metalogix Content Matrix can preserve web part views, however, there are a few known issues with this. In the case of list view web parts, you need to make sure that the list being referenced has already been migrated to the target to ensure that the web part, and it's view, will migrate properly. If the list being referenced in the web part is within the scope of the migration, then Metalogix Content Matrix will make sure the list has been copied first, and will then copy web parts.

There is an additional web part view limitation when using the NWS, CSOM, or Tenant connection adapter on the target, where Metalogix Content Matrix is unable to set the type of a web part view. The most common manifestation of this is to have a web part lose its calendar appearance during migration. However, the other properties of that view will still be preserved. The resulting outcome will be that the content within the web part will be correct, but it will not look the same as the source because the view type is different. This can be corrected by manually, after migration, by changing the web part view to match the same web part view on the source.

NOTE:  In some cases the web part view type may migrate correctly. This can only occur if the web part is using the same view type that it was using when it was first created. However, this behavior is not reliable.

There is also a web part limitation on migrating web part connections. Web part connections are connections that exist between web parts (one web part pointing to another web part, etc.). Metalogix Content Matrix is only able to migrate these web part connections if there is an OM connection type (through the use of the Local or Extensions Web Service connections) on both the source and target SharePoint environments. Other connection types are unable to access this setting, meaning that if any other connection type is used on either the source or target, the web part connection setting cannot be preserved. This also means that this setting cannot be preserved when migrating to O365 environments.

How Customized Form Pages are Migrated

It is possible to migrate your SharePoint Designer (SPD) customized Form pages when migrating a SharePoint list, library, site, or Site Collection.


Connection icon

Customized form pages cannot be migrated when a database (DB) connection type is used on the source.

When migrating between the same versions of SharePoint, Metalogix Content Matrix will copy the customized Form page to the target environment, and all customizations will be preserved.

If migrating between two different versions of Metalogix Content Matrix will only migrate the contents of the Content Area - PlaceHolderMain on the Forms page. This is because not all of the file content is compatible between SharePoint versions. Each Forms page only has one Content Area, so Metalogix Content Matrix will search the page for the Content Area tag, and will migrate the contents of "PlaceHolderMain" to the target.

In SharePoint 2007 and later, the Content Areas are marked with the tag:

<asp:Content ID="Content7" ContentPlaceHolderId="PlaceHolderMain" runat="server">

NOTE: Depending on the Form page customizations in your source environment, the Content Areas tags may appear different from the tag listed above.

If content is found under the tags in the content area, then Metalogix Content Matrix will move that data to the same section of the content area on the target SharePoint Form page. Only the content of these tags are migrated to the target, instead of migrating the actual page itself. If any of the customizations actually block Metalogix Content Matrix from finding these tags on the source page, then the contents will not be migrated because Metalogix Content Matrix will not be able to find anything to migrate (but the web parts will still be migrated).  In fact, when the Copy Customized For Pages option is selected, Metalogix Content Matrix will automatically select the Copy Web parts on Form Pages check-box option (under the Web Part Options tab) because web parts must be copied if migrating Form page customizations.

Related Documents