How Does Virima’s ServiceNow CMDB Sync Work? A Step-by-Step Guide
TLDR
- Virima discovers IT assets across on-premises, cloud, and hybrid environments and populates its own CMDB with detailed CI data
- CI data maps to ServiceNow tables through configurable, per-class mapping profiles before any data moves
- Sync status tracking ensures each CI moves to ServiceNow only when needed, preventing duplicate record creation
- Administrators can manage, clone, reset, or disable individual mappings without rebuilding configurations from scratch
- Picklist property sync aligns Virima attribute values with ServiceNow dropdown fields, so data lands cleanly
Overview: How Virima Connects to ServiceNow
Virima functions as a discovery and CMDB enrichment layer that feeds CI data into ServiceNow. Rather than replacing ServiceNow ITSM processes, Virima enriches the CMDB servicenow with accurate, detailed CI data collected through its own discovery engine. The integration is bidirectional in awareness: Virima tracks what has been synced, and ServiceNow receives only clean, mapped data that conforms to its table and field structure.
The workflow follows a clear sequence: discover, populate, map, push, track, and maintain. Each step is explained below.
Step 1: How Virima Discovers and Populates Your CMDB
Virima’s discovery engine scans IT environments through a combination of agentless network-based scanning and optional lightweight agents. It identifies configuration items across physical servers, virtual machines, network infrastructure, storage systems, cloud workloads, and installed software.
Each discovered device populates Virima’s CMDB as a CI record with detailed attribute data: hostname, IP addresses, operating system, hardware specifications, installed software, running services, SSL certificates, and network relationships. Virima supports discovery across AWS, Azure, cloud, and on-premises environments, and edge infrastructure.
Supported CI data types include:
- Servers (physical and virtual)
- Network devices (switches, routers, firewalls)
- Storage arrays
- Cloud computing and managed services
- Installed software and software suites
- Certificates and endpoints
This initial discovery pass builds a rich, source-accurate CMDB within Virima before any data moves to ServiceNow, ensuring that only validated CI data enters the integration pipeline.
Step 2: How Virima Maps CI Data to ServiceNow Tables
Before any CI data moves to ServiceNow, it passes through a mapping configuration that defines which Virima fields correspond to which ServiceNow CI class tables and columns.
Each CI class, such as Windows servers, Linux servers, network devices, or storage controllers, gets its own mapping profile. Within each profile, individual field mappings connect Virima attributes to ServiceNow fields. For example, Virima’s “OS Version” field maps to the os_version column in the cmdb_ci_computer table.
Administrators can enable or disable individual field mappings within a profile, clone an existing profile for a similar CI class, or reset a profile to its default configuration. This granular control prevents mapping drift, where a series of incremental changes accumulates into a configuration that no longer reflects intended behavior.
Mapping profiles define the full scope of what ServiceNow receives from each CI class — nothing passes through without a configured mapping rule.
Step 3: How Virima Pushes CI Records to ServiceNow
Once mapping profiles are in place, Virima pushes CI records to ServiceNow through its integration layer using the ServiceNow REST API to create or update CI records in the appropriate class tables.
For each CI, Virima constructs a payload from the mapped field values and submits it to ServiceNow. ServiceNow’s IRE (Identification and Reconciliation Engine) receives the payload, and either creates a new CI record or updates an existing one, depending on whether a matching CI already exists based on identifier fields like serial number, IP address, or hostname.
The sync runs on a configurable schedule (nightly, hourly, or custom interval) or triggers immediately after a discovery cycle completes. Both full and incremental sync modes are available per deployment.
Step 4: How Sync Status Is Tracked to Prevent Duplicates
Virima maintains a per-CI sync status record for every CI in its database. The sync status tracks whether each CI has been successfully pushed to ServiceNow and whether any subsequent attribute changes require an update sync.
The sync status states are:
- Not synced: CI exists in Virima’s CMDB but has not been pushed to ServiceNow
- Synced: CI has been successfully pushed and confirmed in ServiceNow
- Pending update: CI attributes have changed since last sync; an update push is queued
This status model ensures that already-synced, unchanged CIs do not re-enter the push queue on subsequent sync cycles. The result: no redundant re-push operations that could trigger duplicate record creation in ServiceNow.
Virima 6.1.1 introduced improved sync status visibility, making per-CI sync states visible directly from the Virima interface so administrators can audit and troubleshoot sync behavior without querying the ServiceNow API directly.
Step 5: How to Manage and Update ServiceNow Mappings
Mapping management in Virima is available through the ServiceNow integration configuration panel. Administrators access the full list of CI class mapping profiles and can:
- Enable or disable individual field mappings within a profile without deleting them
- Edit field-level mappings to adjust source-to-destination field relationships
- Add new field mappings as ServiceNow table schemas evolve
- Review mapping coverage to identify unmapped fields that may leave ServiceNow CI records incomplete
Changes to mapping profiles take effect on the next sync cycle unless a manual sync is triggered immediately. This allows administrators to validate mapping changes in staging before applying them to production sync runs.
Step 6: How to Reset or Clone Mapping Configurations
Virima supports two operations that simplify mapping maintenance at scale:
Clone: Copy an existing CI class mapping profile to create a new profile for a related CI class. For example, cloning a Windows server profile to create a Linux server profile preserves the common field mappings (hostname, IP, OS) while allowing targeted adjustments specific to the new class (kernel version, package management data). Clone operations reduce configuration errors compared to building a new profile from scratch.
Reset to Default: Restore a mapping profile to Virima’s out-of-box configuration for that CI class. This is useful after a series of experimental mapping changes, after a ServiceNow upgrade that changes table structure, or when an administrator inherits a misconfigured integration. Both operations preserve the underlying CI data in Virima and in ServiceNow — they affect only the mapping rules applied on subsequent sync cycles.
Step 7: How Picklist Properties Sync Between Virima and ServiceNow
ServiceNow uses picklist fields for many standard CI attributes, including operating system type, hardware category, and deployment status. Picklist fields only accept values that match a predefined option list in ServiceNow. If Virima pushes a value not in that list, the field lands blank or triggers a reconciliation warning — silently degrading data quality without triggering an error.
Virima’s picklist property sync feature maintains a translation layer between Virima’s internal attribute values and the corresponding ServiceNow picklist options. When Virima discovers a device running “Windows Server 2022 Datacenter,” the translation layer maps that to the exact picklist option text that ServiceNow expects for that field.
When ServiceNow’s picklist options change after a platform upgrade or configuration update, administrators trigger a metadata refresh in Virima to pull the current option lists and update the translation mappings accordingly. This routine refresh process prevents silent data quality degradation from mismatched picklist values.
Summary: Virima to ServiceNow CMDB Sync at a Glance
Virima’s ServiceNow integration keeps CI data flowing accurately between systems, ensuring the CMDB in servicenow remains accurate, without manual intervention and without accumulating the sync errors that degrade CMDB health over time.
Step | What Happens |
1. Discovery | Virima scans and populates its CMDB with detailed CI data from all asset types |
2. Mapping | CI attributes map to ServiceNow class tables and field columns via per-class profiles |
3. Push | Mapped CI records sync to ServiceNow via REST API; IRE reconciles against existing records |
4. Status Tracking | Per-CI sync status prevents redundant re-pushes and duplicate record creation |
5. Mapping Management | Field mappings can be toggled, edited, or extended without rebuilding profiles |
6. Clone / Reset | Profiles can be cloned for new CI classes or reset to out-of-box defaults |
7. Picklist Sync | Attribute values translate to ServiceNow picklist options for clean data landing |
Ready to Connect Virima to Your ServiceNow Instance?
Virima’s ServiceNow integration works out of the box with ServiceNow ITSM and ITOM environments. Virima’s ServiceNow integration works out of the box with ServiceNow ITSM and ITOM environments. With configurable mapping profiles, per-CI sync status tracking, and built-in picklist translation, it gives IT teams the control they need to maintain an accurate, duplicate-free ServiceNow CMDB.
Schedule a Demo at virima.com
Sources: LogicMonitor – ServiceNow CMDB Integration Overview | ServiceNow Community – Foundation Data Synch and CMDB Collaboration | Virima – ServiceNow CMDB Governance Best Practices
