Clone UAT to DEV

[Nithya Devi]

Hi Supporters,

We have planned to clone uat to dev. We have decided to preserve user and their related tables(group,role,has role etc).

1.If do i preserve these tables(user and related tables),do  I expect any mapping(sys_id) issue with the reference table after clone.Because sys_id of user remains same,but the sys_id  of reference table which is mapped to sys_user table will be different after clone.

2.If I have not preserved user related tables.Then dev instance is the copy of uat user records after clone.But we do face some issue with azure ad  password reset.

Could you suggest your idea on this.Which is the  best approach to clone uat to dev.

Thanks in advance.

Regards,

Nithya.

[Ankur Bawiskar]

@Nithya Devi 

My thoughts

-> Use ServiceNow's "Preserve Users and related tables" option during clone to keep user and role data intact. This ensures that user roles, group memberships, and related permissions are preserved, minimizing access issues

-> If user records are not preserved, Azure AD password reset may fail because the user's sys_id or other attributes may not match between UAT and DEV. This can cause authentication and password reset issues

sharing links for help

Clone Basics 

Clone FAQs - Frequently Asked Questions 

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