Converse agora com nosso suporte
Chat com o suporte

Content Matrix 9.8 - 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 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 batch will be resubmitted" Message Displays When Using 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

Required Permissions for Migrating MySites

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

Required Permissions for Migrating MySites to SharePoint On Premises

Migrating MySites to a SharePoint on premises target requires slightly higher permissions than other copy actions. The basic permissions needed to migrate MySites are as follows:

·Full Control permissions are required on the target Web Application. This is because when migrating MySites, the migrating user will not necessarily have access to the newly created MySite, and without access to the new MySite, you would be unable to migrate any other general content into it without getting permission errors. If this account has Full Control on the web application that the MySite is being created on, then it would still be able to migrate content into the new MySite because it will still have access (without making the migrating account a Site Collection Administrator on the MySite).

·Farm Administrator permissions are required on the target SharePoint server to which the MySites will be migrated when migrating to a target that is using the Local Object Model (OM) connection.

EXCEPTION:  If the target connection is using the Remote OM connection through the use of the Metalogix Extensions Web Service, then the Farm Administrator permission is not needed.

·Manage Profile permissions are required on the User Profile application (in Share Services). This option is mainly required when migrating User Profiles, and to help create and manage Managed Metadata for the user profiles.

These basic permissions allow for the creation and migration of MySites (personal sites) on the target, use of personal features, management of user profiles, and management of permissions (these can all be accessed through the Shared Service Applications in Central Administration).

Migrating User Profiles with MySites

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

Migrating User Profiles with MySites

User Profiles can be migrated with the MySites, then later be converted into audiences. When migrating MySites, any custom User Profile properties will only be migrated if the following conditions are met:

§The User Profile property from the source has already been created on the target before migration.

§The target side User Profile property has the same property name as it did on the source.

§The target side User Profile property has the same property type as it did on the source.

When migrating User Profiles to an Office 365 Tenant target, the following limitations apply:

§Any Quick Links on the source profile will not be migrated.

§Any Privacy settings in the profile settings will not be migrated.

§If a profile picture is set on the source profile, it will not be migrated.

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

Navigation:  How Content Matrix Handles Various SharePoint Components >

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

"Share With" Metadata

When a  SharePoint 2016 or 2019 Team Site or MySite is migrated to SharePoint Online and the Import Pipeline is used, 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 connections.

Current Limitations

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

·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.

"Sharing Links" Access Permissions

Sharing Links are not migrated to the target.  However, permissions granted to files and folders via these links can be converted to direct permissions on the target if the following criteria are met:

·the source is SharePoint 2019

·the "People in your organization" option was used to share links

·on the Permissions Options tab, the option Convert Sharing Links permissions to direct permissions is checked.

NOTE:  This option is not available for SharePoint 2016 or earler.

Records Center to SharePoint Online Migration Using the Import Pipeline

Navigation:  How Content Matrix Handles Various SharePoint Components >

Records Center to SharePoint Online Migration 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.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação