Chat now with support
Chat mit Support

Content Matrix 9.10 - SharePoint Edition

Introduction Activating the License Key Selecting the SQL Database You Want to Connect to Content Matrix Console End User Interface Enabling Advanced Mode Multilingual Support Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components
Team Site to Modern Team Site Migration SharePoint Sites to Modern Communication Site Migration Promotion of First Level Subsites to Site Collections MySite Migration "Share With" Metadata and "Sharing Links" Access Permissions Migration Records Center to SharePoint Online Migration Using the Import Pipeline Master Page Migration List Template Gallery Migration Content Types Migration Document Version and Checked Out File Limitations Ghosted and Un-Ghosted Page Migration Document Set Migration Navigation Migration Classic Web Parts Migration Site Theme Preservation Site Feature Migration Managed Metadata Migration Users and Permissions Migration BCS/BDC Data Migration OneNote Notebooks Migration Customized Form Pages Migration InfoPath Forms Migration SharePoint Workflow Migration Nintex Workflows and Forms Migration Link Correction StoragePoint Content Migration
Initiating a Migration Configuring Copying Options Saving or Running a Migration Job Copying SharePoint Objects as a Separate Action 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
DB_Owner Permission Keyboard Shortcuts Activating the License Key Silently License Key Troubleshooting Errors Connecting to SharePoint 2019 or SharePoint Server Subscription Edition in a FIPS-Enabled Environment Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Migrating SharePoint On Premises Using Proxies, Load Balancing or Alternate Access Mappings Extensions Web Service Installation Files Migrating JavaScript Migrating Site Variations Migrating with SharePoint Document IDs Changing a Job Configuration for Multiple Files SharePoint Site Collection Creation Issue Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs When Migrating to SharePoint Online Retrying Failed Document Copies to SharePoint Online CSOM Connections Import Pipeline Batches Getting Stuck Migrating Content When the Source Custom List Template is Missing When Migrating to SharePoint Online HTTP Status Code 429 (“Too many requests”) or 503 (“Server Too Busy”) Message Returned How Do I Identify and Remove Containers and Queues from My Azure Private Storage Account? Error: 'The object is associated with property AssociatedMemberGroup.' Migration Error: 'ERROR, the batch will be resubmitted to the import pipeline' Item Count at Target is Increased When Migrating Using the Import Pipeline Custom Lists with Versioning Enabled Not Being Migrated When Using the Import Pipeline Supported Nintex Actions for SPO Migration Support for GCC High Tenants
About Us

How Content Matrix Handles Various SharePoint Components

Before configuring a migration, it is important to understand how Content Matrix migrates various SharePoint components so that you can plan appropriately.  These include:

Team Sites to Modern Team Sites

SharePoint Sites to Communication Sites

Promotion of First Level Subsites to Site Collections and Association of Promoted Site Collections as Hub Sites

MySites

"Share With" Metadata and "Sharing Links" Access Permissions

Records Centers (to SharePoint Online using the Import Pipeline)

Master Pages

List Template Galleries

Content Types

Document Versions and Checked Out Files

Ghosted and Unghosted pages

Document Sets

Navigation

Classic Web Parts

Site Themes

Site Features

Managed Metadata

Users and Permissions

BCS and BDC Data

OneNote Notebooks

Customized Form Pages

InfoPath Forms

SharePoint Workflows

Quest StoragePoint Content

Link Correction

Team Site to Modern Team Site Migration

Content Matrix supports the migration of:

·a classic team site to a SharePoint 2019 or SharePoint Online modern team site

AND

·a modern team site from a SharePoint 2019 source to a SharePoint 2019 or SharePoint Online target, using the STS#3 (modern team site without Microsoft 365 groups) template.

If you upgraded from a version earlier than 9.2:

Because of the complexities involved with connecting to Microsoft 365 groups when migrating to SharePoint Online, as of version 9.2 a separate option to Paste as a Modern Team Site is no longer available. Instead:

·Modern team sites will automatically be loaded into the Console as part of the hierarchy without connecting to Microsoft 365 groups.

·You will need to connect to the M365 groups after the migration is completed.

IMPORTANT:  If you have upgraded from a version of Content Matrix that is earlier than 9.2 and have existing jobs that include the Paste as Modern Team Site action (including PowerShell jobs), you will no longer be able to run them.

Team Site Target Template Options When Migrating a Classic Team Site

By default, when you configure a migration from a classic Team site to SharePoint Online or SharePoint 2019, the option Automatically upgrade Classic Team Sites (STS#0) to Modern Team Sites (STS#3), which is a modern team site with no Microsoft 365 groups, is enabled.

NOTE:  For migrations to SharePoint Online, Content Matrix does not support connections to tenant-level groups at the target.  You can, however, make these connections after completing the migration.

Site Options Upgrade to STS3

The table below describes how team site templates are applied to sites and subsites on the target, based on whether Automatically upgrade Classic Team Sites (STS#0) to Modern Team Sites (STS#3) is enabled.

If the Automatically Upgrade Classic Team Sites option is ...

And ...

Then ...

enabled

Team site (classic experience) (STS#0) is selected on the Configure Site Copying Options > Site Options tab.

the selected site collection/site and any child sites that use or are mapped to the Classic Team Site (STS#0) template will use the Modern Team Site without M365 Groups (STS#3) template on the target.

a non-team site template is selected on the Configure Site Copying Options > Site Options tab.

·the selected site collection/site will use the non-team site template on the target

AND

·any child sites that either use or are mapped to the Classic Team Site (STS#0) template will use the Modern Team Sites without M365 Groups (STS#3) template on the target

disabled

Team site (classic experience) (STS#0) is selected on the Configure Site Copying Options > Site Options tab.

both the selected site collection/site and any child sites that either use or are mapped to the Classic Team Site (STS#0) template will use the Classic Team Site template on the target.

the selected site collection/site uses a non-team site template

·the selected site collection/site will use the non-team site template on the target

AND

·any child sites that either use or are mapped to the Classic Team Site (STS#0) template will use the Classic Team Site template on the target.

Converting Classic Pages to Modern Pages After Migration

After migrating from a classic site to a modern site, you can use a solution provided by the PnP Community to convert classic pages to modern pages via the Content Matrix Console.  

SharePoint Sites to Modern Communication Site Migration

Content Matrix supports the migration of classic Publishing sites (that is, site collections that use the BLANKINTERNETCONTAINER#0 template) to modern Communication sites  However, there are limitations due to differences between classic and modern site designs. Refer to the Microsoft article Moving from publishing sites to communication sites for more information.

NOTE:  Content Matrix can also migrate SharePoint 2019 Communication sites to SharePoint 2019 or SharePoint Online Communication sites.  However, the following are not supported:

·Migration of the following objects:

§user comments

§workflows

§features, such as Publishing, that cannot be activated in SharePoint Online

·Translation to a different language on the target.

Migrating a Publishing Site as a Site Collection

Using the Paste Site Collection option, Content Matrix can migrate a Publishing site from a SharePoint 2013, 2016 source to a SharePoint 2019 or SharePoint Online Communication site collection.

When configuring your migration, you can select the Communication site template from the Site Collection Options tab, although it is not selected by default.  

NOTE:  The Communications site template is not available for unsupported source/target combinations.

If the site collection you are migrating  also has subsites, a dialog displays warning that Microsoft does not recommend having subsites under a Communications site.  See "Migrating as a Subsite" below for a list of sites that can be migrated as subsites.

Migrating a Publishing Site as a Subsite

When migrating a SharePoint site as a subsite to a SharePoint Communication site collection (using the Paste as Subsite, Paste All Subsites, or Paste All Site Content option), a dialog displays warning that Microsoft does not recommend having subsites under a Communications site.  However, Content Matrix will allow the migration of sites that use any of the following templates:

·Team site (no Microsoft 365 group)

·Team site (classic experience)

·Blog

·Project Site

·Records Center

·Document Center

·Basic Search Center

·Visio Process Repository

·SAP Workflow Site

Subsites using any other templates will be skipped.

Unsupported Objects

Because of differences between classic and modern site designs, even if applicable options are selected when Configuring a Migration, the following objects are not supported when migrating from a Publishing site to a Communications site and will be skipped:

Unsupported
Lists and Libraries

Unsupported
Features

Other Unsupported Objects

·Publishing Lists\Libraries:

§Content and Structure Reports

§Reusable Content

§Pages

§Images

·Hidden Lists\Libraries:

§DeviceChannels

§Cache Profiles

§Long Running Operation Status

§Notification List

§PersistedManagedNavigationListEA69B38CE5CE4F1199

§Quick Deploy Items

§Suggested Content Browser Locations (Published Links)

§Translation Packages

§Translation Status

§Variation Labels

§Badges

·Community Site Lists\Libraries:

§Site Pages

§Site Assets

§Discussion List

§Community members

§Categories

§Abuse Reports

·Site Collection Features:

§Project Web App Settings

§Review

§Cross Site Collection Publishing

§SharePoint server publishing infrastructure

·Site Features:

§Announcement Tiles

§Duet Enterprise reporting

§Duet Enterprise SAP Workflow

§Community Site feature

§The following Community Site-dependent hidden features:

oDiscussion list

oMembership list

oCategory list

oAbuse Reports list

§Site MailBox

§SharePoint Server Publishing

§Publishing Mobile (hidden feature)

·Pages:

§Classic Publishing pages

§Wiki pages

§Web Part pages

·Columns:

§All columns under the groups "Page Layout Columns" and "Publishing Columns"

·Web Parts:

§Classic web parts

§List Forms and List View web parts

·Content Types:

§Publishing content types
(under the groups "Page Layout Content Types" and "Publishing Content Types")

§Community content types

§Any custom content type whose parent is a Publishing or Community content type

§Video content type

·Workflows:

§Out-of-the-box workflows

§SharePoint Designer 2010 style workflows

·Navigation settings:  

§Top Link Bar

§Global Navigation structure

NOTE:  Quick Launch and the current navigation structure are migrated but will not be functional for any unsupported subsites, pages, and lists/libraries.

Disabled Configuration Options

When migrating from a Publishing site to a Communications Site, the following options are disabled on the Configure Site Collection Copying Options - Site Collection Options tab, as they are not supported:

·Copy Master Page Gallery

·Copy List Template Gallery

·Copy Audit Settings

Converting Classic Pages to Modern Pages After Migration

After migrating from a classic site to a modern site, you can use a solution provided by the PnP Community to convert classic pages to modern pages via the Content Matrix Console.  

Promotion of First Level Subsites to Site Collections

If you are migrating to SharePoint Online using the Paste as Site Collection option (or the PowerShell Copy-MLSharePointSiteCollection command) you have the option to promote first level subsites to site collections on the Site Collection Options tab. You can also configure promoted site collections as hub sites.

NOTES:  

·If a corresponding site collection does not exist on the target, a new site collection will be created. If a corresponding site collection already exists, the existing site collection will be updated.

·If the source subsite has its own subsites, those subsites will be migrated as subsites of the promoted site collections on the target.

Prerequisites

The option to promote subsites is enabled only:

·if you are migrating from SharePoint on premises to SharePoint Online using a Microsoft 365 tenant connection on the target

·the source site contains at least one subsite

·the Copy Child Sites recursively option is selected

·the target template is Team site (no Microsoft 365 group) (STS#3) or Communication site (SITEPAGEPUBLISHING#0)

Mapping of Source and Target Templates

When a subsite is promoted, it is migrated to the appropriate modern template on the target.

Source Template

Mapped Target Template

Publishing/ Wiki

Communication (SITEPAGEPUBLISHING#0)

All other templates

Team site (no Microsoft 365 group) (STS#3)

Limitations

Some objects in migrated subsites, such as Lookup columns referring to the parent site and workflow/workflow associations from parent site, may not be migrated properly for the promoted site collection.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen