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.
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.
Document Set Migration
When migrating from SharePoint 2010 or later, as long as the Copy List Items and Documents option is selected, 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.
|
|
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. |
|---|
Navigation Migration
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.
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.
·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 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, 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.
Classic Web Parts Migration
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.
NOTES:
·Currently, If you are using Microsoft 365 OAuth with MFA Authentication, classic web parts can be migrated only if you are using the Import Pipeline.
·Modern web parts are copied as part of page metadata.
Essentially, 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. 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. 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.
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 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 CSOM or Tenant connection adapter on the target, where 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.). 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 Metalogix 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 M365 environments.