---
sourceDocument: Australia Service Exchange
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/service-exchange

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Service Exchange

ft:clusterId :

    - sebrdg

bundleId :

    - sebrdg

workflow :

    - Customer and Industry


---

# Preservers and exclusions tables

# List of preservers and exclusions tables for cloning {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of List of Preservers and Exclusions Tables for Cloning

When installing Service Exchange and performing cloning operations in ServiceNow, certain tables must be preserved or excluded to maintain connectivity and data integrity on the target instance.
Using the default system clone profile may not preserve all necessary Service Exchange table data.
Therefore, ServiceNow customers must create and configure a custom clone profile to ensure key tables are handled correctly during cloning.
Show full answer Show less  
This process involves carefully managing which tables are included in the **Preservers** and **Exclusions** lists within the clone profile to control how data is retained or replaced after cloning.

## How Cloning Affects Service Exchange Tables

The clone profile's Preservers and Exclusions lists determine the fate of table data on the target instance after cloning, as follows:

* **Table in both Preservers and Exclusions:** Existing target data is preserved; no source records are copied over.
* **Table in Preservers only:** Existing target data is retained and source records are added; no overwriting occurs.
* **Table in Exclusions only:** Existing target data is discarded and no source records are copied, leaving the table empty.
* **Table in neither list:** Target table data is fully replaced by source instance data.

## Configuring a Custom Clone Profile for Service Exchange

To maintain Service Exchange connectivity after cloning, customers must:

* Create a custom clone profile via **All \> System Clone \> Clone Profiles**.
* Remove the **Remote Process Sync Disable Records** script from the Cleanup scripts related list.
* Ensure all required Service Exchange tables are correctly listed in the Preservers and Exclusions lists according to ServiceNow specifications.
* Reestablish connections and activate Capture Definitions on the target instance post-clone.

## Key Service Exchange Tables to Include

ServiceNow provides specific lists of tables that must be preserved or excluded for Service Exchange functionality. These lists cover tables related to global settings, Foundation Data Sync, Provider and Consumer data, Health and Error tracking, Transport and Remote Process Sync, and Employee Profiles.

Examples of important tables include:

* **Preservers:** `cataloguipolicy`, `ihsynccapturedefinition`, `snsbservicebridgesettings`, `snfdsproofferingitem`, `snsbhealthconnectionstats`
* **Exclusions:** `ihsynccapturedefinition`, `scantask`, `snsberror`, `snfdsconsubscriptionitem`

It is critical to add any missing Service Exchange tables to these lists and remove any unrelated tables to prevent data loss or connectivity issues.

## Practical Implications for ServiceNow Customers

By correctly configuring the clone profile's preservers and exclusions lists for Service Exchange tables, customers ensure:

* Essential connection and configuration data remain intact on the target instance after cloning.
* Accurate synchronization of entitlement, offering, and subscription records without overwriting critical target data.
* Error and temporary data tables are cleared appropriately to avoid carrying over irrelevant or stale data.
* Seamless reestablishment of Service Exchange connections and workflows post-clone.

Customers should carefully follow these guidelines to avoid disruption of Service Exchange functionality and to maintain data integrity during clone operations.  
When installing Service Exchange, certain tables must be preserved or excluded to maintain connectivity after a clone.
If the default system profile is used, some of the Service Exchange table data isn't preserved. To address this issue, you must create a custom clone profile with specific settings required for Service Exchange. Navigate to AllSystem CloneClone Profiles and select New to create a custom profile. For more details on clone profiles, see [Create a custom clone profile](https://www.servicenow.com/docs/access?context=configure-clone-profile&version=australia&pubname=australia-platform-administration&ft:locale=en-US). In this profile, you must:

* Remove the Remote Process Sync Disable Records script from the Cleanup scripts related list,
* Validate if the following Service Exchange tables are included in the custom profile.

{#service-bridge-v2-cloning__ul_unv_v3w_dcc}  
Note:  
After a clone, you must reestablish the connection and activate the Capture Definitions. See [Reestablish connection after a clone for a provider](https://www.servicenow.com/docs/3s5MdOAk3eUGZ~JJNw2XtQ "After you clone your instance, you must reestablish the connection between the provider and consumer instances.") and [Reestablish connection after a clone for a consumer](https://www.servicenow.com/docs/JtGDwQFEpM8De3uDRMWXEA "After you clone your instance, you must reestablish the connection between the consumer and provider instances.").

## Service Exchange tables to preserve and exclude {#service-bridge-v2-cloning__section_c1s_nlb_1xb}

The following scenarios describe how clone operations affect table data based on table configuration in the preservers and the exclusions tables list.
{#service-bridge-v2-cloning__table_h22_st3_y3c__entry__3}

| Preservers tables | Exclusions tables | Result on target instance |
|-|-|-|
| Included | Included | Target table retains existing data. The system preserves existing records and copies no records from the source. |
| Included | Not included | Target table retains existing records and receives additional records from the source table. The system does not overwrite existing records. |
| Not included | Included | Target table is empty after the clone. The system discards existing target records and copies no records from the source. |
| Not included | Not included | Target table contains only source table data. The system replaces all pre-existing target records with records from the source. |
[Table 1. Clone operation results by table configuration]

{#service-bridge-v2-cloning__table_h22_st3_y3c}

Update the Clone Profile Preservers and Exclusions lists to include only the Service Exchange tables specified in the following preservers and exclusions tables. Add any missing tables from the specified lists and remove any Service Exchange tables that are not included in these lists.
{#service-bridge-v2-cloning__table_rsh_4jy_wgc__entry__3}

|   | Preservers table | Exclusions table |
|-|-|-|
| Global | * catalog_ui_policy * catalog_ui_policy_action * clone_data_exclude * clone_data_preserver * clone_profile_exclusions * clone_profile_preservers * ih_sync_capture_definition * ih_sync_definition * ih_sync_inbound_definition * ih_sync_outbound_definition * ih_sync_process_event * ih_sync_remote_system * item_option_new * sc_cat_item_catalog * sc_cat_item_category * sc_cat_item_user_criteria_mtom * sc_cat_item_user_criteria_no_mtom * sc_category * scan_finding * scan_task * sn_sb_con_entitlement * sn_sb_error * sn_sb_known_error_code * sn_sb_con_persona_group * sn_sb_con_provider_connection * sn_sb_con_provider_task * sn_sb_release * sn_sb_remote_script_approval * sn_sb_rps_connection * sn_sb_service_bridge_settings * sn_sb_transform_line * sn_transport_queue * sn_fds_pro_consumer_criteria * sn_fds_pro_inbound_offering_item * sn_fds_pro_offering_item * sn_fds_con_outbound_offering * sn_fds_con_outbound_subscription {#service-bridge-v2-cloning__ul_l4z_s5z_wgc} | * ih_sync_capture_definition * ih_sync_definition * ih_sync_inbound_definition * ih_sync_outbound_definition * ih_sync_process_event * ih_sync_remote_system * scan_finding * scan_task * sn_sb_error * sn_sb_pro_persona * sn_sb_remote_task * sn_sb_rps_connection * sn_sb_service_bridge_settings * sn_sb_transform_line * sn_fds_pro_consumer_criteria * sn_fds_pro_inbound_offering_item * sn_fds_pro_inbound_subscription * sn_fds_pro_offering_item * sn_fds_con_m2m_company_offering * sn_fds_con_outbound_offering_item * sn_fds_con_outbound_subscription {#service-bridge-v2-cloning__ul_mdb_rtv_chc} |
| Base | * sn_sb_authorized_user * sn_sb_error * sn_sb_identity * sn_sb_known_error_code * sn_sb_provider_task * sn_sb_release * sn_sb_remote_script_approval * sn_sb_remote_task * sn_sb_scratchpad * sn_sb_service_bridge_settings * sn_sb_transform_line {#service-bridge-v2-cloning__ul_m1z_lvz_wgc} | * sn_sb_authorized_user * sn_sb_connection * sn_sb_entitlement * sn_sb_error * sn_sb_identity * sn_sb_provider_task * sn_sb_remote_record_producer * sn_sb_remote_script_approval * sn_sb_remote_task * sn_sb_scratchpad * sn_sb_service_bridge_settings * sn_sb_transform_line {#service-bridge-v2-cloning__ul_itv_xtv_chc} |
| Provider | * sn_sb_pro_authorized_user * sn_sb_pro_consumer_connection * sn_sb_pro_entitlement * sn_sb_pro_provider * sn_sb_pro_provider_task * sn_sb_pro_registration * sn_sb_pro_remote_choice_definition * sn_sb_pro_remote_record_producer * sn_sb_pro_remote_service * sn_sb_pro_remote_task * sn_sb_pro_remote_task_variable * sn_sb_pro_service_bridge_settings * sn_sb_pro_transform {#service-bridge-v2-cloning__ul_bkt_pvz_wgc} | * sn_sb_pro_inbound_field * sn_sb_pro_outbound_field * sn_sb_pro_provider * sn_sb_pro_registration * sn_sb_pro_remote_record_producer_consumer_criteria * sn_sb_pro_remote_task_def * sn_sb_pro_remote_task_def_consumer_criteria * sn_sb_pro_remote_task_variable * sn_sb_pro_transform {#service-bridge-v2-cloning__ul_bbd_d5v_chc} |
| Consumer | * sn_sb_con_authorized_user * sn_sb_con_consumer * sn_sb_con_entitlement * sn_sb_con_inbound_field * sn_sb_con_outbound_field * sn_sb_con_provider_task * sn_sb_con_remote_record_producer * sn_sb_con_remote_task * sn_sb_con_remote_task_def * sn_sb_con_remote_task_variable * sn_sb_con_service_bridge_settings * sn_sb_con_transform {#service-bridge-v2-cloning__ul_b4t_2hm_xgc} | * sn_sb_con_consumer * sn_sb_con_inbound_field * sn_sb_con_outbound_field * sn_sb_con_persona * sn_sb_con_remote_task_def * sn_sb_con_remote_task_variable * sn_sb_con_transform {#service-bridge-v2-cloning__ul_b1g_jxv_chc} |
| Remote Process Sync Transport | sn_sb_rps_connection (Provider only) | sn_sb_rps_connection (Provider only) |
| Transporter | * sn_transport_profile\* * sn_transport_queue\* {#service-bridge-v2-cloning__ul_wwf_jdd_dhc} | N/a |
| Employee Profile | * user_criteria * sys_alias * sys_user * sys_user_has_role {#service-bridge-v2-cloning__ul_mmk_2br_yhc} | sys_alias |
| Foundation Data Sync | * sn_fds_data_processing_queue * sn_fds_offering * sn_fds_offering_item * sn_fds_request * sn_fds_subscription * sn_fds_subscription_item {#service-bridge-v2-cloning__ul_qfg_dss_g3c} | * sn_fds_data_processing_queue * sn_fds_offering_item * sn_fds_subscription * sn_fds_subscription_item {#service-bridge-v2-cloning__ul_idf_4ct_g3c} |
| Foundation Data Sync for Providers | * sn_fds_pro_inbound_offering_request * sn_fds_pro_offering * sn_fds_pro_offering_request {#service-bridge-v2-cloning__ul_zbw_hss_g3c} | * sn_fds_pro_inbound_offering * sn_fds_pro_inbound_offering_request * sn_fds_pro_inbound_subscription_item * sn_fds_pro_offering * sn_fds_pro_subscription * sn_fds_pro_subscription_item {#service-bridge-v2-cloning__ul_dqd_qct_g3c} |
| Foundation Data Sync for Consumers | * sn_fds_con_offering * sn_fds_con_offering_item * sn_fds_con_offering_request * sn_fds_con_outbound_offering_request * sn_fds_con_subscription * sn_fds_con_subscription_item {#service-bridge-v2-cloning__ul_vqg_k5s_g3c} | * sn_fds_con_offering_item * sn_fds_con_subscription * sn_fds_con_subscription_item {#service-bridge-v2-cloning__ul_d51_r2t_g3c} |
| Health | * sn_sb_issue * sn_sb_health_connection_stats * sn_sb_health_issue {#service-bridge-v2-cloning__ul_h3m_jlz_g3c} | * sn_sb_issue * sn_sb_health_connection_stats * sn_sb_health_issue {#service-bridge-v2-cloning__ul_vzq_nlz_g3c} |
[Table 2. Preservers or Exclusions table]

{#service-bridge-v2-cloning__table_rsh_4jy_wgc}

"\*" - Applicable for both provider and consumer.  
The following scenarios describe how clone operations affect table data based on table configuration in the Clone profile preservers list and the Exclude tables list.

The following examples use tables from this page to illustrate each scenario:

sn_sb_service_bridge_settings (included in both lists): The system preserves connection settings you configured on the target instance after the clone. Settings from the source instance do not overwrite
them.

sn_sb_con_entitlement (included in Clone profile preservers only): The target instance retains existing entitlement records and receives additional entitlement records from the source instance.

sn_sb_error (included in Exclude tables only): The error records table is empty on the target instance after the clone. The system discards error records that existed on the target and copies none from the
source.

sn_fds_offering (not included in either list): The system replaces the target table with source data. Records that existed on the target instance before the clone are replaced by source instance records.

*[\>]: and then