Best practice to migrate existing monitor CIs between CMDB classes

[Isabelle Bury]

Hi everyone,

I’m looking for advice on the recommended best practice to migrate existing CIs between CMDB classes in ServiceNow.

Context:

• We currently have ~3000 monitor CIs stored in cmdb_ci_peripheral.

• According to ServiceNow best practices, monitors should be in cmdb_ci_hardware_display.

• These CIs are already:

  • linked to assets (with internal asset tags),

  • linked to other CIs (e.g. computers),

  • and actively used in the CMDB.

• There is no active integration running yet (we are preparing the CMDB first).

Question:
What is the recommended and supported approach to migrate these monitor CIs to the correct CMDB class while preserving CMDB integrity?

More specifically:

• Is the best practice to recreate the CIs in the target class via a scripted migration and retire the old ones?

• Is using ServiceNow reclassification (changing the Class field) considered safe and supported at this scale?

• Are there any official guidelines or pitfalls to be aware of regarding:

  • CI relationships,

  • CI ↔ Asset links,

  • CMDB Health and Identification/Reconciliation?

The goal is to end up with a clean, best-practice-aligned CMDB and avoid structural issues later.

Thanks in advance for your feedback and experience.

[David77]

There are a number of options, and I'll share what I know. 
To change the CI class there are at least 2 options
1.  change CI class in listview
2. Use System Data Management - Update Jobs 

For the Asset records, I only know of one way to do that, and it's with a fix script. 
Here's one of the better descriptions on how to do it.
https://www.servicenow.com/community/sam-forum/need-help-on-updating-the-model-category-in-asset/m-p...

I can provide a copy of my fix script if you'd like, but it only does one at a time and would need to be modified to do more.