Chatta subito con l'assistenza
Chat con il supporto

Metalogix Content Matrix 9.4 - SharePoint Edition User Guide

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Connecting and Migrating Account Requirements Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
How Team Sites are Migrated to Modern Team Sites How SharePoint Sites are Migrated to Modern Communication Sites How MySites are Migrated How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline 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 Classic Web Parts are Migrated How Site Themes are Preserved How Site Features Are Migrated How Managed Metadata is 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 Metalogix StoragePoint Content is 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 Configuring Hub Sites Incremental Migration Using PowerShell with Content Matrix
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

How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline

Navigation:  How Content Matrix Handles Various SharePoint Components >

How "Share With" Metadata is Migrated to SharePoint Online Using the Import Pipeline

When a  SharePoint 2016 or 2019 Team Site or MySite is migrated to SharePoint Online using the Import Pipeline, documents that have been shared by a user will be visible in the OneDrive Shared by you tab of that user, as well as on the Shared with you tab of the user(s) with whom the document has been shared.  Users' Access Request Settings are also copied for site collection and site level migrations.

NOTE: For Access Request settings, a user's email will be correct for the target as long as the email was provided and the user was mapped correctly on the source.

Additionally, if you are migrating to a newly created site collection in SharePoint Online, SharedWithUsers are added to sites and lists.

Connection icon

This functionality has been verified for a SharePoint 2016 and 2019 source:

·to migrate MySites to OneDrives using  an Object Model (OM) source connection, either local or remote (through the Metalogix Extensions Web Service (MEW)).

AND

·to migrate Team Sites to Team Sites using one of the above source connection types, as well as Database and CSOM connections.

Current Limitations

·For SharePoint 2016, the migration of Sharing Details is not supported.

·For SharePoint 2019, Sharing Links are not migrated.  However, shared document are visible and accessible on a user's One Drive.

·Because of functionality not currently supported by Microsoft, the following limitations apply:

§Documents shared with an Active Directory Group or SharePoint Group are not visible in the Shared With Me tab after migration.  Documents are only visible on this tab if they are shared with the user directly.

§Documents are not visible under the Shared With Me tab after a Modern OneDrive site is returned to classic OneDrive mode.

§The Shared Time shows as the migrated time rather than the actual document shared time.

How Records Centers are Migrated to SharePoint Online Using the Import Pipeline

Navigation:  How Content Matrix Handles Various SharePoint Components >

How Records Centers are Migrated to SharePoint Online Using the Import Pipeline

A Records Center is an Enterprise SharePoint site with a number of specialized components and settings.  A Records Center can be migrated either to a Records Center on the target, or to a Classic Team Site with Record Center features activated.

IMPORTANT:  Currently, Content Matrix cannot migrate from a source Team Site to a Records Center on the target using Azure.

 

Connection icon

This functionality has been verified for SharePoint 2010 and 2013 source environments using an Object Model (OM) source connection, either local or remote (through the Metalogix Extensions Web Service (MEWS).

 

When migrating a Records Center to SharePoint Online using the Import Pipeline, Content Matrix preserves the following on the target:

·Content Organizer Settings

·Site and list level Record Declaration Settings

·The following library and folder level Content type-based Based Retention Policy actions:

§Move to Recycle Bin

§Remove all previous versions

§Permanently Delete

§Skip to Next Stage

·Record, hold, exemption status and retention stages

NOTE: You cannot preform an incremental migration for items that have already been declared records or placed on hold on the target.

Current Limitations

Currently, Content Matrix does not migrate the following to SharePoint Online using the Import Pipeline:

·Complex retention actions and custom formulas ( for example, Send to Another Location, custom formulas, start a workflow).

·Retention formulas/stages defined on custom list items

·Record, hold, exemption status and retention stages for custom lists or any list with custom list as base type

·Metadata for items that must be migrated via CSOM (such as Aspx files, InfoPath forms, and large files).

In addition, you cannot currently preform an incremental migration for items that have already been declared records or placed on hold on the target.

How Master Pages are Migrated

Navigation:  How Content Matrix Handles Various SharePoint Components >

How Master Pages are Migrated

The Master Pages Gallery is basically a Document Library at the root of a site.

Metalogix Content Matrix can work with Master Pages at two levels:

·At the Site Collection level, where it can copy master pages and page layouts.

·At the Site level, where it can preserve the master page association.

When a SharePoint site is migrated, Metalogix Content Matrix will run a check to see if a master page with the same name as the source site's master page exists. There are then two main scenarios:

·Migrating from an older version of SharePoint to a newer version of SharePoint - Because master pages are quite different between different versions of SharePoint, when master pages are migrated from an older version of SharePoint to a newer version, a suffix will be appended to the end of the master page name based on the source UI version. For example, if you are migrating from MOSS 2007 to a later version, the master pages will have "_2007" appended to the end of the master page name. If migrating from SharePoint 2010 to a later version, the suffix would be "_2010" instead.

When a SharePoint site is migrated, Metalogix Content Matrix will look for the source master page by name. If the master page name is found, Metalogix Content Matrix will then do another check to ensure that the correct UI version is being used on the target site collection. If this UI version also matches, then the master page will be used for the migrating site. If the UI version is not the same, then the current default master page will be used instead.

If the master page cannot be found by name, then Metalogix Content Matrix will check to see if there is another master page that has the same name plus the appended UI version suffix that would represent the source. For example, if migrating from SharePoint 2013 to SharePoint 2016 and the master page is named "AccountMaster3," then Metalogix Content Matrix will look for a master page with the same "AccountMaster3" name. If that fails it will then look for a master page with the same name plus "_2013" appended to the end, like "AccountMaster3_2013." If this is found, then the same UI version check will be run that is used for the exact same master page name, and the same results will be given.

If no master page with the same name is found, either the direct same name, or the name with the UI version appended to the end, then the current default master page will be used instead.

NOTE: If the master page belongs to a UI version that is not supported by the target SharePoint instance, the master page will be skipped.

·Migrating between similar versions of SharePoint - For migrations that are run between the same basic UI version of SharePoint, such as SharePoint 2013 to SharePoint 2013 and SharePoint 2016 to SharePoint 2016, Metalogix Content Matrix will look for a master page with exactly the same name as the master page on the source. If one is found, then Metalogix Content Matrix will use that master page. If no master page with the same name is found, then the current default master page will be used instead.

How List Template Galleries Are Migrated

Navigation:  How Content Matrix Handles Various SharePoint Components >

How List Template Galleries Are Migrated

Metalogix Content Matrix lets you copy the List Template Gallery from a source SharePoint Site Collection to a target SharePoint Site Collection.

Connection icon

In order for the List Template gallery to be migrated, you must have an Object Model (OM) connection (through either a Local or Remote Metalogix Extensions Web Service (MEWS)) on both the source and target environments for SharePoint .

 

The List Template Gallery can be migrated as part of a Site Collection copy (when copy a Site Collection and pasting as a Site Collection), or it can be copied as a separate action. Any list templates that are copied from the source will overwrite any list templates on the target that have the same name. If the file names are different, then the list templates will be added to the existing List Template Gallery.

For example, if there are two templates on the target named "Template A" and "Template B", and these are migrated to the target where there are also two templates, which are named "Template B" and "Template C" then only "Template B" will be over written. In this case "Template A" will be copied to the target, and since there is no existing file with the same name it will be added without overwriting any other files. Since there was no file with the "Template C" name that was migrated to the target, the "Template C" file will also exist (as is) on the target. However, since both the source and the target have a file with the "Template B" name, the "Template B" file on the target will be overwritten by the one from the source. The end result is that three files will now exist on the target: Template A, Template B (which is a copy of the source version of the file), and Template C.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione