---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Exclude a table

# Exclude a table from cloning {#ariaid-title1}

* Release version: Xanadu
* 
* Updated September 10, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Exclude a table to create an empty but usable table on the target
instance.

## Before you begin

Role required: clone_admin

## About this task

Note:  
When using Exclusions (Exclude Tables), the data is removed during the exclusion substage before the node repoint. The data is removed before the instance becomes available to users.
The System CloneExclude Tables module lists the tables that aren't copied during a system clone. On the clone request form, the option "Exclude tables specified in Exclusion List" is on by default. It verifies that the exclusions are processed during a clone. By default, the system excludes certain required tables such as logging, auditing, notifications, workflow contexts, and license usage.  
Note:  
Excluded workflow context data includes records stored in the wf_context table, and in related tables with names starting with a prefix of wf_. This also includes the workflow scheduler table. This helps to prevent the occurrence of workflow timer syncing issues that might take place due to the length of the cloning process if workflow contexts were included.

`sys_db_object` and `sys_db_object.*` can't be added
to the exclusions.

When excluding child tables of the Task table, which use the [table per hierarchy extension model](https://servicenow-prod.fluidtopics.net/wvwxaMuHCt2VXWgWESqj0w "Table flattening stores a hierarchy of related tables as one table in a relational database."), child tables are excluded. You don't need to exclude the parent Task table together with the child table.  
You can use wildcards to exclude several tables from cloning with one entry. For example, `sys_script.*` excludes all tables starting with sys_script.  
Note:  
The wildcard has to include the dot '.' before the asterisk.

To preserve the existing data on the target instance, see [Create a data preserver](https://servicenow-prod.fluidtopics.net/GcyPL5YdVIvWfI9jKd161A#t_CreateADataPreserver "Data preservers maintain specified data on a target instance."). Data on tables that reference the table, such as business rules, isn't excluded. To avoid unexpected results, we (strongly) advise against altering out-of-box preservers.  
To preserve or exclude related tables, you must preserve and exclude all of the following tables. If any of the tables are missed, the customer may not be able to log in to the instance after a clone.

* sys_user
* sys_user_role
* sys_user_group
* sys_user_grmember
* sys_group_has_role
* sys_user_role_contains
* customer_contact (if the Customer Service Management plugin is active)
{#t_ExcludeATableFromCloning__ul_tcc_qkm_z5b}

## Procedure

1. On the source instance, navigate to System CloneExclude Tables.
2. Select New.
3. Enter the table Name.
4. Select Submit.

*[\>]: and then