Exporting Tag-based service maps from lower environment to higher environment

[DebenduKumB]

Hi Community,

I have created tag-based service maps for business applications in a DEV environment and I’m trying to migrate them to PROD.

I captured the changes using both:

• Update Sets, and

• XML export/import

However, after importing into PROD, I’m noticing that the Tag Categories and Tag Values records are missing from the Tag-Based Service Families record. As a result, the service maps are incomplete and not working as expected.

Questions:

1. Why are the tag categories and tag values not being included when moving tag-based service maps via update sets or XML?

2. Is this expected behavior due to how tag data is stored or referenced in ServiceNow?

3. What is the recommended / best practice approach to move tag-based service maps from lower environments (DEV) to higher environments (PROD) while ensuring all tag data is preserved?

Any guidance or real-world experience would be greatly appreciated.

Thanks in advance!

[SK Chand Basha]

Hi @DebenduKumB 

This should work if you move the CI Tag Categories and tag-based Service Families using XML and if the service family not linked to category then won't work ,and verify that the CI Tag Values data correctly with the category.
After that, click on Manually Update Candidates.

[ganeshpa]

Ideally tag should be getting discovered by discovery on each instance and based on tag value you should create tag category and not move them.

[Pratiksha]

The maps need to be created in production. You should set up the tag categories and handle the remaining tasks. Similarly, even when doing top down, you only need to move the pattern extensions.

Regards, 

Pratiksha