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

Promotion of First Level Subsites to Site Collections

Navigation:  How Content Matrix Handles Various SharePoint Components >

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.

Association of Promoted Site Collections to a Hub Site

Navigation:  How Content Matrix Handles Various SharePoint Components > Promotion of First Level Subsites to Site Collections >

Association of Promoted Site Collections to a Hub Site

If you are migrating to SharePoint Online using the Paste as Site Collection option and have chosen to promote first level subsites to site collections, you also have to option to either:

·associate the promoted site collections on the target to an existing hub site

OR

·register a new hub site for the promoted site collections.

MySite Migration

The following are the supported source/target combinations for migrating MySites:

·Any source server with SharePoint 2007 or later (using the Web App or Farm connection types) to any supported target server (using the Web App or Farm connection types).

·Any source server with SharePoint 2007 or later (using the Web App or Farm connection types) to an Microsoft 365 Tenant environment.

Advanced Mode Icon  This option is only available when Advanced Mode is enabled.

 

Connection icon

When migrating MySites, the target side connection must be a Web App or Farm connection type, using the Local Object Model or Metalogix Extensions Web Service (MEWS) connections for on premises installations of SharePoint. For Microsoft 365 target environments, the Microsoft 365 Tenant connection type must be used.  This allows users to connect at a Site Collection level to the Microsoft 365 environment so they can run Site Collection migrations.

It is recommended that the Web App or Farm connection types be used on the source side as well. Other connection types can be used on the source, such as the Database connection. However, this will have some limitations. If these other connection types are used on the source, MySites can still be migrated to the target, but they will be migrated as Site Collections (not using the MySite template), and as a result, will not include some of the User Profile data and other data that the normal MySite migration will preserve.

When migrating SharePoint MySites, a Local OM or a Remote OM connection can be used. However, due to some User authentication changes that have been made beginning in SharePoint 2013 that inadvertently restrict the creation of Site Collections (MySites are a type of Site Collection), using the SharePoint OM remotely, Content Matrix needs to use a set of elevated permissions to create Site Collections. In order for these elevated permissions to be used, the migrating user account must explicitly (by name) have "Full Control" permissions on the Web Application that the Site Collection is being created on. A preliminary check will be made before elevation occurs to ensure the migrating user has enough permissions initially to be able to use the elevated Site Collection creation. Creating Site Collections with the Local OM connection type does not have this same restriction, but the same permissions are recommended in case elevated permissions are needed. Please see Connecting to SharePoint Online for more details on this connection types. For more information on this specific issue, please see SharePoint Site Collection Creation Issue.

Note that in order to view MySites when migrating to an Microsoft 365 Tenant environment, the Include Microsoft 365 tenant my site host connection check box must be enabled when the connection is created. The MySites are then displayed under their own top-level root node. For more information, please see Connecting to SharePoint Online.

Migrating MySites to a Target that Uses OneDrive

Navigation:  How Content Matrix Handles Various SharePoint Components > MySite Migration >

Migrating MySites to a Target that Uses OneDrive

When migrating MySites to a target SharePoint environment that uses OneDrive, Content Matrix will use a slightly different method to migrate some of the content. Any documents on the source that are in the MySite Shared Documents or Personal Documents library will be migrated into a Shared with Everyone folder in OneDrive. This is done instead of migrating the documents into Document Libraries of the same name. As a result, this can cause some navigation copy issues because the Shared and Personal document libraries will not exist on the target, and because they do not exist, they cannot be added to the navigation.

Additionally, web parts that exist on landing pages in SharePoint 2007 or 2010 will not be migrated.

See also "Share With" Metadata Migration to SharePoint OnlineUsing the Import Pipeline.

IMPORTANT:  If you are migrating to OneDrive on a SharePoint Online target, Owners, Members, and Visitors groups must be created on the target. If these groups are missing, an error will occur. See Error: 'The object is associated with property AssociatedMemberGroup.' in the Frequently Asked Questions section.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação