Migration from 2013 to 2019 for farm with content type hub

Hello,

We are using Content Matrix to migrate from an existing SP 2013 farm to a new SP 2019 farm.  Our 2013 farm has a content type hub set up and configured.  We exported our Managed Metadata term sets from the 2013 env and then imported into the 2019 farm, maintaining the term GUIDs.  Then we  migrated the content type hub from the source to the target farm and verified the connection with the Managed Metadata service application.  We were able to create a new site  in the target environment and then publish some content types to it --  they showed up under Subscribed Content Types in the newly created site -- so we know that the hub is working and publishing.

We then migrated an existing site from the source farm to the target farm.  However, when content type publishing runs, in the migrated site we now see errors such as "Content  type name '<someTypeName>' conflict" followed by a correlation ID.  The error appears to happen because the various content type already exist in the target farm.   

In addition, we have found that, while existing Managed Metadata values are retained during migration, the actual managed metadata properties are greyed our (i.e. cannot be edited).  This appears to be because as the site level the MMD columns have lost their term set mapping -- it exists on the content type hub, but not at the local sites (assuming that this is because when the site is migrated the content types and  columns become site-level entities and  are no longer connected to the content type hub definitions (?).

Looking for guidance on how to properly migrate sites in a scenario such as the above where the content type hub and subscriber sites all need to be migrated and then type updates need to be published again at some point.  Is this not possible using Content Matrix?

Thanks

Parents
  • Update:

    On further investigation we discovered that in order to accommodate the above scenario, the Content Matrix job used to migrate the sites should be configured to "NOT COPY" content types as part of the migration process.  Using this configuration results in the migrated sited getting its required content types from the content type hub.  COPYing content types results in the type getting copied and deployed as local content types, thereby breaking the ability to publish them to the site from the hub.

    In addition, this also appears to resolve the issue with the greyed out managed metadata property fields.

    Hope this helps someone else that is new to Content Matrix.

Reply
  • Update:

    On further investigation we discovered that in order to accommodate the above scenario, the Content Matrix job used to migrate the sites should be configured to "NOT COPY" content types as part of the migration process.  Using this configuration results in the migrated sited getting its required content types from the content type hub.  COPYing content types results in the type getting copied and deployed as local content types, thereby breaking the ability to publish them to the site from the hub.

    In addition, this also appears to resolve the issue with the greyed out managed metadata property fields.

    Hope this helps someone else that is new to Content Matrix.

Children
No Data