How to Build a comparison logic to Compare Platform Configurations and customization with OOTB?

[shayanfayaz]

Hi everyone,

I’m currently working on building a logic within our ServiceNow environment. The objective is to assess the current configuration and comparison state of our platform and compare it against the Out-of-the-Box (OOTB) baseline for the current version.

What we’re trying to build:
A comprehensive engine or framework to scan all platform configurations

A comparison layer to detect deviations from OOTB

A structured output showing customizations, overrides, or unused/obsolete items

We’ve explored a few approaches, including leveraging Sys_metadata table and direct comparisons, but we’re stuck with boolean-level outputs (customized vs. not customized), which don't give us the full picture or detailed delta.

Looking for help with:
Has anyone built a more advanced comparison engine? Any references or tooling you’d recommend?

How does ServiceNow internally assess configuration drift vs. OOTB during upgrades or QA cycles?

Are there best practices or utilities to generate structured outputs showing what exactly has changed?

Appreciate any insights or shared experiences that can guide our next steps.

[SANDEEP DUTTA]

Hi @shayanfayaz ,

For that, i think you will have to talk to ServiceNow Account executive and run health check.

As if you want to build something of your own, it will be another set of custom solution.

[Dr Atul G- LNG]

Hi @shayanfayaz 

Practically, there is no direct way to check all the customizations built in the system over a period of time.

Out of the box (OOB), you can still evaluate using Process Documentation and manually note down the changes, but tracking customizations is not straightforward.

In such cases, it's best to reach out to your ServiceNow account executive directly for assistance.