ServiceNow Prod-to-Test Clone Process, Clone Exclusions, and Best Practices

[bondita1]

Hi Everyone,

I would like to understand the standard process for cloning data from a Production instance to a Test instance in ServiceNow.

Could someone please explain:

1. The end-to-end clone process and the steps involved.
2. The prerequisites and approvals typically required before initiating a clone.
3. How to configure Clone Exclusions and Data Preservers.
4. Which tables are commonly excluded from cloning and why.
5. Best practices for handling sensitive or personal data during and after the clone process.
6. Any post-clone activities that should be performed.

Any examples, documentation, or practical recommendations would be greatly appreciated.

Thank you 🙂

[Ankur Bawiskar]

@bondita1 

check below

Post-Cloning Checklist 

Clone Basics 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Tanushree Maiti]

Hi @bondita1 

I will suggest you to go through folloing KB and community articles:

KB1214608 Clone Basics 

Administration: Cloning || Knowledge & Troubleshooting Resources

https://www.servicenow.com/community/upgrades-and-patching-forum/best-practices-and-steps-to-clone-a...

[Aditya_hublikar]

Hello @bondita1 ,

You can refer this threads it will help you :

Best practice and step by step clone  

Clone preparation and best practice

Cloning - upgrade

Guidence 

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya

[bondita1]

Hello All,

I have one further query: 

Sometimes, after cloning a production instance to a test instance, sensitive production data is copied as well, such as users' phone numbers, email addresses, or even bank account details.

How can this issue be addressed after the clone is completed? What precautions or best practices can be followed before and after cloning to prevent sensitive data from being exposed in non-production environments? Thanks