How to move the Connected Content records from one instance to another instanceDescriptionThis article details what is connected content records, their behavior with UpdateSet, and how to migrate/move these connected content records from Source to Target instance. What is a Connected content record: When you associate a catalog item or knowledge article with a taxonomy topic, the system will update the taxonomy_topic field with that topic name in those catalog items or knowledge articles.Also, it will make an entry in m2m_connected_content which will hold the association between the catalog item or knowledge article with the taxonomy topic.When the same catalog item or knowledge article is associated with more than one taxonomy topic, the system will create new entries in m2m_connected_content for those associations.The taxonomy_topic field will reflect only the topic which was associated first. Connected content records and UpdateSets: Connected content records(m2m_connected_content) are data records and are not captured in an Update set.This is because m2m_connected_content has both catalog items and knowledge associations. Catalog item is sys_metadata item whereas knowledge is a data item, so m2m_connected_connected content is a data item as it has reference to a data item.So, m2m_connected_content needs to be moved as an XML by exporting from the source instance and then importing it back into Target. Migrate/move Connected Content records(m2m_connected_content) from the source to the destination instance: Before you start development on your source instance, make sure to sync the source instance from the target instance via clone, then do taxonomy topic association in the source instance, then capture these associations from the source to the target instance via exporting/importing "m2m_connected_content" records.Then run the OOB fix script "Set primary topics for Employee taxonomy" (/sys_script_fix.do?sys_id=d503bf1ec7213010fedf0bcbe2c260f1).This fix script is provided OOB, it refers to an OOB script include called "EmployeeTaxonomyUtil" and fetches taxonomy from that script include and runs for it. If you want to run for different taxonomy, you just need to update the script include with that taxonomy sys_id.This fix script will read through the m2m_connected_content records and accordingly set the taxonomy_topic field on the catalog item or knowledge article in the target instance accordingly.