Chat now with support
Chat with Support

Metalogix Content Matrix 9.2 - SharePoint Edition User Guide

Introduction Entering the License Key Metalogix Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Migrating to SharePoint Online Using the Import Pipeline Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to SharePoint Online and SharePoint 2019 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 Records Centers are Migrated to SharePoint Online Using the Import Pipeline How Document Sets are Migrated How Navigation is Migrated How MySites are Migrated How Managed Metadata, Terms, and Term Stores are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline How Web Parts are Migrated How Site Themes are Preserved How Site Features Are 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 Link Correction Works
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action Incremental Migration 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 Migration Frequently Asked Questions About Us

Managed Metadata Options

The Managed Metadata (or taxonomy) options are available when migrating from SharePoint 2010 Server or later (including Office 365 tenants), 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.

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 connection to an Office 365 Tenant environment. If using an Office 365 Tenant environment as a source, this is the only connection that can be used. If using any other environment as a source, this connection type can only be used as a target.

·Client Side Object Model (CSOM) connections  This connection type can only be used by Office 365 environments, and can be used for either a source or target connection.

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

Prerequisites for transforming columns into Managed Metadata:

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

·You are migrating into a SharePoint 2013 Server or later target and 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

§Additionally, for O365 environments: Global Administrator and Term Store Administrator.

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.

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  on premises 2013 or later, or a Client Side Object Model (CSOM)/Office 365 Tenant connection for an Office 365 source/target.  

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.

Configuring Permissions Options

If  you want to copy permissions as part of the migration, select the Permissions 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.

Permissions Options

To configure Permissions Options:

1.If you want to Copy site permissions:

§make sure this option is selected

AND

§make sure the appropriate additional options are selected.  Use the information in the following table for guidance.

If ...

Then ....

·you are using Simplified mode

AND

·you want to allow any custom permission levels (roles) that exist on the source to be copied and created onto the target (includes any default permissions that have been modified, or any custom permission level that have been created)

make sure Migrate Site with Broken Inheritance is selected.

NOTE:  If you are using Advanced mode, this option called Ignore permissions inheritance for root node.

·you are using Advanced mode

AND

·you want to allow any custom permission levels (roles) that exist on the source to be copied and created onto the target (includes any default permissions that have been modified, or any custom permission level that have been created)

make sure the Copy permissions levels box is checked.

·you are using Advanced mode

AND

·you are migrating to SharePoint 2013 or later

AND

·you want to copy any access request settings (provided that the target SharePoint location is configured for sending emails)

make sure the Copy access request settings box is checked.

 

Connection icon

This option is only available with an OM or MEWS adapter.

See also Migrating Access Request Settings.

·you are using Advanced mode

AND

·you want to copy any associated group settings for any sites that are within the scope of the migration.

make sure the Copy associated group settings box is checked.

NOTES: Associated groups are the Owners, Members, and Visitors groups that are created by default and associated to each site at its creation.

2.If you want Copy list permissions, make sure this option is selected.

NOTE:  This option is not available if you initiated a folder- or item-level migration.

3.If you  want to Copy Content Permissions, make sure this option is selected.  

NOTE:  If you are using Advanced mode, content is broken out into two separate options: Copy Folders and Copy Items.  (Copy Folders is not available for an item-level migration.)

4.If you are using Advanced mode and want the existing permissions inheritance of the root node being migrated to be ignored and  have any permissions levels and permissions migrated directly for the site, make sure the Ignore permissions inheritance for root node box is checked.

NOTE:  If you are using Simplified mode, this option is called Migrate Site with Broken Inheritance.

5.If you are using Advanced mode and are migrating permissions as a post-migration task and want to Delete pre-existing permissions on the target, check this box.

NOTE:  If you are performing a full migration, this box will be checked and disabled, to ensure that any permissions that exist on the target, within the scope of the migration, are deleted so that no issues are encountered when the migration is run and the source permissions are migrated

6.If you want to copy permissions levels from the source to the target by matching names make sure Map permission levels by name is selected.

For example, if an "Admin" role exists on both the source target, the "Admin" permissions on the source will map over to the "Admin" role on the target, even if they use different levels of permissions. Any item, group, or user that has "Admin" permissions on it will still have "Admin" permissions, though the level of access might be slightly different (if the rights for the "Admin" role are different between the source and target servers).

NOTE:  If this option is selected and the role does not exist on the target, it will be skipped.

7.If you are using Simplified mode and want  groups to be mapped to the target site by name instead of by membership, make sure the Map Groups by Name option is selected.

NOTE:  If you are using Advanced mode, this option is located on the Mapping Options tab.

9.If you chose to Map groups by name and you also want to overwrite any groups on the target, make sure the Overwrite existing groups option is selected.

NOTE:  If you leave this box unchecked, users will be appended into existing groups.

10.If you are using Advanced mode and want roles on the source to be mapped to different roles on the target:

a)Check the Override role mappings box.

b)Click the […] button.

c)Follow the procedure for Mapping Roles.

NOTE:  When you use this option, any other existing permissions role mapping that is set up will be overridden.

11.If you are using Advanced mode and you want to set up a default user account that will be mapped to when migrating content in cases where the source user does not exist on the target:

a)Check the Map missing users to: box.

b)In the text box, enter the user name to use in the Domain\User account format.

NOTES:  

§If you are using Advanced mode, this option is located on the Mapping Options tab.

§This text field does not authenticate, so any spelling mistakes will not be automatically corrected.

§If you want to set more than one user mapping, use Global User Mappings.

§This option does not apply to the Primary Administrator or Secondary Administrator options, when migrating a SharePoint Site Collection.

12.If you are using Simplified  mode and want to map users, domains, URLs, and/or GUIDs between source and target, click [Open Global Mappings...] to display the Specify Global Mappings... dialog.  Continue with the procedure for Global Mappings.

NOTE:  If you are using Advanced mode, this option is located on the Mapping Options tab.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating