Methodology: built from ServiceNow, Atlassian and Freshservice documentation and product pages, Gartner research summaries and G2 reviews, checked on 28 and 29 Sep 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.
The ServiceNow CMDB is the part of the ServiceNow platform that stores your configuration items (servers, applications, databases, services) and the relationships between them. Incidents, problems and changes point at those CIs, which is why the CMDB sits under most of what ServiceNow does. This guide is for platform owners and service management leads who inherited a ServiceNow CMDB, need to clean one up, or are comparing ITSM platforms ahead of a move to or from ServiceNow. Here is how it is built, where it goes wrong, and what happens to it in a migration.
Key takeaways
- Every CI class in the ServiceNow CMDB extends the base Configuration Item [cmdb_ci] class, so child classes inherit its attributes (ServiceNow, as of 28 Sep 2026).
- A relationship is its own record: a parent CI, a child CI and a relationship type, stored in the CI Relationship [cmdb_rel_ci] table (ServiceNow, as of 28 Sep 2026).
- The Identification and Reconciliation Engine (IRE) matches incoming data to existing CIs to prevent duplicates, and lets "only authoritative data sources" write to the CMDB (ServiceNow, as of 28 Sep 2026).
- CMDB Health scores data on correctness, completeness and compliance, and flags CIs as stale after 60 days without an update by default (ServiceNow, as of 28 Sep 2026).
- Incidents and changes link to CIs through Affected CIs, a many-to-many link between the Task [task] and cmdb_ci tables, which a migration must carry across (ServiceNow, as of 28 Sep 2026).
What is the ServiceNow CMDB?
The ServiceNow CMDB (configuration management database) is the ServiceNow application for building "logical representations of assets, services, and the relationships between them" that make up your infrastructure. Each component is stored as a configuration item (CI), which teams use to monitor infrastructure and keep services running (ServiceNow, as of 28 Sep 2026).
A CI can be physical, such as a computer or router. It can be logical, such as a database instance. It can also be conceptual, such as a requisition service (ServiceNow, as of 28 Sep 2026).
The CMDB supports the ITIL service configuration management practice, which PeopleCert describes as providing "accurate and reliable information about the configuration of services and configuration support items when and where it is needed" (PeopleCert, as of 28 Sep 2026).
A CMDB is not the same as an asset register. Gartner notes that many organizations lack clear rules on whether asset and configuration data belongs in an IT asset management tool, a CMDB, or both (Gartner, as of 28 Sep 2026).
How the ServiceNow CMDB works: data model and key tables
The ServiceNow CMDB is a set of related tables, not one table: CI class tables that extend cmdb_ci, a relationship table (cmdb_rel_ci), task-to-CI link tables, with the IRE controlling what gets written. They matter most when you report on, integrate with or move data out of the CMDB.
| Table or component | What it holds or does | Why it matters |
|---|---|---|
| Configuration Item [cmdb_ci] | The base class every CI class extends | Shared attributes live here |
| Class tables (for example computer, laptop) | CIs of one type, inheriting attributes from parent classes | Your class hierarchy is your CI taxonomy |
| Related tables (for example Serial Number [cmdb_serial_number]) | Data linked to CIs that doesn't inherit from cmdb_ci | Easy to miss in exports |
| CI Relationship [cmdb_rel_ci] | Parent CI, child CI and relationship type | Dependencies and impact analysis |
| Affected CIs and Impacted Services/CIs | Many-to-many links between Task [task] and cmdb_ci | Connects incidents and changes to CIs |
| Identification and Reconciliation Engine (IRE) | Matches incoming data to existing CIs | Prevents duplicates |
Sources: ServiceNow docs on the CMDB, relationships, Affected CIs and IRE, as of 28 Sep 2026.
CI classes and the CMDB hierarchy
CIs that share attributes live in their own class table, and classes extend other classes: laptop extends computer, which extends the base CI class. Admins manage classes and their identification settings in the CI Class Manager (ServiceNow, as of 28 Sep 2026).
Relationships in cmdb_rel_ci
Each relationship record has a parent CI, a child CI and a type. Types come in directional pairs, such as "Depends on" and "Used by", or "Runs on" and "Runs". Admins edit them in the Unified Map in CMDB Workspace (ServiceNow, as of 28 Sep 2026).
How data gets in: Discovery, connectors and the IRE
ServiceNow's Discovery data sheet says Discovery scans infrastructure through MID Servers behind your firewall and uses the IRE to prevent duplicate CIs (ServiceNow, as of 28 Sep 2026). Service Graph Connectors bring third-party data into the CMDB, also through the IRE, and are available from the ServiceNow Store (ServiceNow, as of 28 Sep 2026).
The IRE is the ServiceNow service that decides how incoming data lands in the CMDB, and it does two jobs. Identification decides whether an incoming record is a new or existing CI. Dependent CIs are identified in context, so an application is matched only after its host server. Reconciliation decides which source may update which attributes, allowing "only authoritative data sources to write to CMDB" (ServiceNow, as of 28 Sep 2026).
CSDM 5: the service model on top of the CMDB
The Common Service Data Model (CSDM) is ServiceNow's "standardized framework that defines service-related terms and relationships for all ServiceNow products" (ServiceNow, as of 28 Sep 2026).
The CSDM 5 white paper, published by ServiceNow staff on 6 May 2025, organizes the model into seven domains: Foundation, Ideation & Strategy, Design & Planning, Build & Integration, Service Delivery, Service Consumption and Manage Portfolios (ServiceNow Community, as of 28 Sep 2026). In practice, CSDM tells you where services and offerings belong in your CMDB.
Key capabilities of the ServiceNow CMDB
Most of the ServiceNow CMDB's built-in capabilities exist to keep CI data accurate.
| Capability | What it does |
|---|---|
| CMDB Workspace | Central place to search the CMDB, check health and open dashboards |
| CMDB Health | Scores duplicates, required fields and audits |
| CMDB Data Manager | Bulk lifecycle actions such as delete, archive and attestation |
| CI Class Manager | Creates and edits classes and their identification and reconciliation settings |
| CMDB 360 | Shows which discovery sources updated which attributes, and when |
| Duplicate CI Remediator | Finds and fixes duplicate CIs |
| Unified Map | Shows CI relationships and business context graphically |
| Data Certification and CI Attestation | Has owners confirm that CI data is correct and that CIs still exist |
Sources: ServiceNow CMDB documentation and ServiceNow CMDB product page, as of 28 Sep 2026.
On licensing, ServiceNow says the CMDB "is available with the ServiceNow AI Platform." It does not publish list prices on its CMDB product page, and it lists Discovery and Service Mapping among related products (ServiceNow, as of 28 Sep 2026). Confirm with your account team what your subscription covers. Our guide to how ServiceNow prices its platform explains the packages.
Common ServiceNow CMDB problems teams hit
The most common ServiceNow CMDB problems are duplicate, orphan and stale CIs, incomplete records and over-scoping. ServiceNow's CMDB Health scorecard measures data quality in three areas:
- Correctness: orphan CIs, stale CIs (not updated within 60 days by default) and duplicate CIs found using identification rules (ServiceNow, as of 28 Sep 2026).
- Completeness: CIs missing required or recommended fields.
- Compliance: CIs whose values fail template or scripted audits.
Each Health signal points to a common cause:
| Health signal | Common cause |
|---|---|
| Duplicate CIs | An import or integration bypasses the IRE |
| Orphan CIs | Relationships were never created, or were lost when a CI was replaced |
| Stale CIs | No one owns retiring CIs |
| Missing required or recommended fields | No source or owner fills the fields your processes rely on |
| Failed audits | CI values drift from the standards your audits check |
Reviewers report the same pattern. ServiceNow IT Operations Management holds 4.4/5 from 475 reviews on G2, and its most-mentioned cons are a steep learning curve (29 mentions), overall complexity (27), setup complexity (25) and cost (24) (G2, as of 28 Sep 2026). One reviewer names "poor data quality, duplicates, or missing relationships" as the main CMDB challenge (G2, as of 28 Sep 2026). G2 has no separate CMDB listing, so these reviews cover ITOM as a whole.
Gartner's Luis Fernandez and Steve White write that a CMDB tool is "difficult to implement and maintain" but provides valuable data when properly managed (Gartner, 12 Aug 2024, as of 28 Sep 2026). The other common mistake is scope. Gartner warns that putting every IT asset into the CMDB for convenience can undermine its usefulness (Gartner, 3 Jun 2024, as of 28 Sep 2026). If a migration is coming, fix these first and audit your legacy service desk data before the migration, because every duplicate and orphan you carry across must be mapped and reconciled on the target.
The ServiceNow CMDB in a migration: what moves and what breaks
The CMDB is harder to migrate than tickets because other records point at it. Every historical incident, problem and change can carry a configuration item plus Affected CIs, which are many-to-many links between the Task table and cmdb_ci (ServiceNow, as of 28 Sep 2026). Lose those links and your change history loses its context. That is why the CMDB deserves its own workstream in any ITSM migration plan.
In short: CI records and relationship records move; the class model, relationship types, sys_id references and task-to-CI links need remapping; and the IRE rules, discovery and integrations that keep the CMDB accurate are rebuilt on the target.
| Moves cleanly | Needs remapping or at risk | Rebuilt on the target |
|---|---|---|
| CI records and attribute values | Class hierarchy, mapped to the target's CI types or object types | IRE identification and reconciliation rules |
| Retired CIs, if you put them in scope | Relationship types and their direction (parent and child) | Discovery schedules and MID Servers |
| Relationship records, once both CIs exist on the target | sys_id references: the target creates new IDs, so keep a crosswalk | Service Graph Connectors and other integrations |
| Affected CI links on historical incidents and changes | CMDB Health scorecards, audits and Data Manager policies | |
| CSDM services, offerings and application services | Workflows, business rules and SLA definitions | |
| Reference fields that point to users and groups, such as owner and support group |
Workflows, business rules, automations and running SLA timers do not migrate. They are rebuilt on the target.
Load order is what keeps those links intact: CIs first, dependent CIs in the context of their hosts, then relationships once both ends exist, then the task-to-CI links on historical records. A crosswalk from old sys_id values to new IDs ties each step together, and reconciling counts at each step is how you prove data fidelity in the migration.
Leaving ServiceNow
Export CIs, relationships and task-to-CI links together, so the target can rebuild them as one set. The CMDB Instance API reads CIs by class and returns a CI's attributes and relationship information. Its sysparm_limit parameter defaults to 10,000 records per request, with sysparm_offset for pagination (ServiceNow, as of 28 Sep 2026).
Each target models CIs its own way, which is worth checking early if you are still shortlisting ServiceNow alternatives.
In Jira Service Management, Assets imports CSV and JSON data and can build references and parent-child hierarchies during import (Atlassian, as of 28 Sep 2026). Atlassian's Service Collection includes 5,000 Assets objects on Standard, 50,000 on Premium and 500,000 on Enterprise, then charges $0.02 (USD) per object per month (Atlassian, as of 28 Sep 2026). Count your CIs before you choose a plan. For the wider platform differences, see ServiceNow vs Jira Service Management.
Freshservice treats each asset as a CI, lets admins create relationships between assets, and imports through a discovery agent, a discovery probe or CSV files (Freshservice, as of 28 Sep 2026). Our ServiceNow vs Freshservice comparison covers how the two CMDBs differ.
Moving into ServiceNow
Load CIs through the IRE so your identification rules apply. ServiceNow offers REST and scriptable IRE APIs for third-party data (ServiceNow, as of 28 Sep 2026). Load order matters. For classes with dependent identification rules, the CMDB Instance API needs the sys_id of an existing CI to create the new one, so load hosts before the applications that run on them (ServiceNow, as of 28 Sep 2026). The API writes one record at a time. The IRE can also identify a CI by the name of its source and that source's own key (source_name and source_native_key), which gives you a way to keep each CI tied to its ID in the old system (ServiceNow, as of 29 Sep 2026). The rest of the platform move, from tickets to knowledge, is covered in our ServiceNow migration guide.
ServiceNow CMDB migration checklist
- Run CMDB Health and record the three scores before scoping.
- Decide scope: operational CIs only, or retired and stale CIs too.
- Inventory classes in use, including custom classes.
- Map each relationship type, with direction, to the target.
- Build a sys_id crosswalk from old IDs to new IDs.
- Map CSDM services and service offerings.
- Decide how historical incidents, problems and changes keep their CI links.
- List every source that writes to the CMDB.
- Plan target discovery and integrations as rebuilds.
- Rebuild identification and de-duplication rules on the target before loading.
- Test-migrate one class and reconcile counts, relationships and task links, following a zero-loss migration framework for sign-off.
- Plan cutover with delta sync, a CMDB write freeze, reconciliation and a go/no-go.
ServiceNow CMDB FAQ
Methodology
We built this guide from ServiceNow's documentation (Brazil release), product pages, Discovery data sheet and the CSDM 5 white paper by ServiceNow staff. Atlassian and Freshservice documentation is used only for their own products, Gartner summaries for analyst views and G2 for user sentiment. All sources were checked on 28 Sep 2026, and the IRE page was re-checked on 29 Sep 2026. We did not run hands-on tests.
Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.