---
sourceDocument: Zurich ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/servicenow-platform

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Deploying replication configuration

# Deploying a replication configuration from one instance to another in Instance Data Replication {#ariaid-title1}

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

Copy a replication configuration from one instance to another through an update set in Instance Data Replication (IDR).

In IDR, you can capture a snapshot of a replication configuration, including selected fields, filters, or data transformations using the Track in Update Set option, and then
copy it to another instance using an update set.  
Important:  
The Track in Update Set option in IDR is the only supported method for capturing a replication configuration that you want to copy to another instance.

## Key benefits {#copying-replication-configuration__section_lfr_bwp_hyb}

* Save time by defining a replication configuration once and using it as a template for new replication sets on other instances.
* Minimize potential impact to your production instance by developing a replication configuration in your sub-prod instance first.
* Verify a replication configuration in a sub-prod instance before rolling it out to a production instance.
{#copying-replication-configuration__ul_kcm_cwp_hyb}

## Configuration entities {#copying-replication-configuration__section_qhv_ptp_hyb}

The following configuration entities are captured in an active update set when you select the Track in Update Set option.

Entry set
:   An entry set is a bundle of replication entries (like a replication set), that doesn't contain any instance-specific metadata like the Producer ID. A new Producer ID is used in the target instance when you create a
    producer replication set based on an entry set.  
    Replication options that are tracked in an entry set and their status (active or inactive) include:

    * Bi-directional replication
    * Discrete value mapping
    {#copying-replication-configuration__ul_tnf_2jb_hwb}

Replication entries
:   A replication entry contains configuration settings for each table that you want to replicate. Replication entries are either outbound or inbound.

    * Outbound entries from a producer instance contain the source table, filter, fields you want to replicate, and data transformation settings.
    * Inbound entries from a consumer instance include the target table, the option to run business rules after replication, and data transformation settings.
    {#copying-replication-configuration__ul_yt2_lj1_hwb}

## Viewing an entry set and replication entries {#copying-replication-configuration__section_uxv_n5p_hyb}

When you create a replication set, a new record is added to the Entry Sets \[idr_entry_set\] table. New records are added to the Replication Entries \[idr_replication_entry\] table for each outbound entry that you add to the
replication set.

After selecting Track in Update Set, you can view the entry set and its replication entries in the current update set by navigating to AllSystem Update SetsLocal Update Sets, selecting the update set, and then viewing the Customer Updates tab.
* **[Deploy a replication configuration through an update set in Instance Data Replication](https://www.servicenow.com/docs/gMMplxtqwpqot2T7zymbZw)**   
  Export a replication configuration from one instance and import it on another instance through an update set in Instance Data Replication (IDR).

**Related concepts**   

* [Comparing replicated data between instances in Instance Data Replication](https://www.servicenow.com/docs/ZwBxZE8EjVPFz7VN4nDp_g "Find missing or mismatched records by comparing replication data between instances in Instance Data Replication (IDR).")
* [Cloning options with Instance Data Replication](https://www.servicenow.com/docs/aWVqawl2PQx1R2Hy5XgOmA "Ensure that certain tables are preserved or excluded to clone your database from one instance to another successfully with Instance Data Replication (IDR).")
* [Monitoring replication status in Instance Data Replication](https://www.servicenow.com/docs/TXavyliYESfALYlb8NlXxA "Monitor the status of active producer and consumer replication sets, scheduled jobs, seeding requests, license usage, or scheduled replication through the Instance Data Replication (IDR) Monitoring Dashboard.")
* [Monitoring queues in Instance Data Replication](https://www.servicenow.com/docs/QATLHd6QGZANqK07upTqqA "Monitor the replication record queue, message produced queue, message consumed queue, and the messages processed for all replications sets through the Instance Data Replication (IDR) Queue Dashboard.")
* [Avoiding insert and update errors in Instance Data Replication](https://www.servicenow.com/docs/9jyxlc_h6j8A0f5itHT7Dg "You can avoid insert and update failures in Instance Data Replication (IDR) by specifying a class name filter in the producer replication set.")  
**Related tasks**   

* [Manage consumer access to replication data in Instance Data Replication](https://www.servicenow.com/docs/XOfuOuuug2GyvUFGjyMMpw "Approve a consumer's request to access replication data in Instance Data Replication (IDR).")  
**Related reference**   

* [Resolving data replication errors in Instance Data Replication](https://www.servicenow.com/docs/D6N4Ub9HnNCj5jQsdrOrmw "Resolve errors and monitor the status of Instance Data Replication (IDR) replication sets.")

*[\>]: and then