> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.configbot.ai/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # ConfigBot for ServiceNow - Upgrade Analysis The **Upgrade Analysis module** automates ServiceNow upgrade impact analysis by identifying how changes introduced in an upcoming release may affect the existing instance. It analyses release changes and validates their presence and usage within the instance, helping administrators and developers identify potential upgrade risks before deployment.  The module supports the following release change types:  * **New**  * **Change**  * **Deprecate**  * **Removed**  It currently analyses the following ServiceNow elements:  * **Tables**  * **Fields**  * **Roles**  * **System Properties**  * **Workspaces**  **Release Change Types:** The Upgrade Analysis module supports **New, Change, Deprecate, and Removed** release changes. For each change type, the module first verifies whether the affected element exists in the target instance. If the element exists, the module performs impact analysis to identify its usage across impacted tables and records. If the element does not exist, the change is marked as **No Impact**. This consistent validation approach ensures that potential upgrade conflicts are identified regardless of the type of release change. The module provides **impact status and direct links to affected records**, enabling teams to quickly review, validate, and remediate potential conflicts.  By automating upgrade impact analysis, the module helps organizations **reduce manual effort,** **identify** **upgrade risks early, improve analysis accuracy, and confidently prepare their ServiceNow instances for upgrades**.  The following article explains how to use the **Upgrade Analysis** module in ConfigBot to perform operations. **Step 1: Log in to** **ConfigBot**  Enter your **username** and **password**, then click Submit to access the portal.   ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1gdl5ct.png) **Step 2: Access the** **Upgrade Analysis** **Module**  From the **Home Screen**, Navigate to **Impact Analysis** and click on the **Upgrade Analysis** module tile  ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_jqp7mq.png) **Step 3: Create New Iteration**  Click the Add Iteration button  ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_14ybwml.png) * Enter the Iteration Number  * Select the Workspace or ADD NEW WORKSPACE  * Enter Host Address  * Choose the Instance Type  * Enter your Company ID and Username  * Add a short Description   ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_w7s9bl.png) Then click **Submit** to create the iteration.    **Automation (Analyse** **Records using** **ConfigBot):**  **Step 1 –** **Open the Sheet**  Open the **Iteration is Created** and navigate to the desired screen to access the required analysis.  ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1j6khdr.png) ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1i6gadm.png) The sheet is **pre-populated by default**, with the status set to **Pending**. The module includes **pre-built screens for ServiceNow applications** to identify potential upgrade impacts. It also provides **release notes** to help users understand the relevant modules and changes.  **Step 2 – Start Execution (Automation)**  **Navigate back to workspace,** click on the hamburger menu icon and select **“Start Configuration”**  ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1xcd2pn.png) **In the pop-up window:**  * Enter your ServiceNow instance password  * Add any execution notes  * Select the checkbox for the desired sheet, or you can also Select all by the checkbox.  ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_8he745.png) Click "**Confirm and Start**" button to start execution.   **Step 3: Review Results**  Once the status shows complete, navigate to logs by clicking on (i) icon, from logs you can see the selected screen has been executed successfully as well. ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1vv922d.png)[](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image\_j79x96.png) **Navigate to Workbook to verify the analysis:** ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1b1zixc.png)[](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image\_4ovpr6.png) You can see that the **Pending** records have been updated to **Processed**, and the sheet now displays the results of the upgrade impact analysis. Navigate to **Column N – “Impact Yes/No”** and **Column O – “Impacted Record Link.”** * **Impact = Yes:** Indicates that the release element exists in the instance and that the module has identified a potential upgrade impact based on its usage or dependency within the instance. * **Impact = No:** Indicates that the release element does not exist in the instance and therefore does not have an identified impact. * **Impacted Record Link:** Provides a direct link to the affected record or configuration, allowing administrators and developers to review the identified impact and take appropriate remediation action. ServiceNow upgrades don’t have to be a source of uncertainty and operational risk. By automating the complex and time-consuming process of upgrade impact analysis, the **Upgrade Analysis module** helps transform release preparation into a structured, accurate, and actionable process. By analyzing critical elements such as **tables, fields, roles, system properties, and workspaces** across **New, Change, Deprecate, and Removed** release types, the module identifies existing elements, evaluates their potential impact, and provides direct links to affected records. This enables administrators and developers to identify and address upgrade risks proactively, helping keep their ServiceNow instance stable, reliable, and ready for the next release.  Thank You!