Converse agora com nosso suporte
Chat com o suporte

Content Matrix 9.9 - 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 2013 and Later 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

Classic Web Parts Migration

Navigation:  How Content Matrix Handles Various SharePoint Components >

Classic Web Parts Migration

Content Matrix can migrate web parts for:

·landing pages (default.aspx pages)

·web part pages

·publishing content pages, and

·list view pages.

Web parts can be copied as part of a normal migration copy or as a separate action.  

NOTES:  

·Currently, If you are using Microsoft 365 OAuth with MFA Authentication, classic web parts can be migrated only if you are using the Import Pipeline.

·Modern web parts are copied as part of page metadata.

Essentially, Content Matrix reads the XML information of the web parts, processes the data, and moves it over to the target side, where the XML is then written out on the target location. Content Matrix will automatically perform link correction on the data within the web part (the data for the settings), as a part of the migration.

In order for any custom or third party web parts to be properly migrated, these web parts must be manually installed or created on the target server before migration. Content Matrix does not migrate the actual code of the web part, it only migrates the data within the web part. In order for an actual migration, the desired web part must first exist on the target SharePoint instance, otherwise the migration will fail.

 

Content Matrix can preserve web part views, however, there are a few known issues with this. In the case of list view web parts, you need to make sure that the list being referenced has already been migrated to the target to ensure that the web part, and it's view, will migrate properly. If the list being referenced in the web part is within the scope of the migration, then Content Matrix will make sure the list has been copied first, and will then copy web parts.

There is an additional web part view limitation when using the CSOM or Tenant connection adapter on the target, where Content Matrix is unable to set the type of a web part view. The most common manifestation of this is to have a web part lose its calendar appearance during migration. However, the other properties of that view will still be preserved. The resulting outcome will be that the content within the web part will be correct, but it will not look the same as the source because the view type is different. This can be corrected by manually, after migration, by changing the web part view to match the same web part view on the source.

NOTE:  In some cases the web part view type may migrate correctly. This can only occur if the web part is using the same view type that it was using when it was first created. However, this behavior is not reliable.

There is also a web part limitation on migrating web part connections. Web part connections are connections that exist between web parts (one web part pointing to another web part, etc.). Content Matrix is only able to migrate these web part connections if there is an OM connection type (through the use of the Local or Metalogix Extensions Web Service connections) on both the source and target SharePoint environments. Other connection types are unable to access this setting, meaning that if any other connection type is used on either the source or target, the web part connection setting cannot be preserved. This also means that this setting cannot be preserved when migrating to M365 environments.

Using the Import Pipeline to Migrate Classic Web Parts

Navigation:  How Content Matrix Handles Various SharePoint Components > Classic Web Parts Migration >

Using the Import Pipeline to Migrate Classic Web Parts

You can use the Import Pipeline to migrate the classic web parts identified in the following table.

NOTE:  Classic web parts not supported by the Import Pipeline are migrated using CSOM.  However, if Web Part pages or Wiki pages contain non-supported web parts, these web parts will not be migrated.

Category

Web Part Name

Blog

Blog Archive

Blog notification

Blog tools

Community

Join

Tools (community admin)

About this community

My membership

Whats happening

Content Rollup

Project Summary

Relevant Documents

Site Aggregator

Sites in category

Table of contents

Timeline

XML viewer

Content By Query

RSS Viewer

Summary Link(s)

List

Document library

List View

Media and Content

Page Viewer

Picture Library SlideShow

Content Editor

Getting Started

Image Viewer

Script Editor

SilverLight web part

Social Collaboration

Announcement

Analytics Hash Tag

Contact Details

Micro Feed

Note Board

Organization Browser

Site Feed

Site Users

User Tasks

XSLT

XSlt List View

NOTES:

·The same limitations with web part views and connections that apply to CSOM connections also apply when using the Import Pipeline.

·Some web parts require 'Allow Custom Script' setting enabled for the target tenant.  If this is not set at least 24 hours before migration, these web parts will not be migrated.  Refer to the Microsoft article Allow or prevent custom script for details on enabling this feature.

·Closed web parts on the source will be migrated as closed on the target.

Site Theme Preservation

Navigation:  How Content Matrix Handles Various SharePoint Components >

Site Theme Preservation

 

Connection icon

Preserving themes for a site requires Content Matrix to use an Object Model (OM) connection, either local or remote (using the Metalogix  Extensions Web Service (MEWS)) on the target side.

When migrating to/from SharePoint 2013 or later (including SharePoint Online), Content Matrix will migrate some additional required components when preserving themes. In these versions there is a hidden list called "Composed Looks" that contains some of the Theme information, and this list also references the MasterPage Gallery for additional information. Content Matrix will also migrate the corresponding items from the "Composed Looks" and MasterPage Gallery. This will be done for each theme that is copied, so if only the current theme is copied, only the related item from the "Composed Looks" list and the related MasterPage Gallery item will be copied as well. If all themes are copied, then all items in the "Composed Looks" list and MasterPage Gallery will be copied.

Site Feature Migration

Navigation:  How Content Matrix Handles Various SharePoint Components >

Site Feature Migration

Content Matrix can copy over site features and activate them as a part of a site level migration. Content Matrix does not actually copy over the feature itself, it only adds the feature to the target site and activates it.

In order for the feature to be added to the target site it must first be manually installed and available on the target server. If the features from the source do not exist on the target, the migration of features will fail, but the remaining content will continue to copy over.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação