List of preservers and exclusions tables for cloning

Release version: Australia

Updated March 12, 2026

3 minutes to read

Summarize

Summarized using AI

Summary of List of Preservers and Exclusions Tables for Cloning

When installing Service Exchange in ServiceNow, maintaining connectivity after a clone requires specific handling of certain tables. The default clone profile does not preserve all necessary Service Exchange table data, so creating a custom clone profile with designated preservers and exclusions is essential. This ensures the correct table data is retained or replaced appropriately during cloning, preventing disruptions in Service Exchange functionality.

Show full answer Show less

Creating and Configuring a Custom Clone Profile

Create a custom clone profile by navigating to All > System Clone > Clone Profiles and selecting New.
Remove the Remote Process Sync Disable Records script from the Cleanup scripts related list in this profile.
Include the specified Service Exchange tables in the profile’s preservers and exclusions lists as detailed below.
After cloning, reestablish the connection and activate Capture Definitions to restore full Service Exchange functionality.

Clone Operation Behavior Based on Table Configuration

The effect of cloning on table data depends on whether tables are included in the preservers and/or exclusions lists:

Preservers Table	Exclusions Table	Result on Target Instance
Included	Included	Target table keeps existing data; no data copied from source.
Included	Not included	Target table retains existing records and adds records from source; no overwrites.
Not included	Included	Target table is emptied; no source data copied.
Not included	Not included	Target table replaced entirely with source data.

Preservers and Exclusions Tables for Service Exchange

Update your clone profile to include only the following Service Exchange tables in the preservers and exclusions lists, removing any that do not appear here. This ensures correct data handling during cloning.

Examples of Key Tables

Preservers tables include: cataloguipolicy, ihsynccapturedefinition, snsbservicebridgesettings, snfdsproofferingitem, snsberror, and others.
Exclusions tables include: clonedataexclude, ihsynccapturedefinition, scantask, snsbremotetask, snfdsconoutboundofferingitem, and others.

Tables are also categorized by functional groups such as Base, Provider, Consumer, Remote Process Sync Transport, Transporter, Employee Profile, Foundation Data Sync, and Health, with specific tables listed for each.

Practical Examples of Clone Table Behavior

Table included in both preservers and exclusions (e.g., snsbservicebridgesettings): Existing target data is preserved, and source data does not overwrite it.
Table included only in preservers (e.g., snsbconentitlement): Target keeps existing data and adds new records from the source without overwriting.
Table included only in exclusions (e.g., snsberror): Target table is emptied and no source data is copied.
Table included in neither list (e.g., snfdsoffering): Target data is fully replaced by source data.

Summary for ServiceNow Customers

To maintain Service Exchange connectivity through cloning, customize your clone profile by properly configuring the preservers and exclusions tables as outlined. This prevents loss of critical data and ensures source and target instances synchronize correctly. After cloning, remember to reestablish connections and activate Capture Definitions to resume normal operation.

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 All > System Clone > Clone Profiles and select New to create a custom profile. For more details on clone profiles, see Create a custom clone profile. 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.

Note:

After a clone, you must reestablish the connection and activate the Capture Definitions. See Reestablish connection after a clone for a provider and Reestablish connection after a clone for a consumer.

Service Exchange tables to preserve and exclude

The following scenarios describe how clone operations affect table data based on table configuration in the preservers and the exclusions tables list.

Table 1. Clone operation results by table configuration
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.

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.

Table 2. Preservers or Exclusions table
	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	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
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	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
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	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
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	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
Remote Process Sync Transport	sn_sb_rps_connection (Provider only)	sn_sb_rps_connection (Provider only)
Transporter	sn_transport_profile* sn_transport_queue*	N/a
Employee Profile	user_criteria sys_alias sys_user sys_user_has_role	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	sn_fds_data_processing_queue sn_fds_offering_item sn_fds_subscription sn_fds_subscription_item
Foundation Data Sync for Providers	sn_fds_pro_inbound_offering_request sn_fds_pro_offering sn_fds_pro_offering_request	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
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	sn_fds_con_offering_item sn_fds_con_subscription sn_fds_con_subscription_item
Health	sn_sb_issue sn_sb_health_connection_stats sn_sb_health_issue	sn_sb_issue sn_sb_health_connection_stats sn_sb_health_issue

"*" - 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.

Preservers and exclusions tables

Australia Service Exchange