Platform guides

ServiceNow CMDB Explained: What It Is, How It Works and Common Pitfalls

ServiceNow CMDB explained: CI classes, cmdb_rel_ci relationships, IRE, CSDM 5 and Health, plus what moves and breaks in a migration. Read the guide.

Ayush BothraFounding Member, MigrateX

Published Updated 12 min read

Small 3D servers, databases, apps and laptops linked by lines on a ServiceNow base, showing CMDB configuration items and relationships
On this page

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 planning a CMDB move into or out of ServiceNow, or cleaning one up first. Here is how it is built, where it goes wrong, and what happens to it in a migration.

What is the ServiceNow CMDB?

The ServiceNow CMDB (configuration management database) is the ServiceNow application that stores configuration items (CIs) and the relationships between them. ServiceNow describes it as the application to "build logical representations of assets, services, and the relationships between them that comprise the infrastructure of your organization" (ServiceNow CMDB docs, Brazil release, as of 20 Oct 2026).

A CI can be physical, such as a computer or router, logical, such as a database instance, or conceptual, such as a requisition service (same source).

A CMDB is not an asset register. ServiceNow says IT asset management "is the process of accounting for assets during their lifecycle", while the CMDB "is centered around the data used to manage assets during the period of time in which they are live" (ServiceNow, "What is a CMDB?", as of 20 Oct 2026). Put plainly, ITAM tracks what you bought; the CMDB tracks what is running and what depends on it.

How the ServiceNow CMDB works: data model and key tables

The ServiceNow CMDB is a set of related tables, not one table. These are the ones that matter when you report on, integrate with or move CMDB data.

Table or componentWhat it holdsWhy it matters
Configuration Item [cmdb_ci]The base class CI classes extendShared attributes live here
Class tables (for example computer, laptop)CIs of one type, inheriting from parent classesYour class hierarchy is your CI taxonomy
Related tables (for example Serial Number [cmdb_serial_number])Data that references a CI but does not inherit from cmdb_ciEasy to miss in exports
CI Relationship [cmdb_rel_ci]Two CIs and a relationship typeDependencies and impact analysis
Configuration item field and Impacted Services/CIsOne CI reference on a task, plus a many-to-many Task to cmdb_ci linkConnects incidents, problems and changes to CIs
Identification and Reconciliation Engine (IRE)Matches incoming data to existing CIsPrevents duplicates

Source: ServiceNow docs (Brazil release), as of 20 Oct 2026.

CI classes and ServiceNow CI relationships

Classes extend other classes: ServiceNow's example is a laptop class that extends the computer class, which extends the base CI class (ServiceNow docs, as of 20 Oct 2026).

"A relationship in the CMDB consists of two CIs and a relationship type" (ServiceNow docs, as of 20 Oct 2026). Types read in both directions, such as "Depends on" and "Used by", or "Runs on" and "Runs" (Tomcat runs on a Linux server), and admins now edit them in Unified Map (same source).

How data gets in: Discovery, connectors and the IRE

Discovery works through MID Servers that "run securely behind your firewall" and uses the IRE to prevent duplicate CIs (ServiceNow Discovery data sheet, as of 20 Oct 2026). Service Graph Connectors bring third-party data into CMDB and non-CMDB tables; ServiceNow says they use the IRE and are "released through the ServiceNow Store" (ServiceNow CMDB docs and connector program data sheet, as of 20 Oct 2026).

Inside the IRE, identification decides whether a record is a new or existing CI, matching dependent CIs only in the context of their host. Reconciliation decides which source may update which attributes (ServiceNow IRE docs, as of 20 Oct 2026).

CSDM 5: the service model on top of the CMDB

The Common Service Data Model (CSDM) is "the standardized data model that ServiceNow administrators should follow when configuring ServiceNow products and applications" (ServiceNow CSDM docs, as of 20 Oct 2026). The CSDM 5 white paper, posted by ServiceNow employee Scott Lemm on 6 May 2025, groups the model into seven domains: Foundation, Ideation & Strategy, Design & Planning, Build & Integration, Service Delivery, Service Consumption and Manage Portfolios (ServiceNow Community, as of 20 Oct 2026). We found no newer version.

Key capabilities of the ServiceNow CMDB

CapabilityWhat it does
CMDB WorkspaceSearch and explore the CMDB, check health, open dashboards
CMDB HealthScores duplicates, required fields and audits
CMDB Data ManagerPolicy-driven bulk deletion, archival and attestation
CI Class ManagerClass definitions plus identification, reconciliation and Health settings
CMDB 360History of which source proposed which attribute value; can revert a source's updates
Unified Map and Query BuilderMap CIs and relationships; query across classes and relationships
Data Certification and CI attestationValidate data on a schedule; confirm CIs still exist

Source: ServiceNow CMDB docs (Brazil release), as of 20 Oct 2026.

On licensing, ServiceNow says "CMDB is available with the ServiceNow AI Platform" (CMDB product page), and its ITSM pricing page lists "Asset Management and CMDB" in ITSM Foundation with no prices, only "Get Custom Quote" (both as of 20 Oct 2026).

Common ServiceNow CMDB problems teams hit

The most common ServiceNow CMDB problems are duplicate, orphan and stale CIs, incomplete records and over-scoping. CMDB Health measures them through four KPIs:

Health KPIWhat it flagsCommon cause
CorrectnessDuplicate, orphan and stale CIs (stale = not updated within 60 days by default)Imports that bypass the IRE; no one retiring CIs
CompletenessMissing required or recommended fieldsNo source or owner fills them
ComplianceFailed template or scripted audits (audits must be activated)CI values drift from your standards
RelationshipsOrphan and duplicate relationships; a relationship with a stale CI counts as staleRelationships lost when CIs are replaced

Source: ServiceNow CMDB Health docs (Brazil release), as of 20 Oct 2026.

Ownership is the common thread. ServiceNow says "Establishing clear ownership of CIs is vital for maintaining the accuracy and reliability of CMDB data" (ServiceNow, "What is a CMDB?", as of 20 Oct 2026).

Reviewers see the same. ServiceNow IT Operations Management holds 4.4/5 from 495 reviews on G2; its most-mentioned cons are learning difficulty (29), complexity (27), setup complexity (25) and expense (24). One June 2026 reviewer names "poor data quality, duplicates, or missing relationships" as the main CMDB challenge (G2, as of 20 Oct 2026). G2 has no separate CMDB listing, so these reviews cover ITOM as a whole.

The other mistake is scope. ServiceNow's implementation playbook calls the CMDB "the most critical foundation" but warns that aiming for completeness without strong discovery is "likely to result in excessive maintenance costs", and advises limiting CIs to what your target capability needs (ServiceNow implementation playbook, 2021, as of 20 Oct 2026). Fix these before a migration, because every duplicate and orphan you carry across must be mapped and reconciled again.

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. A historical incident or change carries a Configuration item reference plus Impacted Services/CIs entries, which "you can add to any task form"; change requests also use Affected CIs (ServiceNow docs, as of 20 Oct 2026). Lose those links and your change management history loses its context.

You can measure this before you move. ServiceNow's CMDB Data Foundations dashboard reports the share of change requests from the last 90 days, and incidents from the last 60 days, that reference a CI (ServiceNow docs, as of 20 Oct 2026). Record both figures before cutover as the baseline your target must match.

Moves cleanlyRebuilt on the targetAt risk (needs remapping)
CI records and attribute valuesIRE identification and reconciliation rulesClass hierarchy, mapped to the target's CI or object types
Retired CIs, if in scopeDiscovery schedules and MID ServersRelationship types and direction
Relationship records, once both CIs existService Graph Connectors and other integrationssys_id references: the target creates new IDs
CMDB Health, audits and Data Manager policiesCI links on historical incidents, problems and changes
Workflows, business rules and SLA definitionsCSDM services and offerings; owner and support group references

Workflows, business rules, automations and running SLA timers do not migrate. They are rebuilt on the target.

Load order keeps the links intact: CIs first, dependent CIs in the context of their hosts, 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 the steps together, and reconciling counts at each step proves nothing was dropped. Between two ServiceNow instances, a scripted load can keep the original sys_ids instead: see merging two ServiceNow instances.

Leaving ServiceNow

Export CIs, relationships and task-to-CI links together. The CMDB Instance API lists a class's CIs and returns a CI's "attributes and relationship information"; sysparm_limit defaults to 10,000 records per request, with sysparm_offset for paging (ServiceNow CMDB Instance API docs, as of 20 Oct 2026).

In Jira Service Management, Assets imports CSV, JSON and Assets Discovery data and can build references and parent-child hierarchies (Atlassian, as of 20 Oct 2026). Import referenced object types first; each import creates new object keys, so references match by label (Atlassian KB, updated 24 Jul 2026). Service Collection includes 5,000 Assets objects on Standard, 50,000 on Premium and 500,000 on Enterprise, then from $0.02 (USD) per object per month (Atlassian pricing page, as of 20 Oct 2026). Count your CIs before you pick a plan.

Freshservice says "Each asset is known as a Configuration Item (CI)" and imports through a discovery agent, a discovery probe or CSV (Freshservice support, modified 20 Feb 2025, as of 20 Oct 2026).

Our ServiceNow to Freshservice migration guide and ServiceNow to Jira migration guide cover those moves in full. The route pages for ServiceNow to Freshservice and ServiceNow to Jira Service Management show what moves on each.

Moving into ServiceNow

Load CIs through the IRE so your identification rules apply, using its REST or scriptable APIs or import sets (ServiceNow IRE docs, as of 20 Oct 2026). For classes with dependent identification rules, the CMDB Instance API needs "the sys_id of an existing CI", so load hosts before the applications on them; it also writes "one record at a time" (ServiceNow CMDB Instance API docs, as of 20 Oct 2026). The IRE can identify a CI by source_name and source_native_key, which keeps each CI tied to its old-system ID (ServiceNow IRE docs). Coming from BMC? Our Remedy to ServiceNow guide covers the BMC CMDB side.

ServiceNow CMDB migration checklist

  1. Record CMDB Health and Data Foundations results as your baseline.
  2. Decide scope: operational CIs only, or retired and stale CIs too.
  3. Inventory classes in use, including custom classes.
  4. Map each relationship type, with direction, to the target.
  5. Build a sys_id crosswalk from old IDs to new IDs.
  6. Map CSDM services and service offerings.
  7. Decide how historical tasks keep their Configuration item and Impacted Services/CIs links.
  8. List every source that writes to the CMDB.
  9. Plan discovery and integrations as rebuilds.
  10. Rebuild identification and de-duplication rules before loading.
  11. Test-migrate one class; reconcile counts, relationships and task links.
  12. Plan cutover with delta sync, a CMDB write freeze, reconciliation and a go/no-go.

Facts checked October 20, 2026 from ServiceNow CMDB docs, ServiceNow IRE docs, ServiceNow CMDB Health docs, ServiceNow CMDB Instance API and ServiceNow CSDM docs. No vendor paid for this article. How we research

ServiceNow CMDB FAQ

What is CMDB in ServiceNow, and what does it stand for?

CMDB stands for configuration management database. In ServiceNow, it is the application that stores configuration items, such as servers, applications, databases and services, and the relationships between them. Incidents, problems and changes reference those CIs, which gives each record its infrastructure context (ServiceNow CMDB docs, as of 20 Oct 2026).

What is the difference between a CI and the CMDB?

A configuration item is one record: a single server, application, database or service. The CMDB is the database that holds all CIs, organized into classes that extend cmdb_ci, plus the relationship records in cmdb_rel_ci that connect them (ServiceNow docs, as of 20 Oct 2026).

What is CMDB vs CSDM?

The CMDB is where configuration data is stored. The Common Service Data Model (CSDM) is ServiceNow's standard for how that data should be structured, especially services and service offerings. You can run a CMDB without CSDM, but ServiceNow says the shared model "significantly increases the power of your applications" (ServiceNow CSDM docs, as of 20 Oct 2026).

Is ServiceNow a CMDB?

No. ServiceNow is a platform that runs many applications, including ITSM, IT operations management and asset management. The CMDB is one application within it. ServiceNow says "CMDB is available with the ServiceNow AI Platform", and lists it in the ITSM Foundation package (ServiceNow, as of 20 Oct 2026).

How long does a ServiceNow CMDB migration take?

There is no neutral public benchmark. Duration depends on how many CIs and classes are in scope, how many relationships and task-to-CI links must be rebuilt, how much cleanup Health calls for, and how many test migrations it takes to reconcile. Loading into ServiceNow matters too, since the CMDB Instance API writes one record at a time.

Written by

Ayush Bothra

Founding Member, MigrateX

Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.