SuggestBestApproach to Import CMDB Data & Relationships from Third‑Party Tool without ITOM/Discovery

Mani60
Tera Contributor

2 hours ago

Hi All,

We are currently working on a CMDB implementation project in ServiceNow and would appreciate your guidance on the questions below. Could you please help us with this?

1. We need to bring CMDB data from a third-party tool along with its relationships.
2. We are using the ServiceNow ITSM Pro license.
3. We do not have Discovery or ITOM licenses.
4. What is the best approach to ensure CMDB data and relationships are imported correctly into ServiceNow?
5. Please suggest the best approach for Application Services and Business Services.



Thanks,
0 Helpfuls
  • 68 Views
1 REPLY 1

SwamyM
Tera Guru

41m ago

Hi @Mani60 ,

 

Why a Static CMDB Is Not a Best Practice in ServiceNow

Maintaining a static CMDB provides limited value and does not effectively support ITSM or other ServiceNow modules. A CMDB should not be treated as a passive data repository; instead, it must represent real-time, trusted configuration data that reflects the actual state of the infrastructure and services.

Recommended CMDB Best Practices

  1. Start with Business and Customer Services

    • Identify your customer-facing and business services.
    • Ensure all CMDB data is aligned to these services, enabling meaningful impact analysis, incident resolution, and change management.

  2. Identify Existing Data Sources

    • Assess where CMDB-related data currently exists (e.g., discovery tools, monitoring systems, asset systems, spreadsheets).
    • Establish these sources as systems of record or systems of engagement as appropriate.

  3. Streamline and Normalize Data

    • Map existing data to ServiceNow CMDB classes and standard fields.
    • Avoid unnecessary customization of CMDB classes and attributes to ensure upgradeability and platform alignment.

  4. Automate CMDB Data Updates

    • Define schedules and mechanisms (Discovery, Service Mapping, integrations) to keep CMDB data updated.
    • Ensure CMDB reflects real infrastructure changes, not manual or outdated snapshots.

  5. Manage Multiple Data Sources with Governance

    • Define Identification and Reconciliation Engine (IRE) rules when ingesting data from multiple sources.
    • Ensure consistent CI identification and prevent duplicates or conflicts.

  6. Monitor and Maintain CMDB Health

    • Define CMDB Health rules for completeness, correctness, and compliance.
    • Regularly review CMDB health dashboards to maintain data quality and trust.

Outcome

By following these practices, the CMDB becomes a living foundation that:

  • Enables effective ITSM processes
  • Improves service visibility and impact analysis
  • Supports automation, analytics, and future platform growth

 

Please click the “Accept Solution” or “Helpful” button, if my response helped you resolve the issue.

 

Thanks,

Swamy



0 Helpfuls