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 Microsoft 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
"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.
|
|
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
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.
|
|
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.
Master Page Migration
The Master Pages Gallery is basically a Document Library at the root of a site.
Content Matrix can work with Master Pages at two levels:
·At the Site Collection level, where it can copy master pages and page layouts.
·At the Site level, where it can preserve the master page association.
When a SharePoint site is migrated, Content Matrix will run a check to see if a master page with the same name as the source site's master page exists. There are then two main scenarios:
·Migrating from an older version of SharePoint to a newer version of SharePoint - Because master pages are quite different between different versions of SharePoint, when master pages are migrated from an older version of SharePoint to a newer version, a suffix will be appended to the end of the master page name based on the source UI version. For example, if you are migrating from MOSS 2007 to a later version, the master pages will have "_2007" appended to the end of the master page name. If migrating from SharePoint 2010 to a later version, the suffix would be "_2010" instead.
When a SharePoint site is migrated, Content Matrix will look for the source master page by name. If the master page name is found, Content Matrix will then do another check to ensure that the correct UI version is being used on the target site collection. If this UI version also matches, then the master page will be used for the migrating site. If the UI version is not the same, then the current default master page will be used instead.
If the master page cannot be found by name, then Content Matrix will check to see if there is another master page that has the same name plus the appended UI version suffix that would represent the source. For example, if migrating from SharePoint 2013 to SharePoint 2019 and the master page is named "AccountMaster3," then Content Matrix will look for a master page with the same "AccountMaster3" name. If that fails it will then look for a master page with the same name plus "_2013" appended to the end, like "AccountMaster3_2013." If this is found, then the same UI version check will be run that is used for the exact same master page name, and the same results will be given.
If no master page with the same name is found, either the direct same name, or the name with the UI version appended to the end, then the current default master page will be used instead.
NOTE: If the master page belongs to a UI version that is not supported by the target SharePoint instance, the master page will be skipped.
·Migrating between similar versions of SharePoint - For migrations that are run between the same basic UI version of SharePoint, such as SharePoint 2016 to SharePoint 2019 and SharePoint 2019 to SharePoint 2019, Content Matrix will look for a master page with exactly the same name as the master page on the source. If one is found, then Content Matrix will use that master page. If no master page with the same name is found, then the current default master page will be used instead.