"Full Control" permission for Managed Metadata service application
"Full Access to Term Store" permission for Managed Metadata service application
Term Store Administrator
SharePoint Online
Term Store Administrator
Global Administrator
When there are multiple Managed Metadata service applications in the SharePoint environment, make sure that a Managed Metadata service connection has been set as the default term store. For instructions on how to do so, please click here.
Use the following connection types:
Source: Local Object Model (OM) or Metalogix Extensions Web Service (MEWS) connection for SharePoint On-Premises environment, Database (DB) connection when performing GUID mapping only Target: Local Object Model (OM) or Metalogix Extensions Web Service (MEWS) connection for SharePoint On-Premises environment, Client Side Object Model (CSOM) connection for Office 365
Select the correct migration level and action:
Server/Tenant Level
Copy Farm Managed Metadata > Paste Managed Metadata Term Stores (On-Premises to On-Premises/SPO)
Enable the options below depending on the migration scenario:
"Resolve managed metadata by name and hierarchy" should be enabled when the Managed Metadata has the same name and hierarchy on both the source and target environments so Content Matrix will use the existing value on the target.
"Copy referenced managed metadata" should be enabled together with the "Resolve managed metadata by name and hierarchy" option so Content Matrix will migrate values that do not exist on the target using new GUIDs.
"Map term stores for migration" should be used when there are multiple term stores in the environment so Content Matrix will use the correct term store during migration.
"Transform specified site columns to managed metadata columns" should be enabled to transform site columns (Choice, MultiChoice, Text, Lookup, LookupMulti, Number, DateTime, Currency, Boolean, Note, and User) to a Managed Metadata column. For additional information, please click here.
"Transform specified columns in lists to managed metadata columns" should be enabled to transform list columns (Choice, MultiChoice, Text, Lookup, LookupMulti, Number, DateTime, Currency, Boolean, Note, and User) to a Managed Metadata column. For additional information, please click here.
If the Managed Metadata is still not migrated to the target environment correctly, perform one of the following options:
Check if there is any Custom Content Type added to the List or Library being migrated, make sure the columns internal name match in source and target.
Set the "UseExistingTargetTerms" key in the %AppData%\Metalogix\Content Matrix Console - SharePoint Edition\ApplicationSettings.xml file to "True".
UseExistingTargetTerms
True
Map the GUIDs of source and target term/s explicitly. Please refer to the links below for more information:
To improve migration performance of content that includes a large number of terms, perform any of the following:
Use the Local Object Model (OM) or Metalogix Extensions Web Service (MEWS) connection to the source/target environments to migrate Managed Metadata using GUID mappings.
Migrate Managed Metadata first to the target environment, set the "UseExistingTargetTerms" key in the %AppData%\Metalogix\Content Matrix Console - SharePoint Edition\ApplicationSettings.xml file to "True", then migrate the rest of the content with all Managed Metadata options deselected except for "Map term stores for migration".
Change the value of the "MMDTermsBatchSize" key in the %ProgramData%\Metalogix\EnvironmentSettings.xml file. By default, it is set to a batch size of 50 terms.