> ## 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 – Clone Data Between Instances

# The following article explains how to clone data between two ServiceNow instances using ConfigBot


### **Step 1: Log in to ConfigBot**

* Enter your username and password on the login screen and click **Submit** to access your ConfigBot workspace

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1kov5fe.png)

### **Step 2: Select the Module to Clone Data**

From the ConfigBot dashboard, navigate to the module whose data you want to clone—for example, **Notifications**.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1a0rq0j.png)

### **Step 3: Create a New Iteration**

Click the **Add Iteration** button.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_19mzrtv.png)

In the form that appears, enter the following details:

* **Iteration Number**
* **Workspace** – Select the workspace where the iteration will be created
* **Host Address** – Enter the instance URL
* **Instance Type** – Choose the source instance type
* **Company ID**
* **Username**
* **Description** – Add any relevant details about the iteration

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_vwq7y0.png)
Once complete, click **Submit** to create the iteration.

### **Step 4: Prepare Configuration Data**

After the iteration is created, open the **Workbook** and navigate to the **Config** sheet.

Within the Config sheet:

* Select **Fetch by Query** from the dropdown.
* Copy any desired **query** from your ServiceNow instance to fetch specific records (e.g., notifications).

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_v9nzdf.png)
Save and close the workbook.

### **Step 5: Generate Workbook (Source Data Extraction)**

Return to your iteration and click the **Hamburger Menu** → **Generate Workbook**.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_18kzilk.png)


In the pop-up window:

* Enter your **ServiceNow password**
* Add any **execution notes** (optional)
* Select the **Select All** checkbox
* Click **Confirm and Start** to begin the process

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_x3fvh9.png)


This extracts the relevant data from the source instance.

### **Step 6: Review Extracted Data**

Once processing is complete, open the generated workbook and navigate to the **Notifications** sheet.

Here, you’ll see all the notification records fetched from your source instance.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_14dxub1.png)


### **Step 7: Clone Workbook**

Return to your **Workspace** and click the **Clone** option.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_2xp1fu.png)


In the Clone form:

* Select the **Iteration Number**
* Choose the **Instance Type**
* Select the **Cloning Method** (based on your use case)
* Click **Confirm and Clone**

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1tq2gxi.png)


This creates a cloned workbook ready for migration.
 
### **Step 8: Prepare Data for Migration**

Open the cloned workbook and navigate to the **Notifications** sheet.

Before starting migration:

* Remove the **Processing Record IDs** of the notifications you want to migrate.
* Set the **Processing Status** to **Pending** for each record to be transferred.
* Save and close the workbook.

 ![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_16pj9i3.png)


### **Step 9: Update Target Instance Details**

Click the **Edit Iteration** button in ConfigBot.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_ab8zwr.png)


 Update the following fields for the target instance:

* **Host Address**
* **Company ID**
* **Description**

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1fnj7s.png)


* Click **Submit** to save the changes.

You can now see the updated iteration with the new instance details.

### **Step 10: Start Configuration (Data Migration)**

Return to ConfigBot and click the **Hamburger Menu** → **Start Configuration**.

![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_fau9u5.png)


In the pop-up window:

* Add any **notes**
* Enter your **ServiceNow password**
* Select the **Notifications** checkbox
* Click **Confirm and Start**

This initiates the migration process to the target instance.
 
![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1vrp0x2.png)


### **Step 12: Validate the Migration**

After processing is completed:

* Open the workbook and go to the **Notifications** sheet.
* Fields successfully migrated will be **highlighted in green**.
* The **Processing Status** column will show **Processed** for completed items.


![](https://storage.crisp.chat/users/helpdesk/website/-/4/3/b/7/43b7e9fbd033000/image_1pe5l1.png)


ConfigBot’s **Clone Data Between Instances** feature provides a fast, reliable, and secure way to migrate data between ServiceNow environments.

Instead of manually exporting and importing records, you can manage the entire process through a few simple clicks—ensuring data consistency, saving time, and minimizing the risk of errors.

Thank you!