The following article explains how to use the Compare feature in ConfigBot:

The Compare functionality is used to identify configuration similarities and differences between two ServiceNow instances. When the same record exists in both Instance A and Instance B, matching configurations are highlighted in green, while cells are highlighted in red when the configuration differs between the two instances.

ConfigBot supports two comparison methods:  

• Record sys id: When Record sys id is selected, ConfigBot compares records based on their ServiceNow record sys id 
• Record Key: When Record Key is selected, ConfigBot compares records using the Record Value defined in the respective config sheet column. 

allowing administrators to choose the comparison approach that best fits their validation requirements. 

Step 1: Log in to ConfigBot 

Enter your username and password, then click Submit to access the portal 

Step 2: Select the Module for Comparison 

From the ConfigBot Dashboard, navigate to the module you want to compare. For this demonstration, selecting the Groups module. 

Navigate to the Platform, and click on  Group module tile to open it. 

The Groups module allows you to compare Groups, Group Members, and Group Roles between two ServiceNow instances. 

Step 3: Open Your Workspace 

Navigate to the desired workspace containing the iterations you want to compare. 

Within the workspace, ensure that you have two workbooks generated or backfilled from different ServiceNow instances.

You can identify the respective instances using details such as their Host Address and Company ID. 

Step 4: Review Source Data 

Open Workbook 1 and navigate to the Groups sheet to review the data retrieved from the first ServiceNow instance. 

Then, open Workbook 2 and navigate to the Groups sheet to review the data retrieved from the second ServiceNow instance. 

Step 5: Select the Comparison Method 

For this demonstration, the comparison is configured to use Record Key values. This means ConfigBot will identify matching records based on the configured Record Key for each sheet rather than comparing the records using their sys id.

Record key comparison example:

Record Key comparison is particularly useful when the same logical configuration exists in both instances, but the underlying sys id's differ. 

Navigate to the config sheet and select value in respective columns

Step 6: Run Compare Iterations 

After reviewing the workbooks and determining the appropriate comparison method: 

Return to ConfigBot and click the Hamburger Menu, then select Request Reprocess. 

click the Hamburger Menu icon again, and this time select Compare Iteration. 

In the pop-up window:  

• Select the iteration you want to compare against. 
• Add any execution notes
• Click Confirm and Start to start the execution process. 

ConfigBot will compare the current iteration against the selected iteration according to the selected method.

Step 7: Monitor Comparison Progress 

While the comparison is running, click the Information (ℹ️) icon to monitor the execution status in real time. 

](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image\_4ns7lw.png)

Wait until the execution status changes to Complete before reviewing the comparison results. 

Step 8: Review Comparison Results 

Once the comparison is complete, open the generated workbook and review the Groups sheets. 

The comparison results are presented using color-coded highlights: 

• Green Highlights → Indicate that a matching record was found according to the selected comparison method. 
• Red Highlights → Indicate that no matching record was found according to the selected comparison method. 

The meaning of a match depends on the selected comparison method. In this example, although the first record’s sys id is highlighted in red, indicating that the sys id does not match, the record is identified as a match based on the Group Name because Record Key comparison is enabled.

Further you can also Navigate to the “Compare Summary” Sheet, to find the differences.

This Sheet provides a quick and reliable way to verify data consistency between executions. Instead of manually inspecting records, you can visualize differences and matches in a structured tabular form. 

Understand the Difference Between the Two Methods:

The two comparison methods serve different validation purposes.

• Record sys id focuses on the unique identity of the ServiceNow record. It is appropriate when you want to determine whether the exact same records exist across both instances. 
• Record Key focuses on the logical or business identity of the record. It is useful when the same configuration may exist in both instances but have different sys id's. 

The Compare Data Between Instances functionality in ConfigBot provides a flexible and reliable way to validate configuration consistency across ServiceNow instances.

By supporting both Record sys id and Record Key comparison methods, ConfigBot allows administrators to perform comparisons based either on the unique identity of a record or on its configured business key.  Using the Groups module as an example, administrators can compare Groups by Name, Group Members by Group Name + User Name, and Group Roles by Group Name + Role.

The color-coded results make it easy to identify matching and missing records without manually reviewing data across multiple workbooks.  This approach reduces manual validation effort, improves comparison accuracy, and provides a structured way to identify configuration differences between ServiceNow environments. 

Thank you! 

Updated on: 09/14/2026