ServiceNow CSDM Life Cycle Migration in the Australia release

# ServiceNow CSDM Life Cycle Migration in the Australia release ## Scope and currency of findings This report summarizes the **Common Service Data Model (CSDM) life-cycle standards** and migration support in the **Australia** family release of ServiceNow[[1]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html), using Australia-version product documentation updated **March 12, 2026** (where available). [[2]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) For timeline context, the Australia release documentation indicates **Early availability: Q1 2026** and **General availability: TBD** (as published in the release-notes landing pages). [[3]](https://www.servicenow.com/docs/r/pt-BR/release-notes/rn-learn-landing-page.html) ## What “CSDM life cycle” means in Australia In Australia documentation, CSDM “life cycle” is centered on a **two-field “life-cycle value pair”**: · **Life cycle stage**: a broad phase (for example, from procurement to operation to end of life) · **Life cycle stage status**: a more specific status within the current stage [[4]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) These values are intended to standardize how “status” is represented across the platform, replacing or aligning older, inconsistent “legacy” status fields. The documentation explicitly calls out legacy status types that commonly exist before adopting life-cycle values, including **install status**, **operational status**, **hardware status**, and related substatus fields. [[5]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) Australia documentation also frames life cycle in terms of a **product instance** concept that can include an **asset**, a **CI**, and an **install base item (IBI)**, and it explicitly identifies the core tables involved: · **CI**: CMDB CI table **[cmdb_ci]** · **Asset**: **[alm_asset]** · **Install base item (IBI)**: **[sn_install_base_item]** [[4]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) A critical model feature for governance is that valid stage/status combinations are constrained by “life cycle control” rules. In multiple life-cycle domain pages (tangible/physical, product, document), the documentation states that the **[life_cycle_control]** table “uses the type of CI … to determine which life cycle stage status values are available for each life cycle stage.” [[6]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-lifecycle-hardware.html) ## Out-of-the-box migration and synchronization capabilities in Australia Australia documentation describes a fairly prescriptive, OOTB-first migration mechanism that: · **maps legacy status fields to CSDM life-cycle value pairs**, then · performs a **one-time bulk alignment**, then · switches to **ongoing synchronization** via scheduled logic and business rules. [[7]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) ### Mapping and governance tables The base system includes a **Life Cycle Mapping** table **[life_cycle_mapping]**, prepopulated with mappings between widely used legacy status values and the equivalent life cycle stage/stage status values. Mapping rules are applied with explicit **priority**, and the system favors the highest priority rule when multiple candidates match. [[8]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) The **Life cycle mapping form** description in Australia documentation is particularly relevant if you plan to ingest mappings and evaluate “readiness” in an external platform: · **Mapping for table** applies to a legacy CMDB table and (by default) its descending tables, unless a child-table-specific mapping exists. [[9]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.html?contentId=pqCEWiVx6dheaSNluvD9~g) · **Priority** is used during legacy-to-life-cycle sync when multiple legacy values match mapping rules. [[9]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.html?contentId=pqCEWiVx6dheaSNluvD9~g) · If a mapping is inactive or missing, the platform can set the standard life cycle fields to **TBD** (“To Be Determined”). [[9]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.html?contentId=pqCEWiVx6dheaSNluvD9~g) ### The migration “switch” and the key system property The transition from “legacy-driven” synchronization to “life-cycle-driven” synchronization is controlled by the system property: · **csdm.lifecycle.sync.between.ci.and.asset.activated** Australia documentation states that selecting **Enable life cycle sync** from the Life Cycle Mapping list page sets this property to true and runs validation that generates a **discrepancy report** you must remediate before bulk alignment. [[10]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) In the sync reference documentation, the property behavior is described as: · when **false (default)**: synchronization between asset and CI is mediated via **legacy status/substatus fields** · when **true**: the system synchronizes **life cycle stage and life cycle stage status values directly**, providing “significant benefits.” [[11]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/cmdb-asset-CI-IBI-sync-options.html) ### End-to-end OOTB process stages Australia documentation describes four broad phases for alignment/sync when enabling life-cycle sync from legacy-to-asset: · **Phase 1**: discrepancy check and mapping remediation (includes validating mapping rules, including legacy asset-to-CI mapping tables like **alm_hardware_state_mapping** and **alm_asset_ci_state_mapping**) [[12]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) · **Phase 2**: automated bulk alignment to life cycle stage/status pairs (one-time scheduled batch process) [[12]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) · **Phase 3**: update to sync operations (notably, legacy-value changes no longer update life-cycle pairs directly; instead, updates flow through asset↔CI life-cycle synchronization) [[13]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) · **Phase 4**: ongoing automated sync among **asset, CI, and IBI**, maintained by business rules and scheduled logic [[14]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) ### Relationship to activating “CSDM” more broadly Australia documentation ties life-cycle readiness to the broader act of “activating” CSDM: **before you activate the CSDM plugin**, you must map existing life-cycle data to standard CSDM attributes, and the mapping enables tracking assets through transitions with CMDB Data Manager. [[15]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-enable.html) ## Built-in dashboards and metrics you can reuse without Performance Analytics A major Australia-era capability—highly relevant to your “OOTB-first metrics, no Performance Analytics dependency” requirement—is the **CSDM and CMDB Data Foundations Dashboards** store app. The documentation states: · the app provides dashboards with “key foundational metrics” for CMDB and CSDM, and · the capability is provided by the **com.snc.cmdb.getwell** plugin, “activated by default in base systems,” and · the dashboards do **not** support domain separation. [[16]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) ### The specific lifecycle-related health signal to target On the **CSDM Data Foundations dashboard**, the “Crawl” stage includes a report titled: · **CIs with Mismatched Operational Status and Life Cycle Stage** Australia documentation states that this report identifies “life-cycle value mismatches among CMDB, asset, and IBI,” and that it is useful when aligning existing status data to CSDM guidelines. [[17]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-datafdn-dash-crawl-tab.html?contentId=lWpo3ZNZwWFgddbZwMELjA) This aligns closely to your requirement to validate progress and compliance toward a target life-cycle state. ### Where scores and metric configuration live in tables Crucially for ingestion: · The **CSDM Get Well Metric Collection** scheduled job “calculates and stores” metric results, and metric scores are stored in **CSDM Data Foundations Metric Scores [sn_getwell_csdm_score]**. The job runs daily by default, and the dashboard depends on its first run to populate data. [[18]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) · The CMDB equivalent stores metric scores in **[sn_getwell_cmdb_score]**, and explicitly labels the Get Well Metric Collection as a **non-PA job** (with PA jobs only needed for PA widgets/trending). [[19]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/cmdb-data-foundations-dashboard.html?contentId=W3jznFFdpcXU5nbjXnCNqQ) · Metric definitions and performance-management settings (active flag, aggregate limits, runtime thresholds, etc.) are stored in **CMDB/CSDM Get Well Metrics [sn_getwell_metric]**, and ServiceNow documents how to deactivate or limit a metric by updating records in that table. [[16]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) This means you can ingest **sn_getwell_csdm_score + sn_getwell_metric** to obtain OOTB compliance percentages and health signals, while entirely avoiding Performance Analytics for the core “score” and “current state” view. [[20]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) ## AI assistance in Australia for life-cycle migration Australia documentation includes an explicit AI capability related to life-cycle migration in the “Now Assist for CMDB” / AI platform capabilities area: **“CSDM life cycle migration agentic workflow.”** [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) Key points from the Australia page: · It describes a **scan job** that identifies life-cycle-related metadata (scripts, business rules, UI actions, etc.) interacting with legacy life-cycle fields such as **operational_status, install_status, hardware_status**. [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) · The stated intent is to help customers understand current state and dependencies to enable migration to the CSDM life cycle. [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) · It is framed as targeted for an **Innovation Labs** store-app release (“Target is for Innovation Labs release of new store app in Q1”). [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) · The documentation calls out important **limitations**, such as not scanning flows and imperfect detection in some script patterns. [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) · The page describes interaction via a Now Assist panel/skill and notes feedback is stored in Agentic AI logs (sys_generative_ai_log_list.do). [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) What this implies for your planning: **ServiceNow is (at least in limited form) productizing AI-assisted dependency discovery for life-cycle migration** in the Australia timeframe; however, it is described as an Innovation Labs–targeted approach and appears oriented toward “dependency discovery” rather than automatically remediating mappings or executing migration itself. [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) ## Feasibility of compliance metrics via APIs and minimal ServiceNow artifacts You asked specifically about using the **Table API** (which you already have) to pull compliance metrics, and optionally adding foundational views/reports while staying OOTB-first and avoiding Performance Analytics. Based on Australia-era API references and platform docs, there are three practical, low-friction options. ### Using Table API counts for “how many CIs are aligned” ServiceNow’s Table API documentation specifies an **X-Total-Count** response header: “Total count of records returned by the query.” It also documents Link headers for paging. [[22]](https://www.servicenow.com/docs/r/yokohama/api-reference/rest-apis/c_TableAPI.html) That gives you a lightweight way to compute counts without retrieving all rows: issue a filtered query with sysparm_limit=1 and read X-Total-Count. For example, to count CIs with both life-cycle fields populated (illustrative field names shown), your integration can perform a query like: GET /api/now/table/cmdb_ci ?sysparm_query=life_cycle_stageISNOTEMPTY^life_cycle_stage_statusISNOTEMPTY &sysparm_limit=1 &sysparm_fields=sys_id This “Table API + count header” approach is attractive when you want to minimize additional API surface area and stay close to what you already support. [[22]](https://www.servicenow.com/docs/r/yokohama/api-reference/rest-apis/c_TableAPI.html) ### Using Aggregate API for grouped compliance metrics without Performance Analytics If you want richer rollups like “count by stage” or “count by stage status,” the Aggregate API is built for this and is documented for Australia. The **Aggregate API** provides a GET /now/stats/{tableName} endpoint and supports: · sysparm_count for record counts · sysparm_group_by for grouping · sysparm_query for encoded query filters · sysparm_display_value behavior for reference/choice grouping nuances [[23]](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AggregateAPI.html) An illustrative example to count CIs by life-cycle stage might look like: GET /api/now/stats/cmdb_ci ?sysparm_count=true &sysparm_group_by=life_cycle_stage &sysparm_query=life_cycle_stageISNOTEMPTY This approach stays “license-light” (it’s a core REST capability) and is typically far more efficient than pulling records for external aggregation. [[23]](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AggregateAPI.html) ### Reusing OOTB Data Foundations score tables as your compliance source of truth Because ServiceNow already computes and stores scores for CSDM Data Foundations metrics in **sn_getwell_csdm_score** (via the daily **CSDM Get Well Metric Collection** job), you can treat those score records as the authoritative OOTB metric layer and ingest them directly. [[24]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) This is particularly compelling for your stated goal (“as OOTB as possible”) because it: · avoids building bespoke reports · avoids Performance Analytics (for the score itself) · aligns your UI to the same “health” view customers already see in-platform [[25]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) For life-cycle migration, you can specifically ingest the metric score record(s) corresponding to the Crawl-stage indicator **“CIs with Mismatched Operational Status and Life Cycle Stage.”** [[26]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-datafdn-dash-crawl-tab.html?contentId=lWpo3ZNZwWFgddbZwMELjA) ### Minimal “extra artifacts” that remain close to OOTB If you discover you need more than the score tables (for example, you want _your_ tool to show an exact list of noncompliant CIs per metric), the least-invasive artifacts that stay aligned to platform best practices are: · **Database views** to materialize the join logic you need (for example, CI ↔ asset ↔ install base item) in a query-friendly way. ServiceNow documents database-view limitations (read-only output, various constraints) and supports creating/views administratively. [[27]](https://www.servicenow.com/docs/r/platform-administration/table-administration-and-data-management/c_DatabaseViews.html?utm_source=chatgpt.com) · **Saved reports** (sys_report) that implement lifecycle compliance filters and can be executed/queried via API. This is generally “lighter” than custom script logic, though still configuration. In many instances, you can avoid both by combining: 1) Aggregate API rollups for counts and distributions, and 2) direct table ingestion of the mapping + control tables for “configuration compliance.” ## Planning implications for your metadata management platform Given your platform already ingests CMDB relationships and builds architecture diagrams, the Australia-era CSDM life-cycle migration surface area lends itself to a feature set that is mostly **configuration and coverage analytics** rather than record-by-record transformation. A practical approach—grounded in what ServiceNow itself exposes OOTB in Australia—would model your feature around four data “planes,” all accessible through REST table-style ingestion: · **Lifecycle configuration plane**: ingest **life_cycle_mapping**, **life_cycle_control**, and the life-cycle term tables (life_cycle_stage / life_cycle_stage_status) so you can (a) render the enterprise’s configured mapping logic, and (b) detect gaps that would cause values to land in **TBD**. [[28]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) · **Lifecycle execution plane**: ingest CI/asset/IBI records (at least the subset relevant to migration), focusing on legacy status fields plus life-cycle fields. ServiceNow defines the core tables (cmdb_ci, alm_asset, sn_install_base_item) and the legacy fields it expects customers to migrate from. [[29]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) · **Migration state and sync mode plane**: ingest the system property **csdm.lifecycle.sync.between.ci.and.asset.activated** and interpret it as the system’s sync mode selector (default false vs “direct life-cycle sync” true). [[30]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/cmdb-asset-CI-IBI-sync-options.html) · **OOTB compliance plane**: ingest Data Foundations metric configuration and score tables (**sn_getwell_metric**, **sn_getwell_csdm_score**, optionally sn_getwell_cmdb_score), and highlight the specific Crawl indicator about operational status vs life-cycle stage mismatches as your lifecycle-alignment health signal. [[31]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) Finally, if you want to compete directly with the emerging AI-based dependency discovery described in Australia’s “agentic workflow” page, the “minimum viable” equivalent in your platform would be a **deterministic dependency scan** over ServiceNow metadata tables that looks for references to legacy fields (operational_status, install_status, hardware_status) across scripts and configuration artifacts—mirroring the scan described in the documentation, including acknowledging (in UX) the same limitations around flows or constant indirection. [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) --- [[1]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) [[18]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) [[24]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) [[25]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) Configure Data Foundations dashboard [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-foundations-dashboard.html) [[2]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) [[7]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) [[10]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) [[12]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) [[13]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) [[14]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) Sync life cycle [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-standard-values.html) [[3]](https://www.servicenow.com/docs/r/pt-BR/release-notes/rn-learn-landing-page.html) Learn about the Australia release [https://www.servicenow.com/docs/r/pt-BR/release-notes/rn-learn-landing-page.html](https://www.servicenow.com/docs/r/pt-BR/release-notes/rn-learn-landing-page.html) [[4]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) [[5]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) [[8]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) [[28]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) [[29]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) Life-cycle terms [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cyle-terms.html?contentId=EjXcIbJ12DS0dl8FVDWRRg) [[6]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-lifecycle-hardware.html) Tangible/physical life cycle [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-lifecycle-hardware.html](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-lifecycle-hardware.html) [[9]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.html?contentId=pqCEWiVx6dheaSNluvD9~g) Life cycle mapping form [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.html?contentId=pqCEWiVx6dheaSNluvD9~g](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-life-cycle-mapping-form.html?contentId=pqCEWiVx6dheaSNluvD9~g) [[11]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/cmdb-asset-CI-IBI-sync-options.html) [[30]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/cmdb-asset-CI-IBI-sync-options.html) Syncing life-cycle values [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/cmdb-asset-CI-IBI-sync-options.html](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/cmdb-asset-CI-IBI-sync-options.html) [[15]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-enable.html) CSDM plugin [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-enable.html](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-enable.html) [[16]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) [[20]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) [[31]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) CSDM and CMDB Data Foundations Dashboards [https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/csdm-cmdb-foundations-dashboards.html) [[17]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-datafdn-dash-crawl-tab.html?contentId=lWpo3ZNZwWFgddbZwMELjA) [[26]](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-datafdn-dash-crawl-tab.html?contentId=lWpo3ZNZwWFgddbZwMELjA) Crawl tab on the dashboard [https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-datafdn-dash-crawl-tab.html?contentId=lWpo3ZNZwWFgddbZwMELjA](https://www.servicenow.com/docs/r/servicenow-platform/common-service-data-model-csdm/csdm-datafdn-dash-crawl-tab.html?contentId=lWpo3ZNZwWFgddbZwMELjA) [[19]](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/cmdb-data-foundations-dashboard.html?contentId=W3jznFFdpcXU5nbjXnCNqQ) CMDB Data Foundations dashboard [https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/cmdb-data-foundations-dashboard.html?contentId=W3jznFFdpcXU5nbjXnCNqQ](https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/cmdb-data-foundations-dashboard.html?contentId=W3jznFFdpcXU5nbjXnCNqQ) [[21]](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) Update to CSDM life cycle [https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw](https://www.servicenow.com/docs/r/servicenow-platform/now-assist-for-configuration-management-database-cmdb/na-cmdb-awf-life-cycle-migration.html?contentId=YZlTs8bu2GTKTUsjpoSDQw) [[22]](https://www.servicenow.com/docs/r/yokohama/api-reference/rest-apis/c_TableAPI.html) Table API [https://www.servicenow.com/docs/r/yokohama/api-reference/rest-apis/c_TableAPI.html](https://www.servicenow.com/docs/r/yokohama/api-reference/rest-apis/c_TableAPI.html) [[23]](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AggregateAPI.html) Aggregate API [https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AggregateAPI.html](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AggregateAPI.html) [[27]](https://www.servicenow.com/docs/r/platform-administration/table-administration-and-data-management/c_DatabaseViews.html?utm_source=chatgpt.com) Work with database views [https://www.servicenow.com/docs/r/platform-administration/table-administration-and-data-management/c_DatabaseViews.html?utm_source=chatgpt.com](https://www.servicenow.com/docs/r/platform-administration/table-administration-and-data-management/c_DatabaseViews.html?utm_source=chatgpt.com)