Chat now with support
Chat with Support

Metalogix Content Matrix 9.3 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How Publishing Sites are Migrated to Communication Sites How MySites are Migrated 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 "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 Managed Metadata, Terms, and Term Stores 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 Converting Classic Pages to Modern Pages After a Migration Incremental Migration Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix Creating and Running a PowerShell Script 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
DB_Owner Permission 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 Migrating SharePoint On Premises 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 Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint 2013 and Later 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 How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Import Pipeline Batches Getting Stuck "Error, the batch will be resubmitted" Message Displays When Using the Import Pipeline Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

Initiating a Migration

From the Metalogix Content Matrix Explorer View, you can "copy" an object from the source connection then "paste" it to the appropriate location on the target connection.  You will then be prompted to configure Copy Options.

Before you initiate a migration, it is strongly recommended that you review How Metalogix Content Matrix Handles Various SharePoint Components.  

Migrating as a Site Collection

Metalogix Content Matrix can migrate SharePoint Site Collections and promote sub-sites into Site Collections. These migrations can be made within the same SharePoint instance, or can be performed between two separate SharePoint instances. Any site can be promoted into a Site Collection in the same way any Site Collection can be copied to become a sub-site. The location in the hierarchy of the target node is what determines if a site will copy as a Site Collection or as a sub-site.

 

Connection icon

·For migrations to an on premises SharePoint target, an Object Model (OM) level connection must be made with the target environment.

NOTE:  Due to some User authentication changes that have been made starting with SharePoint 2013, which inadvertently restrict the creation of Site Collections using the SharePoint OM remotely,  Metalogix Content Matrix will use a set of elevated permissions to create Site Collections, which means the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the Site Collection is being created on. A preliminary check will be made before elevation occurs to ensure the migrating user has enough permissions initially to be able to use the elevated Site Collection creation. Creating Site Collections for a SharePoint 2013 or later target with the Local OM connection type, does not have this same restriction, but the same permissions are recommended in case elevated permissions are needed.

·For migration to an SharePoint O365 tenant, an Office 365 Tenant connection must be used.

To initiate a Site Collection migration:

1.In Explorer View, select the source site collection or site that you want to migrate.

2.Right-click and choose Copy Site.

3.Select the target node under which you want to create the site collection.

4.Right-click and choose Paste Site Collection, then choose the desired Mode:

Paste as Site Collection

 

§Admin Mode - This mode is the standard Site Collection copy mode and requires Farm Administrator level permissions on the target SharePoint server in order for the Site Collection to be created, and the content to be migrated into it.

NOTE:  This is the only available option when migrating to an Office 365 Tenant environment, and is the only option that supports host header URLs.

§Self Service Mode - This mode is for use with the "Self Service" feature. The Self Service mode allows for Site Collections to be created even if the user does not have Farm Administrator level permissions on the target and the copy is scoped to the Web application. However, in order for this option to work, this feature must first be enabled on the target.  (Refer to your SharePoint documentation for instructions.)

Once the mode is selected, the Configure Site Collection Copying Options dialog displays.

Continue with Configuring Copying Options.

Migrating MySites

Before you initiate a MySites migration, it is recommended that you review the information in the section How MySites are Migrated.

To initiate a MySites migration:

1.In Explorer View, navigate to the (Farm" or "Web app") connection from which you want to copy MySites.

2.Right-click and choose Copy MySites.

3.Select the target node.

4.Right-click and choose Paste MySites followed by the desired MySite copy type:

CONTEN~1_img68

§Paste MySites (Admin Mode) - This mode is the standard MySite copy mode and requires the set of migration permissions described in Required Permissions for Migrating MySites. This will migrate any selected MySites, including any User Profiles and other content (documents, images, etc.) that exists on the selected MySite.

NOTE:  This is the only option that is available when migrating into an O365 environment, using the Office 365 Tenant connection type.

§Paste MySites (Self Service Mode) - This mode is for use with the "Self Service" feature. The Self Service mode allows for MySites to be created, even if the user does not have the set of migration permissions as described in Required Permissions for Migrating MySites. on the target. In order for this option to work there are two conditions that must be met. The first is that the "Self Service" feature must first be enabled on the target side, and the second is that that target connection must be made to the MySite host site address using a Web App connection.

This option is not available for the MySite Options tab when migrating to Office 365 Tenant environments.

Continue with Configuring Copying Options.

Migrating a SharePoint Site

To initiate a site-level migration:

1.In Explorer View, select the site that you want to copy.

2.Right-click, and choose Copy Site.

3.Select  target node.

4.Right-click and choose Paste Site as Subsite.

Continue with Configuring Copying Options.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating