Need Cloning Guidance

[saint]

Hi Experts,

I’m looking to copy groups from Prod to Dev via cloning. I plan to exclude all other user and group-related tables such as sys_user, sys_user_grmember, sys_user_has_role, sys_group_has_role, etc.

Would cloning only the groups be sufficient, or could this approach cause issues by not including the related tables?

I want to include Prod data for task tables such as Incident, Problem, Change, and Service Request during a clone. What’s the best way to configure the clone to include these specific task tables?

I have Transform Maps and Import Sets in both the global and application scopes for Asset Management integrations and other integrations. When performing a clone, how should I configure it so that these configurations are not affected or broken? What’s the best approach to ensure they remain intact in both global and application scopes?

[Dr Atul G- LNG · Accepted solution]

Hi @saint 

In cloning, two things are important: Preserve and Exclude. These define what you want to keep and what you want to edit or add. In your case, you need to add the tables under Preserve."

Preserve data: 

Data preservers

Sometimes, it is necessary to preserve some data on an instance targeted for cloning. For example, if the target is a MID Server, you must not overwrite the MID Server [ecc_agent] table. Preserved data is stored on the target instance before cloning begins and is restored on the target instance after cloning.

https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/managing-data/con...

Exclude data:

https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/managing-data/tas...

Basically:

Preserve means: keep what data is already there on the target instance, but add to it.

Exclude means: If no preserve, don't even bring data to the target instance, but instead make it empty. Otherwise, if perserved, but excluded, then keep what is there, but don't touch it.

[Rafael Batistot]

Hi @saint 

May you try via Preserve data 

1. Navigate to All > System Clone > Preserve Data.

https://www.servicenow.com/docs/bundle/xanadu-platform-administration/page/administer/managing-data/...

[Dr Atul G- LNG · Accepted solution]

Hi @saint 

In cloning, two things are important: Preserve and Exclude. These define what you want to keep and what you want to edit or add. In your case, you need to add the tables under Preserve."

Preserve data: 

Data preservers

Sometimes, it is necessary to preserve some data on an instance targeted for cloning. For example, if the target is a MID Server, you must not overwrite the MID Server [ecc_agent] table. Preserved data is stored on the target instance before cloning begins and is restored on the target instance after cloning.

https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/managing-data/con...

Exclude data:

https://docs.servicenow.com/bundle/orlando-platform-administration/page/administer/managing-data/tas...

Basically:

Preserve means: keep what data is already there on the target instance, but add to it.

Exclude means: If no preserve, don't even bring data to the target instance, but instead make it empty. Otherwise, if perserved, but excluded, then keep what is there, but don't touch it.

[Chavan AP · Accepted solution]

ServiceNow Clone Configuration Best Practices


1. Cloning Groups Only - Potential Issues
Problems with excluding related tables:

Broken memberships: Groups without sys_user_grmember will have no members
Missing roles: Groups without sys_group_has_role will have no assigned roles
Orphaned references: Other tables referencing these groups may break
Recommended approach:

Include these minimum tables:

- sys_user_group (groups)

- sys_user_grmember (group memberships)  

- sys_group_has_role (group roles)

- sys_user_role (roles themselves)



Alternative: Use Preserve Data option for user-related tables instead of excluding them.





2. Including Specific Task Tables
Clone Configuration:

Tables to Include:

- incident

- problem  

- change_request

- sc_request

- sc_req_item

- sc_task

- task (parent table)



Related tables to consider:

- task_activity (journal entries)

- sys_attachment (attachments)

- sys_audit (audit history if needed)



Best Practice: Use Table Hierarchy option to automatically include child tables.



3. Preserving Transform Maps & Import Sets
Configuration approach:

For Transform Maps:

Preserve Data for:

- sys_transform_map

- sys_transform_entry  

- sys_transform_script

- sys_data_source



For Import Sets:

Preserve Data for:

- sys_import_set_row

- sys_import_set

- All custom import tables (imp_*)



Scope considerations:

Global scope: Maps preserved automatically
Application scope: Use Preserve Data for application tables
Custom applications: Include the entire application scope


Recommended Clone Settings:

Clone Type: Data and Configuration

Options:

  - Preserve Data: sys_transform_*, sys_import_*, sys_data_source

  - Include Applications: [your custom apps]

  - Exclude: sys_user, sys_user_has_role (if not needed)

  - Include: All task tables with hierarchy





Pro Tip: Test clone on a sub-prod instance first to validate configuration before applying to Dev.