Metalogix Content Matrix can copy managed metadata values for items and copy and map term stores from a SharePoint 2010 or later (including Office 365) environment into a target SharePoint environment (including Office 365 when a Tenant connection type is used).
Managed Metadata term stores are created through SharePoint Central Administration, and consist of the following managed metadata: Groups, Term Sets, and Terms. Term stores cannot be created by Metalogix Content Matrix, which means that the target side term store must be manually created before any content is migrated. After a term store is created on the target, all the managed metadata and term hierarchy structure from the source can be migrated.
You can migrate Managed Metadata using any of the following connection types:
·Object Model (OM) Connection - This is either a Local or Remote (Extensions Web Service) connection type and can be used for SharePoint on premises source/target environments.
NOTE: You can also use either of these connections to migrate managed metatada using GUID Mappings, which may significantly improve performance over choosing to Resolve by Name and Hierarchy, which requires Metalogix Content Matrix to crawl through the entire term store.
·Office 365 Tenant Connection - This is a server level connection to an Office 365 Tenant environment. If using an Office 365 Tenant environment as a source, this is the only connection that can be used. If using any other environment as a source, this connection type can only be used as a target.
·Client Side Object Model (CSOM) connections This connection type can only be used by Office 365 environments, and can be used for either a source or target connection.
·Database Connections - This connection is only supported as a source connection for the migration of metadata using GUID Mapping . There are prerequisite actions to be performed before using this connection type.
The ability to migrate managed metadata using GUID Mapping is currently supported for Local Object Model, Metalogix Extensions Web Service (MEWS), and Database source connections.
To be able to migrate managed metadata using GUID mapping , it is recommended that you perform the following steps. While Metalogix Content Matrix supports mapping to existing managed metadata at the target, this method will ensure the best results:
1.Using an Object Model (OM) or CSOM/MEWS connection type on the source, migrate the global term store as follows:
a)Select the top-level source node.
b)Right-click choose Copy Farm Managed Metadata.
c)Select the top-level target node.
d)Right-click and choose Paste Managed Metadata Term Stores.
2.Individually migrate each site collection-level term store to be migrated as follows:
a)Select the source site collection.
b)Right-click and choose Copy Site.
c)Select the target site collection.
d)Right-click and choose Paste Site Object > Managed Metadata Local Sites Collection Group.
e)In the Managed Metadata Options tab, ensure that:
§Resolve managed metadata by name and hierarchy is deselected
§Map term stores for migration is selected.
NOTE: Before configuring Term Store and Managed Metadata options, it is strongly recommended that you review the prerequisites for transforming columns into Managed Metadata.
Unless otherwise noted, if you are using Simplified mode and an option is not available for selection, the default value that displays in Advanced mode will automatically be applied. If you want to change the value of the option, click [Advanced Mode] and switch to the Advanced mode interface.
To configure Managed Metadata options:
1.If you are using Advanced mode and want Metalogix Content Matrix to check both the source and target environments to find any existing Managed Metadata term structure and then migrate a copy of the source term structure over to the target, make sure the Resolve managed metadata by name and hierarchy box is checked.
NOTE: If there are terms that do not exist, they will be added (using the same hierarchy structure with new GUIDs), and if there are terms that already exist the terms on the target will be used. If you want terms on the target to be overwritten with those on the source, make sure Map term stores for migration is selected, as described in the next step.
2.If you want to map the term store on the source to a term store on the target:
NOTE: Migrating managed metadata at the site level will only copy the global managed metadata, and will not copy any site collection term sets. Site collection term sets are only copied when the Copy referenced managed metadata and Map term stores for migration options are enabled as part of a SharePoint site or list level migration.
a)Select the appropriate option based on the mode you are using:
§If you are using Simplified mode, click the [...] button to the right of the Map Managed Metadata option.
§If you are using Advanced mode, check the Map term stores for migration box, then click the [...] button.
The Map Term Store dialog displays with a list of all term stores that currently exist on the target.
§This option is primary used in the following situations:
§When migrating the entire term store (the global term store).
§When migrating term stores by their ID value
§When migrating at the site collection level that uses more than one Term Store, to ensure that the correct Term Store is used.
§This option is required when migrating to an Office 365 Tenant target environment. In such a migration, this option is enabled by default and cannot be deselected.
§If the Resolve managed metadata by name and hierarchy option is selected, this option would only be selected if you want to map and overwrite the values the target.
b)Right click the Source Term Store you want to map, and select the Target Term Store you want to Map to.
NOTE: If the Target Term Store is set to <Exclude> (the default value), the term store will not be mapped. Remember that a 1:1 Relationship must exist between Source/Target term store mappings
3.When you are finished mapping term stores, click [OK].
4.If you want to migrate Managed Metadata columns for items and lists, check the Copy referenced managed metadata box.
NOTE: This option will not actually create Term Stores. It is recommended that this option be used in conjunction with the Resolve managed metadata by name and hierarchy and/or Map term stores for migration.
5.If you are using Advanced mode and want SharePoint site columns (fields) to be transformed into Managed Metadata fields on the target:
a)Check the Transform specified site columns to managed metadata columns box.
b)Click the [ ] button.
c)Complete the Configure Transformations for a Site Column dialog as described in the topic Transforming a Site or List Column into a Managed Metadata Columns.
6.If you are using Advanced mode and want SharePoint list columns (fields) to be transformed into Managed Metadata fields on the target:
a)Check the Transform specified list columns to managed metadata columns box.
b)Click the [ ] button.
c)Complete the Configure Transformations for a List Column dialog as described in the topic Transforming a Site or List Column into a Managed Metadata Columns.
NOTE: By default, Metalogix Content Matrix migrates terms in batches of 50. You can, however, change this value (for example, decrease it if you are experiencing timeout errors during the migration operation or increase it if you are migrating an excessively large number of terms or keywords. However, It is recommended that you not change the batch size unless absolutely necessary. See Changing the Managed Metadata Migration Batch Size.
When a Team Site or MySite is migrated to SharePoint Online using the Import Pipeline, documents that have been shared by a user will be visible in the SharePoint Shared by Me tab of that user, as well as on the Shared With Me tab of the user(s) with whom the document has been shared.
This functionality has been verified for a SharePoint 2016 and 2019 source:
·to migrate MySites to MySites (OneDrives) using an Object Model (OM) source connection, either local or remote (through the Metalogix Extensions Web Service (MEWS)).
·to migrate Team Sites to Team Sites using one of the above source connection types, as well as Database and CSOM connections.
Because of functionality not currently supported by Microsoft, the following limitations apply:
·Folders shared with users are not visible in Shared With Me tab after migration.
·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.
·Because the metadata for the Date Shared and Shared By columns on the Shared With Me tab must be migrated using CSOM (even if the Use Import Pipeline box is checked), these columns will be blank after migration.
·The Shared Time shows as the migrated time rather than the actual document shared time.