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

Prerequisites for Migrating Managed Metadata Using GUID Mapping

 

Connection icon

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

To be able to migrate managed metadata using GUID mapping , it is recommended that you perform the following steps. While Metalogix Content Matrix supports mapping to existing managed metadata at the target, this method will ensure the best results:

1.Using an Object Model (OM) or CSOM/MEWS connection type on the source, 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.

Managed metadata can now be migrated with a database, Object Model, or Extensions Web Service source connection using GUID Mapping.

Configuring Term Store and Managed Metadata Options

NOTE:  Before configuring Term Store and Managed Metadata options, it is strongly recommended that you review the prerequisites for transforming columns into Managed Metadata.

Simplified UI icon

Unless otherwise noted, if you are using Simplified mode and an option is not available for selection, the default value that displays in Advanced mode will automatically be applied.  If you want to change the value of the option, click [Advanced Mode] and switch to the Advanced mode interface.

Managed Metadata Options

To configure Managed Metadata options:

1.If you are using Advanced mode and want Metalogix Content Matrix to check both the source and target environments to find any existing Managed Metadata term structure and then migrate a copy of the source term structure over to the target, make sure the Resolve managed metadata by name and hierarchy box is checked.

NOTE:  If there are terms that do not exist, they will be added (using the same hierarchy structure with new GUIDs), and if there are terms that already exist the terms on the target will be used.  If you want terms on the target to be overwritten with those on the source, make sure Map term stores for migration is selected, as described in the next step.

2.If you want to map the term store on the source to a term store on the target:  

NOTE: Migrating managed metadata at the site level will only copy the global managed metadata, and will not copy any site collection term sets. Site collection term sets are only copied when the Copy referenced managed metadata and Map term stores for migration options are enabled as part of a SharePoint site or list level migration.

a)Select the appropriate option based on the mode you are using:

§If you are using Simplified mode, click the [...] button to the right of the Map Managed Metadata option.

§If you are using Advanced mode, check the Map term stores for migration box, then click the [...] button.

The Map Term Store dialog displays with a list of all term stores that currently exist on the target.

Map Term Stores Dialog

NOTES:  

§This option is primary used in the following situations:

§When migrating the entire term store (the global term store).

§When migrating term stores by their ID value

§When migrating at the site collection level that uses more than one Term Store, to ensure that the correct Term Store is used.

§This option is required when migrating to an Office 365 Tenant target environment. In such a migration, this option is enabled by default and cannot be deselected.

§If the Resolve managed metadata by name and hierarchy option is selected, this option would only be selected if you want to map and overwrite the values the target.

b)Right click the Source Term Store you want to map, and select the Target Term Store you want to Map to.

NOTE: If the Target Term Store is set to <Exclude> (the default value), the term store will not be mapped. Remember that a 1:1 Relationship must exist between Source/Target term store mappings

3.When you are finished mapping term stores, click [OK].

4.If you want to migrate Managed Metadata columns for items and lists, check the Copy referenced managed metadata box.

NOTE:  This option will not actually create Term Stores. It is recommended that this option be used in conjunction with the Resolve managed metadata by name and hierarchy and/or Map term stores for migration.

5.If you are using Advanced mode and want SharePoint site columns (fields) to be transformed into Managed Metadata fields on the target:

a)Check the Transform specified site columns to managed metadata columns box.

b)Click the […] button.

c)Complete the Configure Transformations for a Site Column dialog as described in the topic Transforming a Site or List Column into a Managed Metadata Columns.

6.If you are using Advanced mode and want SharePoint list columns (fields) to be transformed into Managed Metadata fields on the target:

a)Check the Transform specified list columns to managed metadata columns box.

b)Click the […] button.

c)Complete the Configure Transformations for a List Column dialog as described in the topic Transforming a Site or List Column into a Managed Metadata Columns.

NOTE:  By default, Metalogix Content Matrix migrates terms in batches of 50.  You can, however, change this value (for example, decrease it if you are experiencing timeout errors during the migration operation or increase it if you are migrating an excessively large number of terms or keywords.  However, It is recommended that you not  change the batch size unless absolutely necessary.  See Changing the Managed Metadata Migration Batch Size.

Web Parts Options

If  you want to copy web parts as part of the migration, select the Web Parts Options tab (in Simplified mode, within the Migration Options > Site Element Options section) and select the applicable options.

Simplified UI icon

Unless otherwise noted, if you are using Simplified mode and an option is not available for selection, the default value that displays in Advanced mode will automatically be applied.  If you want to change the value of the option, click [Advanced Mode] and switch to the Advanced mode interface.

Web Parts Options

NOTE:  For special considerations when migrating web parts, see How Web Parts are Migrated.

To configure Web Part Options:

1.If you are using Advanced mode and initiated a site collection or site-level migration and want to Copy Web Parts on Landing Pages, make sure this box is checked.

NOTE:  Landing pages are usually the default.aspx pages, but these pages can also have other names. For example, starting in SharePoint 2010 these have been changed to home.aspx pages when Wiki features are enabled.  While the method to migrate these pages is the same as for other web parts, the logging may be slightly different.

2.If you you are using Advanced mode and want web parts to be copied on any other web part pages (aside from landing pages) or in any publishing content, make sure the Copy Web Parts on Web Part Pages and Publishing Content box is checked.

3.If you you are using Advanced mode and want to copy SharePoint lists or libraries that have a "view" set on them, check the Copy Web Parts on List View pages box.

NOTES:  In some cases these views have web parts added to them, which only appear within that specific view. This option preserves the addition of these web parts within the views.

In SharePoint 2010 there is an issue relating to adding web parts to a list or library "view." When a web part is added to a list or library the "view" option (or the ability to select a specific view) is no longer available for that list either next to the title, or in the ribbon. This is caused by SharePoint 2010, and not by Metalogix Content Matrix.

Metalogix Content Matrix does not currently support the preservation of views on SharePoint 2010 XSLT list view web parts.

4.If you  want to copy web parts that exist on a page but are no longer displayed, select Copy Closed Web Parts.

5.If you you are using Advanced mode and  want to copy HTML content from a "Content Zone" on a page, make sure the Copy Content Zone box is checked.

NOTES:  

§A "Content Zone" is a location on a page (introduced in SharePoint 2010) where general text can be added, AND a web part can also be embedded into that same location (for example, a Wiki page/Wiki content). When selected this option will help ensure that web parts that are embedded in these "Content Zones" will appear in the correct location on the target after migration.  This option is only available when migrating from SharePoint 2010 or later.

§It is recommended that this option be enabled for most migration scenarios.

6.If you are using Advanced mode and want any web parts that are on custom created "Form" pages to be migrated, make sure the Copy List Form Pages box is checked.

NOTES:  

§This option does not support any customizations of an Out Of Box (OOB) form that is  not related to web parts and is customized through the direct modification of the ASPX page (aside from adding or modifying a web part).

§This option is automatically selected if you checked the Copy Customized Form Pages box on the List Content Options tab.

7.If you are copying web parts as a post-migration task and you want to Copy Web Parts Recursively down through the content structure, check this box.

NOTE:  This  option is only available when migrating web parts as a separate action.

8.For Existing Web Part Protocol, select how you want to have Web Parts that already exist on the target handled before migration:

§Delete Existing Web Parts on Target (default)

§Close Existing Web Parts on Target

This will close, but not delete, any web parts that exist on the target, before migration.

§Preserve Existing Web Parts on Target

Permissions Options

For users to be migrated, they must exist on the target side Active Directory (AD), so that SharePoint can authenticate them. A good rule of thumb is if the user cannot be manually authenticated in the target SharePoint instance, then Metalogix Content Matrix will not be able to add them.

In cases where data was migrated and the referenced user cannot be authenticated, Metalogix Content Matrix will set the migrating user account into the files metadata instead, and a warning will be listed in the logs. In these cases user mappings can be set up, to map these users to another account.

You can also migrate only users from a source to a target as a separate action.

If a migration is initiated at the site collection or site level, Metalogix Content Matrix can migrate permission levels as well as permissions. This includes any default permission levels that have been modified, as well as any custom created permission levels.

Connection icon

When migrating permissions levels, the target connection must be a Local or Remote - Extensions Web Service connection to SharePoint 2010/2013/2016, or a Client Side Object Model (CSOM)/Office 365 Tenant connection for an Office 365 source/target.  

EXCEPTION:   The Native Web Service (NWS) connection type can be used on a target SharePoint 2010 server. However, the NWS connection type cannot break inheritance, so permission levels can only be migrated with this connection type if the target SharePoint instance already defines its own permission levels.

Permission levels are a set of permission rights that can be assigned to a user or group as a "permission." Metalogix Content Matrix can migrate these permission levels as part of a site level migration, or they can be migrated separately through the context (right-click) menu.

For example, if there is a custom permission level on the source called "Marketing Team," that is applied to a group and some users, then this permission level would not normally be migrated, unless this option is used. If this option is not used, Metalogix Content Matrix will try to map the permissions over to the target, but will fail because the "Marketing Team" permission level does not exist, even if the users/groups exist, so we will try to match these permissions to the next closest match. If the copy Permission Levels option is used, the permission level will be created on the target SharePoint instance (otherwise it would have to be created manually). Once the permission level is created on the target, all the user/group permissions can be migrate and mapped over to the target SharePoint instance without issue.

NOTE:  If a site level copy is being performed, and the Copy Child Sites recursively option is enabled (in the Site Options section), all the sites, lists, folders, and items under the selected source node will be migrated, and any enabled options for permissions copying will be applied recursively down through the migration. If Copy Child Sites recursively is not enabled, only permissions for the selected (top-level) site will be copied.

Related Documents