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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Explore

# Exploring Instance Data Replication {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Exploring Instance Data Replication

Instance Data Replication (IDR) in ServiceNow enables continuous or scheduled replication of data updates from a producer instance to one or more consumer instances.
It helps maintain consistent data across different instances, whether within different organizations or separate companies.
IDR ensures recoverability of data in transit during failures, supporting synchronization of operational data but excluding metadata and sensitive encrypted fields.
Show full answer Show less  

## Key Features

* **Producer and Consumer Replication Sets:** Administrators configure which tables and columns to replicate by creating producer replication sets, and consumers request and activate consumer replication sets to receive data.
* **Replication Types:** Supports continuous near-real-time replication, scheduled replication for historical data, bidirectional replication (updates on either side), and discrete replication targeting specific consumer instances.
* **Data Transformation:** Administrators can map data to differently named tables/columns on consumer instances and modify data during replication using adapters (e.g., currency or timezone conversion).
* **Workflow Integration:** Post-replication workflows can be triggered for notifications or validations to support business processes.

## Use Cases and Benefits

* Keeping data synchronized across multiple ServiceNow instances in near real-time or on a schedule.
* Supporting data sharing between different business units or external companies with separate instances.
* Mapping and transforming data for localization or business-specific requirements.
* Automating follow-up actions after data replication through workflows.

## Limitations and Best Practices

* IDR is not designed for instance cloning and does not replicate metadata, most user/system tables, or encrypted fields.
* Regular replication of large attachments (over 10 MB) or CMDB tables should be avoided or carefully managed due to performance impact.
* Maximum record size is 10 MB, and continuous replication is optimal for up to about 1 million records daily.
* Seeding data must complete within seven days, and only one scheduled replication set with a single outbound entry is supported.
* Data overwriting and replication of sensitive data requires testing in a non-production environment to prevent data loss or exposure.
* Data archiving is not synchronized between instances---archive rules must be managed independently.

## Next Steps

ServiceNow customers looking to implement IDR should explore detailed configuration guides, administration best practices, and reference documentation to optimize their replication setup and ensure data consistency across instances.  
Instance Data Replication (IDR) replicates data updates on one instance, called the producer instance, to one or more other instances, called the consumer instances.

## IDR overview {#exploring-instance-data-replication__cf-exploring-parent-overview}

Maintain consistent data across different instances using IDR.

* Automatically replicate data to one or more other instances.
* Synchronize data between different organizations in your company or even between different companies with separate instances.
* Data that is in transit during a crash is recoverable.
{#exploring-instance-data-replication__ul_f1j_rky_qdc}

## IDR users {#exploring-instance-data-replication__cf-exploring-parent-users}

{#exploring-instance-data-replication__table_bbw_why_qdc__entry__2}

| User | Description |
|-|-|
| IDR admin | The IDR admin determines which tables and columns to replicate and analyzes table hierarchies and relationships. The IDR admin creates producer and consumer replication sets and monitors ongoing replication. |
[Table 1. Users]

{#exploring-instance-data-replication__table_bbw_why_qdc}

## IDR workflow {#exploring-instance-data-replication__section_fnx_v3y_qdc}

This image shows how IDR replicates data from multiple tables on a producer instance to multiple consumer instances.
Figure 1. Replication overview  
1. On the producer instance, the IDR admin specifies the tables and table columns to replicate by creating a producer replication set.
2. The IDR admin activates the producer replication set, which makes the producer data available for replication to consumers.
3. The IDR admin creates consumer replication sets on one or more consumer instances to receive the producer replication set data.
4. On each consumer instance, the IDR admin requests approval from the producer instance.
5. On the producer instance, the IDR admin approves or denies the requests from each consumer instance.
6. On each approved consumer instance, the IDR admin activates the consumer replication set. After the consumer replication is activated, data that is updated in a producer replication set automatically updates the corresponding data in the consumer replication sets.
7. On each consumer instance, the IDR admin can optionally replicate existing data from the producer instance by seeding data to the consumer instances.
8. On either the producer or consumer instance, the IDR admin can optionally replicate data to tables or table columns that have different names on the consumer instance by configuring a transformation in the replication set.
9. On either the producer or consumer instance, the IDR admin can optionally modify producer data before replicating it to a consumer by configuring an adapter in the replication set.
{#exploring-instance-data-replication__ol_inx_v3y_qdc}

## IDR benefits {#exploring-instance-data-replication__cf-exploring-parent-benefits}

{#exploring-instance-data-replication__table_ebw_why_qdc__entry__3}

| Benefit | Feature | Users |
|-|-|-|
| Continuously replicate inserts and updates from a producer instance to one or more consumer instances in near-real time, ensuring minimal delay. | [Continuous replication](https://www.servicenow.com/docs/y5QSwNwjqDyXIJbGVR6wEA "Replicate inserts and updates from a producer instance to one or more consumer instances in near-real time in Instance Data Replication (IDR).") | Administrator |
| Schedule replication of historical inserts and updates from a producer instance to one or more consumer instances at predefined intervals. | [Scheduled replication](https://www.servicenow.com/docs/X0REryEdytb__LX~7eixmw "Replicate historical inserts and updates from a producer instance to one or more consumer instances on a scheduled basis in Instance Data Replication (IDR).") | Administrator |
| Continuously replicate inserts and updates from a producer instance to a consumer instance in near-real time, with changes on either side replicated back to the other. | [Bidirectional replication](https://www.servicenow.com/docs/bwO3mK6ta2v4_Joc52pWaQ "Bidirectional replication in Instance Data Replication (IDR) enables data to flow from a producer instance to a consumer instance and accept data from a consumer instance to flow back to the producer instance.") | Administrator |
| Continuously replicate inserts and updates from a producer instance to specific, distinguished consumer instances in near-real time, ensuring each consumer instance receives updates independently. | [Discrete replication](https://www.servicenow.com/docs/2heCgx3VrgH02GTfWtOuCw "Distinguish consumers in Instance Data Replication (IDR) using discrete mapping in a producer replication set.") | Administrator |
| Map producer data to tables and table columns that are named differently on consumer instances. For example, you can modify and map table columns to localize data for different locales. | [Transform replication data](https://www.servicenow.com/docs/dnxO93XdA9KPgkdqTlmYiA "Transform producer instance data for tables or table columns that are named differently on consumer instances in Instance Data Replication (IDR).") | Administrator |
| Modify producer data before replicating it to a consumer instance using an adapter. For example, you can configure adapters that perform string and mathematical operations, such as converting one currency to another, or converting one time zone to another. | [Transform replication data](https://www.servicenow.com/docs/dnxO93XdA9KPgkdqTlmYiA "Transform producer instance data for tables or table columns that are named differently on consumer instances in Instance Data Replication (IDR).") | Administrator |
| Trigger post-replication workflows such as generating notifications or validating replication using business rules. | [Triggering workflows after replication](https://www.servicenow.com/docs/Jj8G31k3QDVBzGnm71mSkA#post-replication-actions "Trigger workflows after replication using platform business rules.") | Administrator |
[Table 2. benefits]

{#exploring-instance-data-replication__table_ebw_why_qdc}

## IDR limitations and when not to use IDR {#exploring-instance-data-replication__section_jvf_3g4_3gb}

* Do not use IDR to clone instances.

  IDR does not replicate metadata tables, child metadata tables, and most user and system tables. IDR is designed to replicate data, not to clone instances. For example, the Application File \[sys_metadata\] table and tables that extend \[sys_metadata\] (including the Business Rules
  \[sys_script\], Catalog \[sc_catalog\], and Workflow \[wf_workflow\] tables) are excluded and can't be replicated. For details on cloning, see [Instance Clone](https://www.servicenow.com/docs/access?context=system-clone-landing&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).
* Avoid using IDR to replicate a series of large attachments on a regular basis. If you need to include attachments that are larger than 10 MB regularly, monitor IDR to ensure that the lag time doesn't exceed expectations.
* Avoid continuous replication of CMDB tables. Replicating CMDB data as changes occur can create performance issues or unforeseen consequences with replication due to the number of records involved. If you must replicate CMDB tables, consider scheduling replication or use conditions to constrain the count of replicated records and ensure all required columns are included in the replication set.
* You cannot replicate Edge Encrypted, Field Encryption, and Password (2-Way Encrypted) fields.
* IDR does not synchronize data archiving between instances. For example, archiving records or restoring archive records on a producer instance doesn't affect archived records on the consumer instance (and vice versa). You must create and manage archive rules for each instance independently.
* Additional replication limitations:
  * Maximum record size is 10 MB.
  * Continuous replication supports up to approximately 1 million records per day.
  * Seeding must not take longer than seven days to complete.
  * You can only create one scheduled replication set, with only one outbound entry in that set.
  * 
  {#exploring-instance-data-replication__ul_ysq_gcs_byb}

{#exploring-instance-data-replication__ul_khc_kg4_3gb}  
Warning:  
IDR overwrites data on instances and can replicate sensitive data. Avoid potential data loss and data exposure, by testing your IDR implementation in a pre-production environment. See [data privacy in IDR](https://www.servicenow.com/docs/Lg4LrdeltYN9ugUpYxtnbQ "The ability of replication sets to host multiple remote consumers in Instance Data Replication (IDR) means that there are potential data privacy issues to consider.") for more information.

## What to explore next {#exploring-instance-data-replication__section_rhz_bry_qdc}

To learn more about configuring and using IDR, see:

* [Configuring Instance Data Replication](https://www.servicenow.com/docs/sDy8LZCXbzT1GLwssD0Q1w "Set up and configure Instance Data Replication (IDR).")
* [Replicating data with Instance Data Replication](https://www.servicenow.com/docs/39C9ZPIRq7~z7d~w6l~ghg "Synchronize data between instances using Instance Data Replication (IDR).")
* [Administering Instance Data Replication](https://www.servicenow.com/docs/mPrDa5suq3CymDUGJ9Flkg "Perform administrative duties in Instance Data Replication (IDR).")
* [Instance Data Replication reference](https://www.servicenow.com/docs/HweYPiuQCKeOCclp~EziZg "These reference topics provide additional information about data privacy in Instance Data Replication (IDR) and domain separation.")
{#exploring-instance-data-replication__ul_shz_bry_qdc}