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

Viewing StoragePoint Details

Metalogix Content Matrix can display the Metalogix StoragePoint details for any document items that have been offloaded to StoragePoint.

NOTE  Currently, StoragePoint Details functionality will be disabled for SharePoint 2019 as it is not currently supported.

To view StoragePoint details:

1.In Explorer View, navigate to a SharePoint Document Library that contains items that have been offloaded to StoragePoint.

2.Switch to the Items View tab.

3.Select an item, right-click and choose StoragePoint Details.

NOTE:  The StoragePoint Details option will only be available in the menu if the selected items have been offloaded into StoragePoint. If the selected item has not been offloaded to StoragePoint the StoragePoint Details options will not be available. Only one item can be selected at a time.

CONTEN~1_img55

The Storage Point Details dialog provides the below information:

§Address - The web address for the specified item within SharePoint.

§Endpoint Relative Folder - The folder that has been configured as endpoint for the offloaded item (i.e. the location of the item in the offloaded storage space).

§Filename - The StoragePoint file name reference that is left behind in SharePoint after the item has been offloaded.

4.When finished, click [Close].

How Content Matrix Handles Various SharePoint Components

Before configuring a migration, it is important to understand how Metalogix Content Matrix migrates various SharePoint components so that you can plan appropriately.  These include:

Team Sites to SharePoint Online

Master Pages

List Template Galleries

Records Centers (to SharePoint Online using the Import Pipeline

Content Types

Document Versions and Checked Out Files

Ghosted and Unghosted pages

Records Centers to SharePoint Online

Document Sets

Navigation

MySites

"Share With" Metadata (to SharePoint Online using Azure)

Web Parts

Site Themes

Site Features

Managed Metadata

OneNote Notebooks

Users and Permissions

BCS and BDC Data

OneNote Notebooks

Checked Out Files

Customized Form Pages

InfoPath Forms

SharePoint Workflows

Nintex Workflows and Forms

Link Correction

How Team Sites are Migrated to SharePoint Online and SharePoint 2019

If you upgraded from a version earlier than 9.2:

Because of the complexities involved with connecting to Office 365 groups when migrating to SharePoint Online, as of version 9.2 a separate option to Paste as a Modern Team Site is no longer available. Instead:

·Modern team sites will automatically be loaded into the Console as part of the hierarchy without connecting to Office 365 groups.

·You will need to connect to the O365 groups after the migration is completed.

IMPORTANT:  If you have upgraded from a version of Content Matrix that is earlier than 9.2 and have existing jobs that include the Paste as Modern Team Site action (including PowerShell jobs), you will no longer be able to run them.

Team Site Target Template Options

By default, when you configure a migration to SharePoint Online or SharePoint 2019, the option Automatically upgrade Classic Team Sites (STS#0) to Modern Team Sites (STS#3), which is a modern team site with no Office 365 groups, is enabled.

NOTE:  For migrations to SharePoint Online, Content Matrix does not support connections to tenant-level groups at the target.  You can, however, make these connections after completing the migration.

Site Options Upgrade to STS3

The table below describes how team site templates are applied to sites and subsites on the target, based on whether Automatically upgrade Classic Team Sites (STS#0) to Modern Team Sites (STS#3) is enabled.

If the Automatically Upgrade Classic Team Sites option is ...

And ...

Then ...

enabled

Team site (classic experience) (STS#0) is selected on the Configure Site Copying Options > Site Options tab.

the selected site collection/site and any child sites that use or are mapped to the Classic Team Site (STS#0) template will use the Modern Team Site without O365 Groups (STS#3) template on the target.

a non-team site template is selected on the Configure Site Copying Options > Site Options tab.

·the selected site collection/site will use the non-team site template on the target

AND

·any child sites that either use or are mapped to the Classic Team Site (STS#0) template will use the Modern Team Sites without O365 Groups (STS#3) template on the target

disabled

Team site (classic experience) (STS#0) is selected on the Configure Site Copying Options > Site Options tab.

both the selected site collection/site and any child sites that either use or are mapped to the Classic Team Site (STS#0) template will use the Classic Team Site template on the target.

the selected site collection/site uses a non-team site template

·the selected site collection/site will use the non-team site template on the target

AND

·any child sites that either use or are mapped to the Classic Team Site (STS#0) template will use the Classic Team Site template on the target.

How Master Pages are Migrated

The Master Pages Gallery is basically a Document Library at the root of a site.

Metalogix Content Matrix can work with Master Pages at two levels:

·At the Site Collection level, where it can copy master pages and page layouts.

·At the Site level, where it can preserve the master page association.

When a SharePoint site is migrated, Metalogix Content Matrix will run a check to see if a master page with the same name as the source site's master page exists. There are then two main scenarios:

·Migrating from an older version of SharePoint to a newer version of SharePoint - Because master pages are quite different between different versions of SharePoint, when master pages are migrated from an older version of SharePoint to a newer version, a suffix will be appended to the end of the master page name based on the source UI version. For example, if you are migrating from MOSS 2007 to a later version, the master pages will have "_2007" appended to the end of the master page name. If migrating from SharePoint 2010 to a later version, the suffix would be "_2010" instead.

When a SharePoint site is migrated, Metalogix Content Matrix will look for the source master page by name. If the master page name is found, Metalogix Content Matrix will then do another check to ensure that the correct UI version is being used on the target site collection. If this UI version also matches, then the master page will be used for the migrating site. If the UI version is not the same, then the current default master page will be used instead.

If the master page cannot be found by name, then Metalogix Content Matrix will check to see if there is another master page that has the same name plus the appended UI version suffix that would represent the source. For example, if migrating from SharePoint 2013 to SharePoint 2016 and the master page is named "AccountMaster3," then Metalogix Content Matrix will look for a master page with the same "AccountMaster3" name. If that fails it will then look for a master page with the same name plus "_2013" appended to the end, like "AccountMaster3_2013." If this is found, then the same UI version check will be run that is used for the exact same master page name, and the same results will be given.

If no master page with the same name is found, either the direct same name, or the name with the UI version appended to the end, then the current default master page will be used instead.

NOTE: If the master page belongs to a UI version that is not supported by the target SharePoint instance, the master page will be skipped.

·Migrating between similar versions of SharePoint - For migrations that are run between the same basic UI version of SharePoint, such as SharePoint 2013 to SharePoint 2013 and SharePoint 2016 to SharePoint 2016, Metalogix Content Matrix will look for a master page with exactly the same name as the master page on the source. If one is found, then Metalogix Content Matrix will use that master page. If no master page with the same name is found, then the current default master page will be used instead.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating