--- title: Your ServiceNow Go-Live Happened. Your CMDB Didn't. description: Your implementation delivered incident and change but left the CMDB half-built. The five symptoms, how to measure them, and the rescue sequence that works. image: https://www.apexconfiguration.com/hubfs/AI-Generated%20Media/Images/Corporate%20Project%20Room%20at%20Dawn.png --- [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png "APEX CONFIGURATION GROUP")](https://www.apexconfiguration.com/) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) - [Home](https://www.apexconfiguration.com) - ServiceNow - [ServiceNow CMDB](https://www.apexconfiguration.com/servicenow-cmdb) - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [CMDB Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - Maximising ServiceNow - [CMDB Health Dashboard](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) - [CMDB Dependency Mapping](https://www.apexconfiguration.com/cmdb-relationship-table) - [CMDB Configuration Items](https://www.apexconfiguration.com/cmdb-configuration-items) - [CMDB Workspace](https://www.apexconfiguration.com/cmdb-workspace-servicenow) - [CMDB Best Practice](https://www.apexconfiguration.com/cmdb-best-practices) - [ServiceNow Discovery](https://www.apexconfiguration.com/servicenow-discovery-setup) - [Service Mapping](https://www.apexconfiguration.com/servicenow-service-mapping) - About - [How We Help](https://www.apexconfiguration.com/about-apex) - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - Resources - [Blog](https://www.apexconfiguration.com/blog) - [Contact Us](https://www.apexconfiguration.com/contact-us) [Contact Us](https://www.apexconfiguration.com/contact-us) [tel:+442080588135](tel:+442080588135)[mailto:contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [CMDB](https://www.apexconfiguration.com/blog/tag/cmdb)[ServiceNow](https://www.apexconfiguration.com/blog/tag/servicenow) [CMDB Remediation](https://www.apexconfiguration.com/blog/tag/cmdb-remediation)[ServiceNow Advisory](https://www.apexconfiguration.com/blog/tag/servicenow-advisory) # Your ServiceNow Go-Live Happened. Your CMDB Didn't. [![Iain Moone](https://www.apexconfiguration.com/hs-fs/hubfs/iain-moone.webp?width=40&height=40&name=iain-moone.webp)](https://www.apexconfiguration.com/blog/author/iain-moone) by [Iain Moone](https://www.apexconfiguration.com/blog/author/iain-moone) 7 min read Oct 17, 2026, 9:00:02 AM Last updated on 17 Oct 2026, 09:00:02 If your ServiceNow go-live delivered incident, change and request but left the configuration management database (CMDB) half-built, you're in the position we're most often asked to fix. A ServiceNow CMDB after go-live tends to show the same five symptoms, and you can measure all of them in a couple of weeks from data you already hold. The order you fix them in matters more than the effort you throw at them. Stop new damage first, then repair identification, then extend coverage and wire it into the processes that were meant to use it. ## Key Takeaways - A ServiceNow CMDB after go-live tends to show five symptoms. The configuration item field is optional on incident and change, data was loaded once from spreadsheets, Discovery was piloted and never extended, de-duplication tasks are piling up, and owner and support group are empty. - You can measure all five in about two weeks from data you already hold, using six reports. - Fix them in order. Stop new damage, repair identification and reconciliation, clear the backlog, extend discovery in phases, connect the CMDB to the processes, then put an operating model around it. - The first two steps hold most of the value and are the least visible, so expect to defend them to a sponsor who wants to see discovery running. - A de-duplication backlog is a symptom of identification rules that don't work. At one consulting organisation, more than 50,000 untouched tasks took two analysts eight weeks to clear while an architect fixed the rules behind them. - A rescue needs visible progress within weeks. Track the share of incidents and changes with a real configuration item recorded, and whether new de-duplication tasks have stopped arriving. This article walks through the symptoms, the reports that measure each one, what an ignored backlog really costs, and the rescue sequence we use. ## Five symptoms of a CMDB that missed the go-live These rarely appear alone. Most estates we look at have four of the five. | Symptom | What to measure | What it costs you | | --- | --- | --- | | The configuration item (CI) field is optional on incident and change | Share of incidents and changes in the last quarter with a CI, and how many of those point at a placeholder | No impact analysis, no trend analysis, no route from a failure to its cause | | Data was loaded once from spreadsheets | CIs created by import that have never been updated since | A snapshot of the estate on load day, ageing every week | | Discovery was piloted and never extended | Discovery schedules against the network team's current address plan | Most of the estate described by nobody | | De-duplication tasks are piling up | Open task count and the age of the oldest | Every duplicate splits history, ownership and impact across two records | | Owner and support group are empty | Completeness of those two fields on operational CIs | Assignment by hand, and nobody to certify anything | The first symptom is the one to show a sponsor. If the service desk isn't recording CIs, nothing downstream can work, and the number is easy to understand. ## Measuring the gap from data you already hold You don't need a tool purchase or a new project to size the problem. Six reports will do it. 1. Incidents and changes from the last quarter, grouped by whether the CI field is populated, and by the ten most common CIs used. If one of those is a catch-all record, count it as blank. 2. Every source that has created or updated a CI in the last month, taken from the discovery source attribute and the created-by field. Anything writing directly to CMDB tables, without going through the Identification and Reconciliation Engine, goes on a list. 3. CIs that haven't been updated since they were loaded, grouped by class. 4. The de-duplication task list, grouped by class and by age. 5. Completeness of owner, support group and operational status on operational CIs. 6. The CMDB server count compared with your hypervisor and cloud inventories. Report two usually explains the others. Spreadsheet imports and scripted integrations that bypass the engine are where most duplicates and stale records start. ## What an ignored de-duplication backlog costs De-duplication tasks feel like housekeeping. They're a symptom of identification rules that don't work, and the backlog only grows until the rules are fixed. A consulting organisation with around seven million CIs believed its Identification and Reconciliation Engine was preventing duplicates. It wasn't. Misconfigured identification and reconciliation rules meant the organisation's own discovery scans were creating duplicate CIs, run after run. When the client brought us in, we found more than 50,000 de-duplication tasks that had never been touched. Clearing them took two of our analysts eight weeks, while one of our architects fixed the rules that were generating them. The order mattered. Had the analysts started clearing tasks without the rule fixes, the next scan would have refilled the queue. Fix identification first, then clear the backlog, then watch the queue to confirm new tasks have stopped arriving. ## The rescue sequence for a ServiceNow CMDB after go-live Every rescue we run follows roughly the same order. Skipping ahead is the most common reason internal recovery attempts stall. **1. Stop new damage.** Every source on the list from report two is either rerouted through the Identification and Reconciliation Engine or switched off. New custom classes are frozen until the class model has been reviewed. Nothing new should make the problem worse while you fix it. **2. Repair identification and reconciliation.** Review identification rules for the classes that matter most, starting with servers, network devices and application services. Set reconciliation rules so each attribute has a named authoritative source. Our articles on [identification rules](https://www.apexconfiguration.com/blog/servicenow-identification-rules-how-cmdb-duplicate-prevention-really-works) and [reconciliation rules](https://www.apexconfiguration.com/blog/servicenow-reconciliation-rules-which-source-wins) cover the mechanics. **3. Clear the backlog.** Work the de-duplication tasks by class, highest-impact classes first, and retire stale records rather than deleting them so their history survives. **4. Extend discovery in phases.** One network zone or data centre at a time, with credentials tested and scan windows agreed through change. Phasing keeps each problem small enough to diagnose. **5. Connect the CMDB to the processes.** Make the CI mandatory on change at a defined state, and on incident at resolution. Drive assignment from the CI's support group, so good data saves the service desk time and they have a reason to keep it accurate. **6. Put an operating model around it.** A named configuration manager, a RACI (responsible, accountable, consulted, informed) matrix for each class, and certification campaigns for ownership. Without this, the CMDB degrades back to where it started within a year. Steps one and two are where most of the value sits, and they're the least visible. Expect to defend them to a sponsor who wants to see discovery running. ## Why the implementation stopped where it did It helps to understand how you got here, because it shapes what you ask for next. This is rarely a question of anyone doing a poor job. Go-live dates are usually fixed, and statements of work tend to be written around process: incident, change, request, the portal. CMDB work depends on things a project can't control on its own timetable, such as firewall changes for discovery, credentials from infrastructure teams and owners willing to confirm data. When the date is at risk, the CMDB is the part that can be moved to a later phase without stopping go-live. Later phases often lose their budget once the platform is live. The result is a platform built to use CMDB data, sitting on a CMDB that can't supply it. ## Proving progress to the people who funded go-live A rescue needs visible progress within weeks, or the funding goes elsewhere. Four key performance indicators (KPIs) show it: - Share of incidents and changes with a real CI recorded, trended monthly - Open de-duplication tasks, and new tasks arriving each week - CMDB server count against independent inventories - Share of changes with impacted services calculated from relationships The second one proves the rule fixes worked. If new tasks stop arriving while the backlog falls, identification is holding. ## How Apex helps Our two-week CMDB health baseline tells you which of the five symptoms you have, how severe each one is, and which of your CIs can be trusted today. The output is a scored report you can take to your change advisory board and your sponsor, with the rescue sequence set out against your own findings. Where duplicates and bypassed identification are the main problem, our data quality assessment measures de-duplication, normalisation and reconciliation against weighted critical success factors, KPIs and metrics, and shows where and why they're failing. If you'd rather not staff the recovery yourself, we can run configuration management for you as a managed service once the rescue is complete. You can [book a CMDB diagnostic call](https://www.apexconfiguration.com/cmdb-diagnostic-call) to talk through where your go-live left you, or [book a meeting](https://www.apexconfiguration.com/book-a-meeting) with one of our consultants. ## Frequently asked questions ### Can we fix the CMDB without reimplementing ServiceNow? Yes. A CMDB rescue works within your existing instance. It changes identification and reconciliation rules, integrations, discovery configuration and process settings, and leaves the incident, change and request work that went live in place. ### Should we switch discovery on across the whole estate straight away? Not until identification rules are fixed. Discovery running against broken rules produces duplicates at scale, and you'll spend months clearing them. Repair identification first, then extend discovery one zone at a time. ### How long does a CMDB rescue take? It depends on the estate and on which symptoms you have. The baseline takes two weeks. As one reference point, clearing a backlog of more than 50,000 de-duplication tasks on a seven-million-CI estate took two analysts eight weeks, alongside an architect fixing the rules behind it. ### Why are our de-duplication tasks never cleared? Usually because the team is working the tasks while the identification rules keep generating new ones. The queue never shrinks, and people stop looking at it. Fix the rules, then clear the queue, then monitor the arrival rate. ### Who should own the CMDB once it's been rescued? A named configuration manager with a RACI matrix for each class, and CI owners who certify their records. If that capacity doesn't exist in-house, running configuration management as a managed service is an alternative. *Written by Iain Moone, Apex Configuration Group.* Book a free call to discuss how Apex can help you on your journey to a better CMDB   [![\CMDB Diagnostic Call\](https://hubspot-no-cache-eu1-prod.s3.amazonaws.com/cta/default/147949153/interactive-378363509978.png)](https://www.apexconfiguration.com/hs/cta/wi/redirect?encryptedPayload=AVxigLL56Cqt4UsSkCus7mx%2FgqZOtxOhYU7gx0b7eYkoCX5XF8DMKrS0%2Fuoru5gCEfH%2Fse8eT0TZjipx2fejnfF4S%2FHmXZbH%2FBqL5wm5XcHxt5cogP4KY5CT6u%2FussSCUJ8hpUewyoPHUpMmRkZN3NHkb7PBhosPO3ra2IW8z8NItYK80RtSkFxijJhjMCGyPgkr9FHeuaB1w5SReSjsgARNG7DAdgK%2FGj%2B10yB8L%2BW4ixo%3D&webInteractiveContentId=378363509978&portalId=147949153) - Recent - Topics - Archive Recent ### Recent Topics ### Topics - [ServiceNow (42)](https://www.apexconfiguration.com/blog/tag/servicenow) - [CMDB (30)](https://www.apexconfiguration.com/blog/tag/cmdb) - [CMDB Data Quality (13)](https://www.apexconfiguration.com/blog/tag/cmdb-data-quality) - [Case Studies (8)](https://www.apexconfiguration.com/blog/tag/case-studies) - [Change Management (6)](https://www.apexconfiguration.com/blog/tag/change-management) - [Service Mapping (6)](https://www.apexconfiguration.com/blog/tag/service-mapping) - [ServiceNow Discovery (6)](https://www.apexconfiguration.com/blog/tag/servicenow-discovery) - [Duplicate CIs (5)](https://www.apexconfiguration.com/blog/tag/duplicate-cis) - [IT Governance (5)](https://www.apexconfiguration.com/blog/tag/it-governance) - [Vulnerability Management (5)](https://www.apexconfiguration.com/blog/tag/vulnerability-management) - [CI Ownership (4)](https://www.apexconfiguration.com/blog/tag/ci-ownership) - [Compliance & Audit (4)](https://www.apexconfiguration.com/blog/tag/compliance-audit) - [Incident Management (4)](https://www.apexconfiguration.com/blog/tag/incident-management) - [Service Graph Connectors (4)](https://www.apexconfiguration.com/blog/tag/service-graph-connectors) - [Agentic AI (3)](https://www.apexconfiguration.com/blog/tag/agentic-ai) - [Configuration Management (3)](https://www.apexconfiguration.com/blog/tag/configuration-management) - [Data Model Design (3)](https://www.apexconfiguration.com/blog/tag/data-model-design) - [Enterprise Risk Management (3)](https://www.apexconfiguration.com/blog/tag/enterprise-risk-management) - [IRE (3)](https://www.apexconfiguration.com/blog/tag/ire) - [Problem Management (3)](https://www.apexconfiguration.com/blog/tag/problem-management) - [Broadcast & Media (2)](https://www.apexconfiguration.com/blog/tag/broadcast-media) - [CI Reconciliation (2)](https://www.apexconfiguration.com/blog/tag/ci-reconciliation) - [Cyber Security (2)](https://www.apexconfiguration.com/blog/tag/cyber-security) - [Dependency Views (2)](https://www.apexconfiguration.com/blog/tag/dependency-views) - [IT Cost Optimisation (2)](https://www.apexconfiguration.com/blog/tag/it-cost-optimisation) - [ITOM (2)](https://www.apexconfiguration.com/blog/tag/itom) - [Managed Services (2)](https://www.apexconfiguration.com/blog/tag/managed-services) - [Manufacturing (2)](https://www.apexconfiguration.com/blog/tag/manufacturing) - [CMDB Remediation (1)](https://www.apexconfiguration.com/blog/tag/cmdb-remediation) - [CSDM (1)](https://www.apexconfiguration.com/blog/tag/csdm) - [IT Asset Management (1)](https://www.apexconfiguration.com/blog/tag/it-asset-management) - [Operational Efficiency (1)](https://www.apexconfiguration.com/blog/tag/operational-efficiency) - [ServiceNow Advisory (1)](https://www.apexconfiguration.com/blog/tag/servicenow-advisory) See all Archive ### Archive - [October 2026 (15)](https://www.apexconfiguration.com/blog/archive/2026/10) - [September 2026 (16)](https://www.apexconfiguration.com/blog/archive/2026/09) - [August 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/08) - [July 2026 (4)](https://www.apexconfiguration.com/blog/archive/2026/07) - [June 2026 (3)](https://www.apexconfiguration.com/blog/archive/2026/06) - [May 2026 (2)](https://www.apexconfiguration.com/blog/archive/2026/05) See all ### Subscribe by email Share this [Share on X](https://x.com/intent/post?url=https://www.apexconfiguration.com/blog/your-servicenow-go-live-happened-your-cmdb-didnt&text=Your+ServiceNow+Go-Live+Happened.+Your+CMDB+Didn%27t.) [Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https://www.apexconfiguration.com/blog/your-servicenow-go-live-happened-your-cmdb-didnt&t=Your+ServiceNow+Go-Live+Happened.+Your+CMDB+Didn%27t.) [Share on LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https://www.apexconfiguration.com/blog/your-servicenow-go-live-happened-your-cmdb-didnt&t=Your+ServiceNow+Go-Live+Happened.+Your+CMDB+Didn%27t.) Previous story [← ServiceNow Multi-Source Data: Precedence Starts Before Reconciliation](https://www.apexconfiguration.com/blog/multi-source-data-in-servicenow-why-precedence-starts-before-reconciliation) ![Iain Moone](https://www.apexconfiguration.com/hs-fs/hubfs/iain-moone.webp?width=64&height=64&name=iain-moone.webp) By [Iain Moone](https://www.apexconfiguration.com/blog/author/iain-moone) Before founding Apex Configuration Group, I held senior global roles including Director, Global Head of SACM, and CMDB Architect within complex, regulated, multi-national environments. I help large… [Full profile & credentials →](https://www.apexconfiguration.com/blog/author/iain-moone) ### Get Email Notifications [![APEX CONFIGURATION GROUP](https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png?width=135&height=93&name=ACG-logo.png)](https://www.apexconfiguration.com/) ServiceNow CMDB specialists delivering enterprise-grade implementation, remediation, and managed services. Address: 20 Wenlock Road, London, England, N1 7GU VAT Number: 505 0347 31 Company Number: 15871442 Email: [contact@apexconfiguration.com](mailto:contact@apexconfiguration.com) [Follow Apex Configuration Group on LinkedIn](https://www.linkedin.com/company/apex-configuration-group) Services - [CMDB Health Check](https://www.apexconfiguration.com/cmdb-health-check) - [Design & Implementation](https://www.apexconfiguration.com/cmdb-design-implementation) - [Managed Service](https://www.apexconfiguration.com/managed-cmdb-services) - [Automation & Optimisation](https://www.apexconfiguration.com/cmdb-automation-tools) - [Health Dashboard & Reporting](https://www.apexconfiguration.com/cmdb-health-dashboard-servicenow) Company - [What is a CMDB?](https://www.apexconfiguration.com/what-is-cmdb) - [Benefits](https://www.apexconfiguration.com/benefits-of-cmdb) - [About](https://www.apexconfiguration.com/about-apex) - [Blog](https://www.apexconfiguration.com/blog) Resources - [Contact Us](https://www.apexconfiguration.com/contact-us) - [CMDB Diagnostic Call](https://www.apexconfiguration.com/cmdb-diagnostic-call) - [Book A Meeting](https://www.apexconfiguration.com/book-a-meeting) © 2026 Apex Configuration Group. All rights reserved. ServiceNow is a trademark of ServiceNow, Inc. We are not affiliated with or endorsed by ServiceNow. - [Terms](https://www.apexconfiguration.com/terms) - [Cookies](https://www.apexconfiguration.com/cookie-policy) - [Privacy](https://www.apexconfiguration.com/privacy-policy) ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#organization", "@type" : [ "Organization", "ProfessionalService" ], "address" : { "@type" : "PostalAddress", "addressCountry" : "GB", "addressLocality" : "London", "addressRegion" : "England", "postalCode" : "N1 7GU", "streetAddress" : "20 Wenlock Road" }, "alternateName" : "Apex Configuration Group", "areaServed" : "GB", "contactPoint" : { "@type" : "ContactPoint", "areaServed" : "GB", "availableLanguage" : "en", "contactType" : "customer service", "telephone" : "+44 20 8058 8135" }, "identifier" : { "@type" : "PropertyValue", "propertyID" : "UK Companies House company number", "value" : "15871442" }, "image" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/Configuration-data.webp", "legalName" : "Apex Configuration Group Ltd", "logo" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png", "name" : "Apex Configuration Group Ltd", "sameAs" : [ "https://www.linkedin.com/company/apex-configuration-group", "https://find-and-update.company-information.service.gov.uk/company/15871442", "https://www.crunchbase.com/organization/apex-configuration-group-ltd" ], "telephone" : "+44 20 8058 8135", "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.apexconfiguration.com/#website", "@type" : "WebSite", "inLanguage" : "en-GB", "name" : "Apex Configuration Group", "publisher" : { "@id" : "https://www.apexconfiguration.com/#organization" }, "url" : "https://www.apexconfiguration.com/" } ``` ```json { "@context" : "https://schema.org", "@type" : "WebPage", "description" : "Your implementation delivered incident and change but left the CMDB half-built. The five symptoms, how to measure them, and the rescue sequence that works.", "inLanguage" : "en-GB", "name" : "Your ServiceNow Go-Live Happened. Your CMDB Didn't.", "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" }, "url" : "https://www.apexconfiguration.com/blog/your-servicenow-go-live-happened-your-cmdb-didnt" } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/", "name" : "Home", "position" : 1 }, { "@type" : "ListItem", "item" : "https://www.apexconfiguration.com/blog/your-servicenow-go-live-happened-your-cmdb-didnt", "name" : "Your ServiceNow Go-Live Happened. Your CMDB Didn't.", "position" : 2 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Iain Moone", "sameAs" : [ "https://www.linkedin.com/in/iainmoone/" ], "url" : "https://www.apexconfiguration.com/blog/author/iain-moone" }, "dateModified" : "2026-10-17T08:00:02+0000", "datePublished" : "2026-10-17T08:00:02+0000", "headline" : "Your ServiceNow Go-Live Happened. Your CMDB Didn't.", "image" : [ "https://147949153.fs1.hubspotusercontent-eu1.net/hubfs/147949153/AI-Generated%20Media/Images/Corporate%20Project%20Room%20at%20Dawn.png" ], "mainEntityOfPage" : { "@id" : "https://www.apexconfiguration.com/blog/your-servicenow-go-live-happened-your-cmdb-didnt", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.apexconfiguration.com/hs-fs/hubfs/Act3%20child/images/ACG-logo.png" }, "name" : "Apex Configuration Group Ltd", "url" : "https://www.apexconfiguration.com/" } } ```