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 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 Microsoft 365 Tenant connection (based on the CSOM connection type) `
·A read-only connection to a SharePoint Database (DB)
* As of version 9.3 the Content Matrix Console client application requires Microsoft .NET Framework 4.7.2 to run. Since this .NET requirement applies to the machine on which Content Matrix is installed, 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 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:
SharePoint Server Type |
Local Object Model (OM) Connection (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) |
Microsoft 365 Tenant Connection |
---|---|---|---|---|---|
Microsoft SharePoint 2007 (WSS and MOSS) (Source only) |
- |
- |
- | ||
Microsoft SharePoint 2010 (Foundation and Server) (Source only) |
- |
- |
- | ||
Microsoft SharePoint 2013 (Foundation and Server) |
-- |
** |
- | ||
Microsoft SharePoint 2016 |
-- |
** |
- | ||
Microsoft SharePoint 2019 |
* |
* |
-- |
** |
- |
Microsoft SharePoint Server Subscription Edition |
* |
|
-- |
** |
- |
Microsoft 365 |
- |
- |
- |
* 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 source database, you have the option of making an External Connection to a SharePoint server to allow large file migration.
Required Permissions |
·For SharePoint 2013, 2016, 2019, and SharePoint Server Subscription Edition: The combination of Reader and Execute on the Content Database is the minimum set of required permissions, but the combination of db_dataReader and SPDataAccess can also be used. ·For SharePoint 2007 and 2010: Only Reader or DBReader on the Content Database is required. |
Okta authenticaton support |
N/A |
When to Use |
·When connecting to the source farm ·When there is a need to optimize migration performance ·When there is a requirement to use the Search function in SharePoint 2013 |
Optimal Use Cases |
·Migrating SharePoint 2010 lists and libraries containing Managed Metadata using the Import Pipeline, provided all affected Metadata is migrated to the target and the source and target GUIDs of all affected Metadata is mapped ·Migrating alerts to a SharePoint on premises target ·Connecting SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-enabled environment. NOTE: 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 |
Unsupported Operations |
·Creating and deleting SharePoint objects (because it is a read-only connection) ·Migrating Managed Metadada ·Migrating MySites (because they will be migrated as site collections and will not include some of the User Profile data) ·Migrating InfoPath forms ·Mapping site templates (because it can only detect site templates for any site that exists under the selected source node) |
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.
Required Permissions |
Site collection and db_owner on SharePoint Admin, Config and content databases. NOTE: The connecting account must be the currently logged-in user. |
Okta authenticaton support |
N/A |
When to Use |
·When the Content Matrix Console is installed on a WFE server of an on premises SharePoint farm. ·On the target farm, to help with performance. |
Optimal Use Cases |
·Updating site collection settings ·Migrating web part connections ·Migrating List Template Gallery ·On the source farm: §migrating alerts to SharePoint on premises §migrating Records Centers to SharePoint Online using the Import Pipeline §preserving workflow associations ·On the target farm: §migrating Site collections, including site collection administrators §migrating Master Page Gallery §preserving SharePoint List and List Item IDs §preserving Authorship metadata §setting site quotas §transforming list and site columns into a Managed Metadata column |
Unsupported Operations |
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.
Required Permissions |
Site collection administrator |
---|---|
When to Use |
When the Metalogix Extensions Web Service (MEWS) is installed on the SharePoint farm |
Okta authenticaton support |
Supported* with the following limitations: ·Content Matrix SharePoint Edition only ·Must be used with Web Browser Authentication (which is not auto-detected) NOTE: Because Okta requires web browser authentication, running a job via a PowerShell script and Distributed Migration are not supported. ·Not supported for a connection that uses a proxy and/or certificate EXCEPTION: Okta supports the use of certificates for SharePoint 2010 only. Refer to the article For SharePoint 2010 only: Import security certificate to Trusted Root Certificate Authority on the Okta website for details.
* Only connections to SharePoint 2016 have been tested by Quest. |
Optimal Use Cases |
·Migrating List Template Gallery ·Updating site collection and navigation settings ·On the source farm: §migrating alerts to SharePoint on premises §migrating Records Centers to SharePoint Online using the Import Pipeline ·On the target farm: ·migrating Site collections, including site collection administrators §migrating Master Page Gallery §preserving SharePoint List and List Item IDs §preserving Authorship metadata §migrating site quotas §transforming list and site columns into a Managed Metadata column |
Unsupported Operations |
·Connecting to SharePoint 2019 in a FIPS-enabled environment |
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.
Required Permissions |
Site collection administrator |
When to Use |
When making a site-level connection to SharePoint Online |
Okta authenticaton support |
N/A
|
Optimal Use Cases |
·Migrating libraries that contain .aspx files, even if migration using the Import Pipeline is enabled ·Migrating OOB and SPD workflows ·Preserving major, minor, and draft versions of a document ·Preserving Web Part views (in most cases) ·Transforming list and site columns into Managed Metadata columns |
Unsupported Operations |
·Preserving list/library settings such as Quick Edit, Open document in browser, Launch form in a dialog and Allow items to be downloaded to offline clients ·Preserving workflow instances |
Microsoft 365 Tenant Connection
The Microsoft 365 Tenant connection works the same as a CSOM connection to an Microsoft 365 environment, but since it connects at the tenant level it can also be used for the migration of site collections, MySites, and Managed Metadata.
Required Permissions |
SharePoint Administrator (and Site Collection Administrator for each site collection in the Microsoft 365 tenant environment) |
Okta authenticaton support |
N/A |
Optimal Use Cases |
From an on-premises source: ·Migrating Site collections, including site collection administrators ·Migrating Managed Metadata (This also requires the Term Store Administrator role) ·Transforming list and site columns into a Managed Metadata column ·Migrating SPD workflow associations for lists and content types |
Unsupported Operations |
On the target: ·Preserving workflow instances ·preserving Web Part Views |
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.
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center