Chat now with support
Chat with Support

Metalogix Content Matrix 8.9 - Advanced Installation Guide

Software Requirements



Operating System

Any of:

·Windows Server 2003

·Windows Server 2008

·Windows Server 2008 R2

·Windows Server 2012

·Windows Server 2016

·Windows XP Professional

·Windows Vista

·Windows 7

·Windows 8 and 8.1

·Windows 10

All of these Operating Systems are supported on both 32-bit and 64-bit systems.

SharePoint Target Environment

Any of:

·Windows SharePoint Services (WSS) 3.0

·Microsoft Office SharePoint Server (MOSS) 2007

·SharePoint Server 2010

NOTE:  If users are creating Publishing Sites in the SharePoint 2010 environment they are migrating into, it is recommended that the Office 2010 SP1 Windows update is installed on the same system that the Metalogix Content Matrix Console client application is installed on.

·SharePoint 2013

·SharePoint 2016

·SharePoint 2019

·Microsoft Office 365


Any of:

·SQL Server 2000

·SQL Server 2005

·SQL Server 2008

·SQL Server 2008 R2

·SQL Server 2012

·SQL Server 2014

·SQL Server 2016

As well as :

·SQL CE 4.0 SP1

Windows PowerShell

Metalogix Content Matrix Console has the ability to run migrations using a pre-configured PowerShell console, provided that PowerShell Version 3.0 or later is installed prior to Metalogix Content Matrix.

Web Browser

Microsoft Internet Explorer 6.x or later (8.x or higher is required if browser authentication is being used).

.NET Framework

Microsoft .NET Framework 4.6 or later.

Since this .NET requirement applies to the machine on which Metalogix Content Matrix is installed, Metalogix Content Matrix cannot make a local Object Model (OM) connection on a SharePoint 2007 or 2010 environment, because SharePoint 2007 and 2010 require an earlier version of the .NET Framework (v.3.5), which prohibits Metalogix Content Matrix from completing the connection.  Because of this, any migration ‘jobs’ configured to connect to SharePoint 2007 and 2010 environments using a Local OM connection type will cease to work, and these jobs will need to be recreated for use over a different adapter type such as MEWS or DB.

Access Requirements

All of the installation and migration permissions/access requirements can change depending where the Metalogix Content Matrix Console client application is installed. The below requirements are the standard set of requirements if you are installing Metalogix Content Matrix on a non-SharePoint machine (i.e. installing on a machine that is not running SharePoint, but has access to the source and target environments).

If you are installing the Metalogix Content Matrix client application directly on a target SharePoint Server or Web Front End (WFE), then you would need the same permissions that are required for installing the Metalogix Extensions Web Service (MEWS).  



Installing User

The user account that is installing the client only needs permissions to install a client application on the target/installation machine. This is because the Metalogix Content Matrix Installer will attempt to elevate permissions as part of the installation process. However, any user account that is going to be running the Metalogix Content Matrix Console application will require Administrator permission.

Application Pool Accounts

If connecting to a remote, on-premises instance of SharePoint the Metalogix Extensions Web Service can be used (for SharePoint 2007 or later). This is a SharePoint solution file that is installed and will use the Application pool user account. See the Installing and Configuring the Metalogix Content Matrix SharePoint WSPs section of this document for more details and permission specifications.

Server Access

The installing user, and any user launching Metalogix Content Matrix Console, will require Administrator permissions on the local machine.

SharePoint Access

The migrating user requires the following permissions (provided that the Extensions Web Service is installed on the SharePoint target).

·Site Collection Administrator on the target SharePoint environment.

·Farm Administrator on the target SharePoint environment.

·Permissions to access all of the content that is being migrated.


Access to any ports that allow access to the SharePoint Web Application.


A valid license key is required.

Metalogix Extensions Web Services (MEWS)

Metalogix Extensions Web Service is an additional component that can be installed which can be installed on remote SharePoint instances and provides additional permission/access.

See Installing and Configuring the Metalogix Content Matrix SharePoint WSPs for details.


This section describes various installation scenarios, as well as how to install the Metalogix Content Matrix Console client application(s) and the Extensions Web Service.

Basic Installation Scenarios for Content Matrix Console

One of the more powerful aspects of Metalogix Content Matrix Console is its flexibility for installation scenarios. Each Edition of Metalogix Content Matrix Console has multiple scenarios that can be utilized to help with system installation limitations and optimization for performance.

There are three basic scenarios that can be applied when installing Metalogix Content Matrix Console:

1.Installing the console directly on the Source system. This scenario is most likely with SharePoint Edition since the ECM (Electronic Content Management) Editions, such as Blogs and Wikis, File Share, etc., are sufficiently different enough from SharePoint that installing the console on these systems provide any real benefit for migration performance.

2.Installing the console directly on the Target system. In most cases this can be the most beneficial since it will help reduce the network traffic when communicating with the target SharePoint environment during a migration, which helps improve migration performance. Another benefit of this scenario is that it provides the client application with direct access to the local SharePoint Object Model (OM), giving Metalogix Content Matrix greater fidelity when migrating content. This scenario is not possible when migrating to a target SharePoint Cloud environment.

Many companies have internal policies in place that restrict or limit the installation of any software directly on the server, usually due to general security and/or software quality concerns. Depending on the policy, this could mean that all software must go through an approval/testing phase before it is allowed to be installed on the server. The testing/approval process can take anywhere from a few days to a few months depending on the organization. This can be a hindrance if any short timelines are involved with a migration. These strict limitations could also completely prevent any third party software from being installed on a server directly.

3.Installing the console on a third machine that has access to both the Source and Target systems. This is the most common use case for most customers. This scenario allows users to install, run, and even upgrade their version of Metalogix Content Matrix without needing to access the source or target environments. And with the use of the Metalogix Extensions Web Service (installed on the target SharePoint environment) users can install the client on their own machine and still have remote access to the SharePoint Object Model for any on-premise installations, providing the same level of fidelity that the local OM connection would give if Metalogix Content Matrix was installed locally on the target SharePoint server or a Web Front End (WFE).

Connections to other source environments are all roughly similar and only have one method for direct connection. However, there are multiple connection types for SharePoint. These connection types consist of:

·SharePoint Database Connection – This is a read-only connection directly to a SharePoint Database (DB). This connection type is only used in SharePoint Edition for connection to a SharePoint on-premises source environment, and is valid for any version except SharePoint 2019.

·SharePoint Local Object Model Connection – This connection can only be made when Metalogix Content Matrix is installed directly on the target SharePoint server or WFE. It accesses the SharePoint OM locally on the machine, which allows it to preserve more existing metadata and grant deeper access for some Metalogix Content Matrix features.

·SharePoint Remote Object Model Connection – This connection requires the installation of the Metalogix Extensions Web Service on the target SharePoint environment. The Extensions Web Service allows Metalogix Content Matrix to have a remote connection to the SharePoint OM. This grants all of the same access for features and metadata that is available from the Local OM connection (see above). This connection type is available for on-premise installation.

·SharePoint Client Side Object Model Connection – This connection is available for SharePoint 2013 or later environments. While it connects through the SharePoint Client Side Object Model (CSOM), it does not have the same level of fidelity that the Local OM or Remote OM connections have. This connection type is mainly used when connecting to O365 environments, or when remotely connecting to a SharePoint server/WFE that does not have the Extensions Web Service installed.

·SharePoint Native Web Service Connection – This connection type is only possible for SharePoint 2010 environments and earlier. This is similar to the CSOM connection (above) in its feature and metadata restrictions, but uses the SharePoint Native Web Service instead.

Please see the Connecting to SharePoint section of the appropriate edition of the Online Help for complete details.

Related Documents