Chatta subito con l'assistenza
Chat con il supporto

Metalogix Content Matrix 9.4 - SharePoint Edition User Guide

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How SharePoint Sites are Migrated to Modern Communication Sites How MySites are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Master Pages are Migrated How List Template Galleries Are Migrated How Content Types are Migrated Document Version and Checked Out File Limitations How Ghosted and Un-Ghosted Pages are Migrated How Document Sets are Migrated How Navigation is Migrated How Classic Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata is Migrated How Users and Permissions are Migrated How BCS/BDC Data is Migrated How OneNote Notebooks are Migrated How Customized Form Pages are Migrated How InfoPath Forms are Migrated How SharePoint Workflows are Migrated How Nintex Workflows and Forms are Migrated How Metalogix StoragePoint Content is Migrated How Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Converting Classic Pages to Modern Pages After a Migration 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 About Us

How Site Themes are Preserved

Navigation:  How Content Matrix Handles Various SharePoint Components >

How Site Themes are Preserved

 

Connection icon

Preserving themes for a site requires Metalogix Content Matrix to use an Object Model (OM) connection, either local or remote (using the Metalogix  Extensions Web Service (MEWS)) on the target side.

When migrating to/from SharePoint 2013 or later (including O365), Metalogix 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. Metalogix 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.

How Site Features Are Migrated

Navigation:  How Content Matrix Handles Various SharePoint Components >

How Site Features Are Migrated

Metalogix Content Matrix can copy over site features and activate them as a part of a site level migration. Metalogix 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.

How Managed Metadata is Migrated

Navigation:  How Content Matrix Handles Various SharePoint Components >

How Managed Metadata is Migrated

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

 

Connection icon

You can migrate Managed Metadata using any of the following connection types:

·Object Model (OM) Connection - This is either a Local or Remote (Extensions Web Service) connection type and can be used for SharePoint on premises source/target environments.

NOTE:  You can also use either of these connections to migrate managed metatada using GUID Mappings, which may significantly improve performance over choosing to Resolve by Name and Hierarchy, which requires Metalogix Content Matrix to crawl through the entire term store.

·Office 365 Tenant Connection - This is a server level target connection to an Office 365 Tenant environment.

·Client Side Object Model (CSOM) connections  This connection type can only be used with a SharePooin Online target.

·Database Connections - This connection is only supported as a source connection for the migration of metadata using GUID Mapping. There are prerequisite actions to be performed before using this connection type.

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 following TechNet article for more information for SharePoint 2013/2016.

Prerequisites for Migrating Managed Metadata Using GUID Mapping

Navigation:  How Content Matrix Handles Various SharePoint Components > How Managed Metadata is Migrated >

Prerequisites for Migrating Managed Metadata Using GUID Mapping

If you want to migrate Managed Metadata using GUID mapping via the Content Matrix Console (rather than by using the TaxonomyMapping utility), it is recommended that you perform the following steps.

Connection icon

The ability to migrate Managed Metadata using GUID Mapping is currently supported for Local Object Model, Metalogix Extensions Web Service (MEWS), and Database source connections.

1.Migrate the global term store as follows:

a)Select the top-level source node.

b)Right-click  choose Copy Farm Managed Metadata.

c)Select the top-level target node.

d)Right-click and choose Paste Managed Metadata Term Stores.

2.Individually migrate each site collection-level term store to be migrated as follows:

a)Select the source site collection.

b)Right-click and choose Copy Site.

c)Select the target site collection.

d)Right-click and choose Paste Site Object > Managed Metadata Local Sites Collection Group.

e)In the Managed Metadata Options tab, ensure that:

§Resolve managed metadata by name and hierarchy is deselected

AND

§Map term stores for migration is selected.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione