Chat now with support
Chat with Support

Metalogix Content Matrix 8.8 - SharePoint Edition User Guide

Introduction Entering the License Key Content Matrix Console End User Interface Enabling Advanced Mode Connecting to SharePoint Preparing for a Migration How Content Matrix Handles Various SharePoint Components Initiating a Migration Configuring Copying Options Saving or Running a Migration Action Copying SharePoint Objects as a Separate Action Self-Service Migration Incremental Migration Log Files Using PowerShell with Content Matrix
Configuring PowerShell for Use with Content Matrix
Registering Metalogix Command DLL Files 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 and Self-Service Migration Frequently Asked Questions
DB_Owner Permission Migrating with the Fabulous 40 Templates Item Count Discrepancies Keyboard Shortcuts License Key Troubleshooting Determining the Status of a Migration Running in the Background MySite and User Profile Migration Issues Optimal Setup for Best Performance Using Proxies, Load Balancing or Alternate Access Mappings Troubleshooting the Extensions Web Service Installing the Extensions Web Service on Specific Systems Extensions Web Service Installation Files Using Older Versions of the Extensions Web Service Preserving IDs when Migrating a Custom List as a Folder Migrating JavaScript Migrating Site Variations Migrating with SharePoint 2010/2013/2016 Document IDs Changing a Job Configuration for Multiple Files SharePoint 2003 Version Migration Limitations SharePoint 2013 and 2016 Site Collection Creation Issue Job List Database fails to Load After Upgrade Customized Wiki Page Web Part Zones Not Being Migrated Preserving SharePoint List Item IDs with a CSOM Connection Type Retrying Failed Document Copies to O365 CSOM Connections Migrating Content When the Source Custom List Template is Missing Are SharePoint Online Migrations Throttled? What to Expect when Migrating with StoragePoint on the Target Migration Error Message 'There was an Error Reading from the Pipe: The Pipe has been Ended (109, 0xd6)' How do I Remove Items from My Azure Blob Storage Account? Azure Batches Getting Stuck Supported Nintex Actions for SPO Migration "Insufficient Credentials" Message Connecting to Modern Team Site Using Web Browser Authentication Error Making a Browser-Based Connection with PowerShell Console Open
About Us

Migrating MySites

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 target server with SharePoint 2007 or later (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 Office 365 Tenant environment.

·A source Office 365 Tenant environment to a target Office 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 or Extensions Web Service connections for on premise installations of SharePoint. For Office 365 target environments, the Office 365 Tenant connection type must be used.  This allows users to connect at a Site Collection level to the Office 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 to a SharePoint 2013 or 2016 target, 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, Metalogix 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 for a SharePoint 2013 or 2016 target 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 for more details on this connection types. For more information on this specific issue, please see SharePoint 2013 or 2016 Site Collection Creation Issue.

The same issue, for requiring elevated permissions, can be encountered in SharePoint 2010 environments using Claims authentication.

Note that in order to view MySites when migrating to an Office 365 Tenant environment, the Include Office 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 O365 Tenant.

Migrating MySites into a Target that Uses OneDrive

When migrating MySites into a target SharePoint environment that uses OneDrive, Metalogix 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/2010 will not be migrated to SharePoint 2013. or 2016.

Required Permissions for Migrating MySites

Migrating MySites 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 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

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.

Related Documents