Need help with CMDB cleanup options

[Uttam Sai]

Hi ,

We are planning to Cleanup some unwanted CMDB CIs . 

Is there a way we can Hide or deactivate them before deleting them later.

Thank you
Uttam Sai S

[Connectmustaq]

Hi @Uttam Sai ,

Yes, you can "hide" or deactivate CMDB CIs before deleting them later—a common best practice to safeguard operational history, auditability, and prevent accidental loss. In ServiceNow, this is typically achieved by setting a CI’s operational status (for example, to "Retired") or updating the install status (to values like "Absent" or "Disposed") instead of directly deleting the CI.

You can check this question in community:-https://www.servicenow.com/community/sysadmin-forum/delete-quot-absent-quot-ci/m-p/2427783

How to Hide or Deactivate CMDB CIs

• Change the Operational Status:

• Update the Install Status:

• Mark as Non-Principal Class / Remove from Dashboards:

Key Points:

1. Archiving: Instead of deleting immediately, archiving or setting the CI as non-operational is recommended for compliance and reverting decisions if necessary.

2. Deletion: Once verified as safe and unwanted, these CIs can be batch deleted from the CMDB using Data Manager or deletion jobs.

3. Best Practice: Never delete critical CIs without first retiring/inactivating, analyzing dependencies, and retaining necessary audit records.

This approach is widely used for CMDB hygiene and ensures a safe, reversible deactivation and cleanup process in ServiceNow

If it is helpful, please hit the thumbs button and accept the correct solution by referring to this solution in the future it will be helpful to them.

 

Thanks & Regards,

Mohammed Mustaq Shaik