- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Community,
I need to deactivate an existing group in ServiceNow and make sure all future tickets get assigned to a new group instead. The challenge is:
There are a large number of old tasks assigned to the current group.
The group is referenced in multiple business rules, client scripts, and assignment logic.
It also appears in hundreds of report filters.
I want to ensure that all future work routes to the new group, while also handling existing references.
👉 Is there any short or OOTB method in ServiceNow to replace all references of a group with a new one?
👉 If not, what would be the best process to safely migrate (e.g., handling open tasks, scripts, and reports) without breaking historical data?
Any guidance, best practices, or scripts would be really helpful.
Thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @AshutoshB,
it could be done by Update job:
- select a table (e.g. Incident)
- set conditions (e.g. state is not closed or cancelled to avoid updating old records)
- click preview to see what and how many records would be touched
- then select the new value in the assignment group
I recommend you uncheck the two fields as per shown in the below part - as keeping it true might trigger notifications upon assignment etc, and the other would mark the updated on and updated by values so it could lose some important data.
This example is for Incident but you can do it on Task table for more records, or do one update job for incidents, one for RITMs, one for Problems etc...
This update jobs have rollback record if something goes wrong 🙂 then you can select when to execute it.
Let me know if this helped you or what would it take to consider this as solution?
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @AshutoshB,
it could be done by Update job:
- select a table (e.g. Incident)
- set conditions (e.g. state is not closed or cancelled to avoid updating old records)
- click preview to see what and how many records would be touched
- then select the new value in the assignment group
I recommend you uncheck the two fields as per shown in the below part - as keeping it true might trigger notifications upon assignment etc, and the other would mark the updated on and updated by values so it could lose some important data.
This example is for Incident but you can do it on Task table for more records, or do one update job for incidents, one for RITMs, one for Problems etc...
This update jobs have rollback record if something goes wrong 🙂 then you can select when to execute it.
Let me know if this helped you or what would it take to consider this as solution?
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
HI @AshutoshB,
have you had chance reading my reply? It'd be cool to hear some feedback from you.
Let me know what would it take to solve this
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey @GlideFather
Thanks for the detailed response!
That’s really helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Awesome! Thanks for your confirmation.
I'm glad you like this, it's very good method how to update data. Only negative part is that this means that the data will be updated with the same values (e.g. re-assigned to one assignment group), not much space for dynamic updates 🙂
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */