CSDM Guide
The CSDM Crawl Guide
What the Crawl stage actually means, why most organizations stall at Foundation, and how GetInSync accelerates you from Foundation to Crawl without a multi-year transformation project.
The five stages of CSDM maturity
ServiceNow's Common Service Data Model (CSDM) is the standardized framework that defines how service-related data is structured, organized, and connected across the platform. Without CSDM alignment, organizations struggle with incident management, service mapping, application portfolio management, and reporting.
ServiceNow describes maturity in five stages. Most organizations find themselves stuck somewhere between the first two.
Foundation
Where most organizations start
Basic data exists but it's inconsistent. Application records are incomplete, ownership is unclear, and the service model hasn't been defined. There's no shared language between IT and the business.
Crawl
This guideThe first meaningful milestone
Business applications are defined and owned. Deployment profiles exist. Applications are linked to services. Leadership can begin asking portfolio questions and getting defensible answers.
Walk
Operational clarity
Service offerings are defined. Cost and contract data is structured. Integration mapping is in place. Teams can run meaningful reporting across the portfolio.
Run
Strategic visibility
Portfolio decisions are data-driven. Lifecycle management is active. Technology health is tracked. Investment conversations are backed by evidence, not estimates.
Fly
Full platform value
Real-time service health, automated discovery, full CMDB accuracy. The platform is self-maintaining and executive reporting is continuous.
Why Crawl is the stage that actually matters
Foundation is where you document what exists. Crawl is where you start making decisions with it.
At the Crawl stage, business applications are properly defined and owned. Each application has a deployment profile - a structured record of how it runs, what it costs, and what it depends on. Leadership can ask "what do we run, who owns it, and what does it cost?" and get a defensible answer within hours, not weeks.
That sounds basic. But for most organizations, it represents a genuine transformation in how IT communicates with the business. Before Crawl, portfolio conversations require assembling spreadsheets, chasing owners, and reconciling inconsistent lists. After Crawl, those conversations are grounded in shared data.
Walk, Run, and Fly build on that foundation. But Crawl is where the ROI of CSDM adoption first becomes visible to leadership - and where budget conversations shift from "trust us" to "here's the evidence."
"Most teams reach Crawl within 6 to 12 months. Most teams that try to skip Crawl never reach Walk."
What holds organizations at Foundation
Most teams don't get stuck at Foundation because of a technical problem. They get stuck because of sequencing, scope, and expectation mismatches.
Waiting for perfect CMDB data
The most common trap. Teams believe CSDM adoption requires a clean, accurate CMDB first. So they spend months improving data quality before building any portfolio structure. But Crawl doesn't require a perfect CMDB - it requires a usable one. Clear ownership, basic lifecycle data, and cost information are enough to start. Maturity improves in parallel, not as a prerequisite.
Scope that grows before value is visible
An APM mandate lands on the ITSM team with vague requirements: improve clarity, reduce duplication, strengthen lifecycle discipline. Without clear sequencing, the project expands to cover everything at once. Capability mapping, full service modeling, integration documentation, financial alignment. The scope becomes unmanageable and momentum stalls before any executive-visible output exists.
Treating Crawl as a CMDB project
CSDM maturity is a portfolio visibility initiative, not a configuration management exercise. When it gets handed to the CMDB team as a data quality project, the outputs are technical - but leadership still can't answer basic portfolio questions. The right audience for Crawl outputs is executives, not configuration managers.
No shared definition of what Crawl looks like
ServiceNow's documentation describes the stages at a high level. Most organizations struggle to translate that into concrete tasks with clear owners and measurable outcomes. Without that translation, teams can't tell whether they're making progress or marking time.
What reaching Crawl actually requires
Crawl is achievable with a focused dataset and clear ownership. You don't need every field populated or every relationship mapped. You need the attributes that support executive decision-making.
Application inventory
A defensible list of every business application your organization operates - not a CMDB export, but a curated portfolio view with clear ownership and lifecycle stage for each entry.
Deployment profiles
Each application needs at least one deployment profile - a structured record of how it runs (SaaS, on-prem, cloud), what environment it operates in, and who is responsible for it.
Cost and contract visibility
Basic cost data: annual spend, vendor, renewal date. Doesn't need to be precise accounting - it needs to be directionally accurate enough to identify concentration and timing risk.
TIME assessment
Each application rated as Tolerate, Invest, Modernize, or Eliminate based on business fit and technical health. This is the output that makes portfolio conversations credible to leadership.
When these four elements are in place, leadership can answer the questions that matter: what do we run, what is it worth keeping, what is it costing us, and what are we doing about it. That is the Crawl milestone.
Where GetInSync fits
GetInSync is built around the CSDM data model from the ground up. Business applications, deployment profiles, IT services, and software products in GetInSync map directly to their equivalents in ServiceNow's CSDM - so the work you do in GetInSync is never thrown away when you're ready to sync.
Most teams use GetInSync to reach Crawl faster than they could inside ServiceNow directly. The platform hides the complexity of CSDM - users answer plain-language questions about their applications, and the data lands in the right structure automatically. No metamodel configuration. No custom objects to build.
Whether your organization is on ServiceNow today or planning to be, GetInSync gives you the portfolio foundation to get there - without waiting for a clean CMDB or a completed architecture model.
| GetInSync | ServiceNow CSDM |
|---|---|
| Business Application | cmdb_ci_business_app |
| Deployment Profile | cmdb_ci_service_auto (Application Service) |
| IT Service (Shared) | service_offering (Technical Service Offering) |
| IT Service (Local) | cmdb_ci_service_technical (Technical Service) |
| Software Product | alm_product_model (Software Model) |
Ready to move from Foundation to Crawl?
Get in touch and we'll walk through where your portfolio stands today and what reaching Crawl looks like for your organization specifically.