Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint 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 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 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 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 Content Types are Migrated

Metalogix Content Matrix can migrate content types at the site level. Copying of content types can be done as part of a normal site level copy, or they can be copied separately (at the site level) using the context (right-click) menu.

When Metalogix Content Matrix copies over content types they will be copied to the target site with the same name and fields that they had on the source. All content types that are available within the scope of the migration will be copied. In other words, all content types within the selected source site, as well as all the content types that exist within any sub-sites, will be copied. Metalogix Content Matrix will also copy any content types that the source site inherits from its parent site. The copying of these inherited content types is done in order to maintain any dependencies that may exist.

For example, let's look at a scenario where you have a site (Site 1) that has a parent site (Site 0) and two child sites at the same level (Site 2-a and Site 2-b), and all of these sites have content types. In this example, if you select Site 1 and copy content types, when pasted Metalogix Content Matrix will copy over all the content types from Site 1, Site 2-a, and Site 2-b, and it will also copy over all of the content types from Site 0, in case there are any dependencies. If you select Site 2-a to copy from, then it will only copy over the content types from Site 2-a, Site 1, and Site 0 (again because of the inheritance). But the content types from Site 2-b would not be copied since it is outside the scope of the copy, and there is no inheritance. If Site 0 is selected, then Metalogix Content Matrix would copy over all the content types for all four sites.

Please see the following Microsoft article for more information on SharePoint content types and content type inheritance: http://office.microsoft.com/en-ca/sharepoint-server-help/introduction-to-content-types-HA010149551.aspx.

How Ghosted and Un-Ghosted Pages are Migrated

Metalogix Content Matrix can migrate the following types of pages:

·Ghosted page - A page whose contents are not stored in the content database but are read from a site definition file; a page that has not been customized.  

NOTE:  When ghosted pages are migrated they will remain ghosted.

·Un-ghosted page - A page that has been modified from the site definition file, and whose contents are stored in the content database.  (These are also known as "customized" pages in Microsoft Office SharePoint Services (MOSS) 2007).

NOTES:  

§If un-ghosted pages are migrated between the same version of SharePoint, un-ghosted pages can have their customizations preserved, and be migrated as un-ghosted pages.  

§If un-ghosted pages are migrated between different versions of SharePoint, Metalogix Content Matrix is unable to retain the customizations needed for un-ghosted pages, and will reattach these pages to their page layouts. Once these pages have become ghosted, manual steps would have to be taken in order for them to become un-ghosted again.

Converting Un-Ghosted Pages into Ghosted Pages in a Migration

When migrating between the same version of SharePoint, the Reattach Publishing Page Layouts option on the Configure Copy Options – List Content Options tab allows you to convert un-ghosted pages back into ghosted pages, When selected, un-ghosted pages will be reattached to their page layout, and become ghosted again.

NOTE:  When you copy un-ghosted pages between different version of SharePoint, this option is disabled because the conversion is done automatically.

Metalogix Content Matrix is unable to retain the customizations needed for un-ghosted pages, and will reattach these pages to their page layouts. Once these pages have become ghosted, manual steps would have to be taken in order for them to become un-ghosted again.

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.

Related Documents