What is Clone in ServiceNow?
Clone in ServiceNow is a process of copying a production instance to sub-production instance. The clone requests use the latest backup for the source instance. Cloning data is always constituting Latest Data Movement. It is most recommended process before every major release upgrade. Most Important factors during clone in ServiceNow are Back up Request Process, Preserve Table, Exclude Table, and Clone Review.
Some Well Known Facts of Clone:
- Clone Activity always performed to Sub-Production instance from Production Instance.
- Post Clone immediately we can see the sub-production looks like exact copy.
- Clone activity provides flexibility of Data Preserve and Data Exclusion.
How Does Clone in ServiceNow Works?
Process of Clone in ServiceNow involves creating a copy of an instance’s configurations, data, and settings in a new environment. ServiceNow consulting helps organizations manage this process, ensuring it’s done correctly to maintain system integrity and optimize ServiceNow instance performance.
- Clone generates a file to preserve operational data on the target server. This file contains the data preserved by data preservers.
- It always creates a new database for the target instance (DEV/UAT).
- Restoration of the database schema and data both is taken from the most recent backup to the newly created database by an individual.
- System waits for the data to get copied.
- Post data copying the exclude/preserver functions starts.
- If Exclude options are ticked, sliced tables in the exclude module the data is cleared.
- Then it loads the file for preservers into the target database (overwriting any data from the restore).
So, we can see here, exclusion works first then preserve happens
- Outbound Emails are disabled in the target database. (expected behavior in DEV/UAT)
- Once whole process of 2-3 hours done, target instance again pointers to the newly created database.
- Auto Execution of cleanup script in the target instance gets done.
- Regenerate Text indexes
- Clear scheduled job node connections
- The clone is done, 100% completion message displayed and email received and the instance is accessible for the customer.
- After the clone, always a backup is taken of the old Target database
- Once the backup is done, the old target database is retired.
READ – Streamlining the Workflows and Productivity Commission With ServiceNow
Important Terms of Clone in ServiceNow
1) File Preservers
“File Preservers” is categorical type of data preserver that is designed to ascertain that annexations (files) associated with records are facsimile over when cloning an instance, efficaciously preserving the files during the process of clone in ServiceNow. Essentially, it sanctions you to select which files to keep on the target instance when cloning data from a source instance
2) Exclude/Preserve
Preserve: Entire data which we have in target instance keep it and we should keep it as it is.
Exclude: No Need to bring data to target instance.
3) Cleanup Script
Cleanup script runs on target instance once clone is completed. These are useful scripts for removal or unwanted date in target instance after preserve and clone completed.
4) Scheduled Job Node Connections
Schedule Job is an activity that runs as per the set schedule. ServiceNow platform uses the cluster awareness for execution of the job. The main preference of this feature is to make sure that, single note is available for schedule job execution.
5) Clone Profile
Clone Profile is record that includes predefined target and source instance details. This close profile also constitutes the details of Exclude, Preserves, cleanup scripts. We can create a clone request directly from close profile itself. We can mark the profile as default as well as shown in below image.

6) Clone Request
Once the above set up is done, we need to request the clone. Which can be made from All>Request Clone Module.

7) Clone Review
A “Clone Review” is a process micro examination of target instance once clone activity is completed. We can ensure the settings, preserved and excluded data.
Conclusion
By understanding the process, you can leverage ServiceNow solutions to streamline your IT operations and improve efficiency.
Read more: