---
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


---

# Set up continuous replication

# Set up continuous replication {#ariaid-title1}

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

Enable near-real time data replication from a producer instance to one or more consumer instances in Instance Data Replication (IDR).

## Before you begin

Verify that the producer and consumer instances belong to the same customer.

Plan your data replication strategy by reviewing the important considerations described in [Preparing for Instance Data Replication](https://www.servicenow.com/docs/A1r31KD0amErbk9_Q9qrzA "Before you set up Instance Data Replication (IDR), analyze the tables and columns in the producer and consumer instances to replicate data successfully.").

Role required: idr_admin or admin

## Procedure

1. On the producer instance, navigate to Instance Data ReplicationProducer Replication Sets.
2. Select New.
3. Enter a name and description for the producer replication set.  
   * The name can only contain alphanumeric characters and hyphens.
   * Avoid using a name that applies only to the producer instance. You must provide the same name in the consumer replication set, so the name shouldn't be producer-specific.
   {#set-up-continuous-replication-idr__ul_ts2_nyv_gdc}
4. **Optional:** Create the producer replication set from a list of outbound entries by selecting Entry set.  
   If you imported an update set from another instance or you created one earlier on your instance, you can choose an existing entry set.
5. Select Submit.  
   The producer replication set is created with an auto-generated producer ID that identifies the producer instance in the system.
6. Specify the tables and columns on the producer instance that you want to replicate.
   1. Select the Outbound Entries related list.
   2. Select New.
   3. On the form, fill in the fields.  
      {#set-up-continuous-replication-idr__table_ty4_pmz_clb__entry__2}

      | Field | Description |
      |-|-|
      | Source Table Name | Name of one of the tables on the producer instance to replicate. For example, SAN Disk \[cmdb_ci_san_disk\]. |
      | Filter | Filter criteria to control the records in the table that the system is replicating. * Use the filter to limit the number of records in your replication set. For example, if the table has an Active field, add a filter condition like \[Active\] \[is\] \[True\] to replicate only active records. * If you want to replicate and preserve a parent and child table hierarchy, add a filter for the sys_class_name column to each outbound entry. This ensures that all of the child table columns are replicated, and not just the parent the columns.For example, to replicate both the Task \[task\] parent table and the Incident \[incident\] child table, you must add \[Task type\] \[is\] \[Task\] as a filter in the parent table entry and \[Task type\] \[is\] \[Incident\] as a filter in the child table entry. In this example, Task type is the label for the sys_class_name column on each table. For details, see [Preserving table hierarchy in Instance Data Replication](https://www.servicenow.com/docs/o52dR_j31gI3hNPCf0GINQ "Decide if you want to replicate a parent-child table hierarchy and what strategy to use for replicating the data in Instance Data Replication (IDR)."). {#set-up-continuous-replication-idr__ul_l2n_dg3_dtb} |
      | Include Attachments | Option to replicate the files associated with the records that you are replicating. |
      | Included Fields | Fields to include. Move table fields into the Selected column to replicate them or into the Available column to prevent replicating them. Note: The system must replicate some fields, such as sys_id (Mandatory). The system cannot replicate some fields, such as Edge Encrypted and Password1. They do not appear in either column. |
      | Enable Custom Coalesce | Option to enable you to choose a field other than the default sys_id field to coalesce IDR. |
      | Coalesce Field | Choose a field to use to coalesce IDR. Only unique fields are available. See [Custom coalescing](https://www.servicenow.com/docs/_0MBwigenQ1TGUsBJ7KOdg#idr-coalesce "Coalesce records using a different column when records on the consumer instance have a different sys_id than the same record on the producer instance in Instance Data Replication (IDR)."). This field only displays if you select Enable Custom Coalesce. |
      [Table 1. Replication entry form]

      {#set-up-continuous-replication-idr__table_ty4_pmz_clb}
   4. Repeat these steps for each table that you want to include in the replication set.  
      Note:  
      If a table that you select has child tables, repeat these step and add outbound entries for each child table to maintain data integrity.
   {#set-up-continuous-replication-idr__substeps_fkj_t3w_gdc}
7. Select Submit.
8. Make the producer data available for replication to consumers by selecting Activate.  
   The producer is ready to send the data that is specified in the replication set to one or more consumer instances.
9. On a consumer instance, navigate to Instance Data ReplicationConsumer Replication Sets.
10. Select New.
11. On the form, fill in the fields.  
    {#set-up-continuous-replication-idr__table_c3t_jh3_3jb__entry__2}

    | Field | Description |
    |-|-|
    | Producer Instance URL | URL of the producer instance. For example, https://\<producer_instance\>.servicenow.com. |
    | Producer Replication Set Name | Name of the consumer replication set. The name on the consumer must match the name on the producer. Obtain the name from the producer administrator. |
    | Description | Description of the purpose of the replication. |
    [Table 2. Consumer Replication Set form]

    {#set-up-continuous-replication-idr__table_c3t_jh3_3jb}
12. Select Submit.  
    The list of all consumer replication sets on the consumer instance appears. The system sends a request to the producer replication set administrator to approve or deny the request.
13. Approve the consumer request.
    1. On the producer instance, navigate to Instance Data ReplicationProducer Replication Sets.
    2. Select the producer replication set where you want to approve consumer access.
    3. Under Related Links, on the Consumer Subscriptions tab, select the option for the consumer replication set that you want to approve.
    4. On the Actions on selected rows list, select Approve.  
       The approved consumer set starts receiving replicated data.
    {#set-up-continuous-replication-idr__substeps_h5q_ryd_hhb}
14. Activate the consumer replication set.
    1. On the consumer instance, navigate to Instance Data ReplicationConsumer Replication Sets.
    2. Select the consumer replication set that you want to activate.
    3. Select Activate.

    {#set-up-continuous-replication-idr__substeps_urs_czm_rdc}  
    After some time, the status changes to Active Replication, and the Partial Seeding and Full Seeding buttons are displayed.
{#set-up-continuous-replication-idr__steps_ffx_yff_rdc}

## Result

Data in the producer tables is replicated into tables and table columns of the same name on the consumer instances.

## What to do next

* [Seed a consumer instance](https://www.servicenow.com/docs/nbnZqsVCBx9_p~TVcOXSeA "Seed all or some of the tables in your Instance Data Replication (IDR) replication sets depending on the needs of your consumer instance.")
* [Transform replication data](https://www.servicenow.com/docs/acqsaJfmMywRz9wFIJTg3A "Transform producer instance data for tables or table columns that are named differently on consumer instances in Instance Data Replication (IDR).")
* [Trigger a workflow after replication](https://www.servicenow.com/docs/_0MBwigenQ1TGUsBJ7KOdg#post-replication-actions "Trigger workflows after replication using platform business rules.")
{#set-up-continuous-replication-idr__ul_g5k_gpm_rdc}

*[\>]: and then