Content Matrix supports migrations to SharePoint Online when the default language used on the source is different than the default language used on the target.

NOTE:  Multilingual migrations have been fully tested for a limited number of language combinations (including English, French, Spanish, Italian, and Arabic). However, you can perform migrations using other language combinations.  If you encounter issues, contact Quest Support.

Prerequisites

·When making a connection to the target, the default language of the connecting account must use the same default language as the source.

EXAMPLE:  If you are migrating from English to Spanish, connect to the target with an account whose default language is English.

·The following keys in the ApplicationSettings.xml file must be set to True before performing a migration to a target with a different default language:

·IsMultiLingualMigration

·SkipExistingColumnsAndContentTypes

Supported Objects

The following objects are supported for cross-language migrations:

·Lists and Libraries

·Columns

·Content Types

·Workflows and Forms

·Users and Permission

·Site and List settings

·Web Parts

·Out of Box items and pages

·Views

NOTE:  Item-level (user-created) content is migrated in the source language.  This is a SharePoint limitation.

The following basic connection adapters are supported for making 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 client side object model (CSOM) connection 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.3 the Metalogix Content Matrix Console client application requires Microsoft .NET Framework 4.7.2 to run. 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 MEWS or DB.

The following table identifies the connection adapter types for each supported version of SharePoint:

*  Currently, if Content Matrix is installed in a FIPS-enabled environment, you cannot connect to or migrate to/from SharePoint 2019 with a local or remote server connection. For SharePoint Server Subscription Edition in a FIPS-enabled environment, you can only connect using a remote object model connection.  See Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment for more information.

**

·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  a SharePoint 2013, SharePoint 2016, or SharePoint 2019/Subscription Edition database adapter, as more than one 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

·You cannot connect to a SharePoint Server database from a machine that has SharePoint Server Subscription Edition installed, or to a SharePoint Server Subscription Edition database from a machine that has SharePoint Server installed.

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

SharePoint Database Connection

The SharePoint Database connection is a read-only connection that accesses the  SharePoint data by reading the content databases directly from the SQL server used by an on premises SharePoint farm.

NOTE:  After connecting to a 2013 or later SharePoint database, you have the option of making an External Connection to a SharePoint server to allow large file migration.

Local Object Model (OM) Connection

The local Object Model connection accesses the SharePoint on premises OM API locally on the machine, which allows it to preserve more existing metadata and grant deeper access for some Content Matrix features.

Remote Object Model Connection Using Metalogix Extensions Web Service

The Remote Object Model connection allows Content Matrix to have a remote connection to the SharePoint on premises OM API through a SharePoint solution, which grants all of the same access for features and metadata that is available from the Local OM connection.

Client Side Object Model (CSOM)

The Client Side Object Model connects through the SharePoint CSOM. It is the only method for making site-level connections to SharePoint Online.  

Office 365 Tenant Connection

The Office 365 Tenant connection works the same as a CSOM connection to an Office 365 environment, but since it connects at the tenant level it can also be the migration target for site collections, MySites, and Managed Metadata.

You can connect to SharePoint on premises by:

·making a read-only connection to a SharePoint database

OR

·by connecting to a SharePoint site or server at the farm, Web application, or site level.