MicrosoftMicrosoft
MicrosoftSure Jose Luis Serrano. For our environment, we did our best to freeze the content types in the on-premises content type hub and at migration duplicate them (meaning, rebuild them) in our SPO content type hub. We mapped the ones in SPO to the term sets in the SPO Term Store, which consisted of term sets that were migrated from on-prem. At that point, we tried not to many any changes to the on-premises content types and if there were changes they needed to also be made (via the SPO admin UI) online. This can be a lot of effort, so we focused on this work for the highest value content that was leveraging the managed metadata service. We tried to keep the number content types managed in the hub as small as possible, aligned just to key business needs. I'll be honest, this was a while ago, so we were using custom, internal build hybrid taxonomy tools (it was before Hybrid Taxonomy was available in the product) but I think the concepts remain the same even today since the CTH isn't part of the current tool either.