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

Jobs List

Jobs in Metalogix Content Matrix Console can be managed from the Job List. Jobs are listed for migration actions that have already been run, as well as for actions that have been saved. Jobs List SP

Using Multi-Select

Multi-select can be used to select a number of nodes on the source side Explorer View tree, and migrate those nodes to a target SharePoint instance. Multiple SharePoint connections can be selected at one time, but only to Disconnect or Refresh those connections. If connected to a SharePoint farm or web application, only a single site collection can be selected at a time, however, multi-select can be used on any sub-sites under a single site collection.

This feature also works for migrating a single list or site into multiple target locations at the same time; for example, if you have a document library that you want to migrate into two or more target SharePoint sites. After the library is copied, any number of desired target sites can be selected, as long as they are all under the same target connection node, and when pasted the list will be migrated to all of the selected target site nodes. The basic cases for multi-select are copying: multiple to one, one to multiple, and multiple to multiple.

In addition to using check boxes to multi-select, you can use <Shift> and the <Ctrl> keys in the conventional way.

Limitations of Multi-Select

There are a few limitations when using multi-select. These limitations are:

·Only one node type can be selected at a time - This means that if a SharePoint site node is selected, then only other site nodes can be selected, and included in the action.  

While the content under those nodes will be migrated (as per the selected options), only other site nodes themselves can be selected. This is the same for SharePoint lists/libraries, and folders. When connected to a SharePoint server only a single site collection can be selected at one time, but multiple sites under the site collection level can be selected.

The first node selected in the multi-select will determine what type of node can be included, and if an invalid selection is made, then the node that you tried to select will only blink. For example, if a list is selected, then only other lists, within the site collection, can be selected. If you try to select a SharePoint folder or site, then this is an invalid selection, and the folder or site will blink.

·Column Mapping - Column mapping is not available in some cases when using multi-select. If multiple lists are selected (on the source or target) then the Column Mapping feature will not be available. Some basic examples are: pasting lists (on the source) as folders (on the target), or if pasting list Items into multiple lists on the target.

·Available Context (Right-Click) Menu Options - When using multi-select the options that are available in the context (right-click) menu can change depending on where the multi selection is taking place.

When copying multiple nodes from the source side, only a few context menu options are available. These options are: Copy [Object], Check Links, Delete [Object], Refresh Nodes. Additionally, when multiple source items are selected in the Explorer View, only the Paste [Object] option is available on the target, and not the Paste Special > Paste [Specific Object] option.

If only one source item is selected and pasted to multiple locations, a few more of the Paste context menu options become available. While most of the Paste Special options become available there are still a few of these that are not. When pasting a single node to multiple locations the following options are available: Paste [Object], Paste Special, Check Links, Delete [Object], and Refresh Nodes. The options that are not available for multi-select are under the Paste Special action, and these are: Paste alerts, Paste master page gallery, Paste site navigation, and Paste users. All the remaining context menu options should be available.

Enabling Advanced Mode

Some options in Metalogix Content Matrix are considered "advanced" and are disabled by default.  Options that require Advanced Mode are identified throughout this documentation.

To enable Advanced Mode:

In Metalogix Content Matrix Console ribbon toolbar, choose Settings > Enable Advanced Mode.

NOTE:  When the button is highlighted, Advanced Mode is enabled, and additional options become available for nodes/items selected in Explorer and Item View tabs. Transformations Options  become available as well.

Advanced Mode Enabled

Connecting to SharePoint

There are six  basic connection adapters that can be used to make connections to SharePoint from Metalogix Content Matrix Console:

·A local connection to a SharePoint site or server *

·A remote connection to a SharePoint site or server

·A connection through the SharePoint Client-Side Object Model (CSOM) for SharePoint 2013 or later, and for SharePoint Online at the site level

·An Office 365 Tenant connection (based on the CSOM connection type) `

·A read-only connection to a SharePoint Database (DB)

* As of version 9.0 the Metalogix Content Matrix Console client application requires Microsoft .NET Framework 4.6.2 to run. Since this .NET requirement is on the machine that Metalogix Content Matrix is installed on, Metalogix Content Matrix cannot make a local Object Model (OM) connection on a SharePoint 2010 or earlier environment, because earlier versions of SharePoint  require a lower version of the .NET Framework (v.3.5), which prohibits Metalogix Content Matrix from completing the connection.  Because of this change, any migration ‘jobs’ that are configured to connect to SharePoint or earlier environments using a Local OM connection type will cease to work because of the .NET Framework criteria described above, and these jobs will need to be recreated for use over a different adapter type such as MEWS or DB.

The following table describes the connection adapter types that can be made for each supported version of SharePoint:

SharePoint Server Type

Local Object Model (OM) Connection (Metalogix Content Matrix Console - installed on server)

Remote Object Model (OM) Connection (Metalogix Extensions Web Service installed on remote server)

SharePoint Client Side Object Model (CSOM) Connection

SharePoint Database (DB) Connection (Read Only)

SharePoint Office 365 Tenant Connection

Windows SharePoint Services (WSS) 3.0

-

Green Checkmark

-

Green Checkmark

-

Microsoft Office SharePoint Server (MOSS) 2007

-

Green Checkmark

-

Green Checkmark

-

Microsoft SharePoint 2010 (Foundation and Server)

-

Green Checkmark

-

Green Checkmark

-

Microsoft Office 365

-

-

Green Checkmark

-

Green Checkmark

Microsoft SharePoint 2013 (Foundation and Server)

Green Checkmark

Green Checkmark

Green Checkmark

Green Checkmark

**

-

Microsoft SharePoint 2016

Green Checkmark

Green Checkmark

Green Checkmark

Green Checkmark

**

-

Microsoft SharePoint 2019

Green Checkmark

Green Checkmark

Green Checkmark

-

-

** If Content Matrix Console is installed on a server where SharePoint is also installed, the appropriate version of the adapter will be configured automatically. If SharePoint is not installed on the same machine as the Content Matrix Console, the installer will prompt for the configuration of either a SharePoint 2013 or SharePoint 2016 database adapter, as both cannot exist on the same non-SharePoint machine at the same time. If you need to switch from one version of the database adapter to the other, you will need to first uninstall and then re-install the SharePoint edition using Modify operation.  If you are using Distributed Migration, you will also need to update the database adapter version on the agents.

For each of the direct connections to SharePoint (local OM, remote OM, CSOM, and Tenant) there is a full connection and a read-only connection (with the exception of DB connections, which are read-only by default). The Write and Read-Only connection states are available under the Add Connection menu, and are differentiated in the Explorer View tab by different icons (the read-only icon has a lock over the system connection).

Adding a connection to Office 365 is essentially the same as connecting to any other SharePoint site or server, with a few minor differences. Users can make a site level connection to an O365 environment using the CSOM connection adapter, and they can also make a Site Collection level connection using the Tenant connection adapter.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating