How to migrate taxonomies from Employee Center between instancesIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } How to migrate the taxonomy of the employee center into another instance? Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Option 1 (Most common): XML export / import:1. In source instance (DEV): Export taxonomy-related records via XML Export from the list view.This includes all related m2m tables such as: m2m_connected_content,sn_ex_sp_external_link, child topics, featured_content, etc. 2. Import XML into target instance (TEST/PROD). Validate relationships (topics → connected content). Option 2: Update sets (only with heavy manual cleanup)Update sets do not reliably capture taxonomy data. If you try this anyway: Taxonomy records are created in Global scopeSome tables never auto‑add to update setsYou must manually add records (especially M2M and external links) Option 3: Clone If your goal is to have the same data over both instances, a full clone is the only guaranteed way. Additional information:For Option 2: Update sets Migrating records from the following tables to another instance, you will need to more careful, as these records doesn't get captured in update sets properly. We suggest whenever you are changing/creating new configurations for these tables you can follow below checklist to make sure all the updates are captured properly. 1. Usually records always gets created in global application. So make sure you are capturing them in correct application update sets. 2. While moving quick links make sure you are capturing records for external link field as well if there are any. 3. While moving m2m_connected_content records make sure you have all the topics present in target instance if not capture them as well.- Please note that you can look at the following m2m_connected_content table to grab the necessary records. 4. sn_ex_sp_external_link does not get captured automatically, You will need to add them in update set manually. Summary, you need to check for each records that is captured along with their related records.For Option 1 & 2: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, 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. 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.