Need help with Update Set migration

[Juan Pablo]

Hi Team,

I’m trying to understand the best approach for migrating an Update Set between ServiceNow instances and wanted to get some guidance from the community.

My scenario is fairly simple:

• Development instance → Test instance

• Standard Update Set migration process

I know about committing retrieved Update Sets, but I wanted to ask:

• What is the recommended/best practice process you usually follow?

• Do you prefer exporting/importing XMLs manually or using remote update sets?

• Are there any common issues or pitfalls I should watch out for before committing?

• Any recommendations regarding preview problems or collision handling?

I have worked with Update Sets before, but I’d like to better understand the approach more experienced teams use in real projects.

Thanks in advance!
Regards,
Juan

[Ana39 · Accepted solution]

Best practice is usually:

• Use Remote Update Sets between Dev → Test → Prod
• Avoid manual XML unless:
  • instances are disconnected
  • emergency recovery
  • moving single records

Typical flow:

1. Complete Update Set in Dev
2. Retrieve from Test
3. Preview first
4. Resolve preview problems/collisions
5. Commit
6. Smoke test immediately

Biggest things to watch:

• Missing dependencies
• Changes made directly in Test/Prod
• Skipped records during preview
• Dictionary/UI Policy/ACL collisions
• Update Sets capturing unintended changes

Good habits:

• Keep Update Sets small and focused
• Never mix unrelated stories/fixes
• Use naming conventions
• Back out plans for critical deployments

And always preview before commit 😅
Preview errors are ServiceNow’s way of saying:

“You sure about this, campeón?” ☠️