- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-04-2025 03:10 PM
Here's your question formatted in English for the ServiceNow Community:
Title: User Management During Production to Test Environment Cloning
I'm planning to clone our production environment to a test environment and have a question about the sys_user table handling:
We intend to preserve (not exclude) the sys_user table during cloning, and I have some concerns about existing users:
For existing users like System Admin that exist in both environments with the same Sys ID, will the cloning process overwrite the test environment users or create duplicates?
If duplicates are created, what is the recommended approach to manage these duplicate user records?
Are there any best practices or considerations we should be aware of when preserving the sys_user table during cloning, particularly regarding user management?
Any insights or experiences would be greatly appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-04-2025 05:01 PM - edited ‎06-04-2025 05:03 PM
KB to refer Go Live Best practice ( Tech Support Perspective) Onboarding
KB to refer for Duplicate removal Mass-Deletion and excess data management recommendations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-04-2025 05:01 PM - edited ‎06-04-2025 05:03 PM
KB to refer Go Live Best practice ( Tech Support Perspective) Onboarding
KB to refer for Duplicate removal Mass-Deletion and excess data management recommendations