Content Matrix 9.10 - SharePoint Edition

Using the Import Pipeline to Migrate Classic Web Parts

You can use the Import Pipeline to migrate the classic web parts identified in the following table.

NOTE:  Classic web parts not supported by the Import Pipeline are migrated using CSOM.  However, if Web Part pages or Wiki pages contain non-supported web parts, these web parts will not be migrated.

NOTES:

·The same limitations with web part views and connections that apply to CSOM connections also apply when using the Import Pipeline.

·Some web parts require 'Allow Custom Script' setting enabled for the target tenant.  If this is not set at least 24 hours before migration, these web parts will not be migrated.  Refer to the Microsoft article Allow or prevent custom script for details on enabling this feature.

·Closed web parts on the source will be migrated as closed on the target.

Site Theme Preservation

When migrating from SharePoint 2013 or later (including SharePoint Online), Content Matrix will migrate some additional required components when preserving themes. In these versions there is a hidden list called "Composed Looks" that contains some of the Theme information, and this list also references the MasterPage Gallery for additional information. Content Matrix will also migrate the corresponding items from the "Composed Looks" and MasterPage Gallery. This will be done for each theme that is copied, so if only the current theme is copied, only the related item from the "Composed Looks" list and the related MasterPage Gallery item will be copied as well. If all themes are copied, then all items in the "Composed Looks" list and MasterPage Gallery will be copied.

Site Feature Migration

Content Matrix can copy over site features and activate them as a part of a site level migration. Content Matrix does not actually copy over the feature itself, it only adds the feature to the target site and activates it.

In order for the feature to be added to the target site it must first be manually installed and available on the target server. If the features from the source do not exist on the target, the migration of features will fail, but the remaining content will continue to copy over.

Managed Metadata Migration

Content Matrix can copy Managed Metadata values for items and copy and map term stores from a SharePoint 2010 or later environment into a target SharePoint environment.

Managed Metadata term stores consist of the following Managed Metadata: term groups, term sets, and terms. Term stores cannot be created by Content Matrix, which means that the target side term store must be manually created before any content is migrated. After a term store is created on the target, all the Managed Metadata and term hierarchy structure from the source can be migrated.

The Managed Metadata (or taxonomy) options are available when migrating from SharePoint 2010 Server or later and can be selected at all migration levels (site collection, site, list, and item).

NOTE:  For these options to function properly the term stores must be created on the target before migration, which will then allow for the migration (and mapping) of the terms, and the migration of data using these terms.

The TaxonomyMigrator utility, which is run outside of Content Matrix, can also be used to migrate term groups and term sets.  The utility also creates mapping files, which can be imported and used in future migrations that use the Content Matrix Console.  The utility, along with instructions, is included in the product download zip file. Mappings can then be imported and migrated via the Content Matrix Console.

Prerequisites for Migrating Managed Metadata:

You can migrate Managed Metadata only if all of the following conditions are met:

·The migrating account has the following permissions for the Term Store that will be used:

§Full Access to Term Store and Term Store Administrator for the Managed Metadata Service being used on the target.

NOTE:  It is recommended that the same permissions be set on the source, although Read permissions may be sufficient, depending on your environment).  If you encounter the error The Managed Metadata Service is inaccessible because the current web application has not been granted permissions to access it, it may also be necessary to add the account that the App Pool user is running under in order to have permissions.

§When migrating at the site collection level, or when migrating the Term Store explicitly, it is highly recommended that you map term stores before migration to ensure that the correct term store is being used.

NOTE:  A 1:1 relationship must exist between Source/Target term store mappings.  That is, a term store from the source can only be mapped to one term store on the target, and the same target term store cannot be mapped to more than one source term store.

·You are migrating using the Full Copy mode. (These options are not currently available when running an Incremental copy.)

·When using the Resolve managed metadata by name and hierarchy option, make sure that the default storage location for column specific term sets option is enabled in the target SharePoint environment.  See the Quest Support Knowledge Base article for more information.