Does IDR (instance data replication) replicate sys_id field of the expected records?Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Does IDR (instance data replication) replicate sys_id field of the expected records if the record has different sys_id on target consumer instance? Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Zurich Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Yes it does replicate the sys_id of the record under below mentioned conditions. By default, IDR uses a record's sys_id field as the lookup value to keep data synchronized between the producer and consumer instance. If the target table contains existing data or records from prior data imports, the sys_id values in the consumer don't match the sys_ids from the producer instance.Always consider the producer instance as the source of truth. Here is the documentation that explains on preparing the target tables on the consumer instance As in the question , in the scenerio when the same records are having different sys_id in 2 instances, existing records in the table on the consumer instance are not updated and duplicate records could be created.In situations where this can not be avoided, the suggestion is to clean the tables on the consumer instance prior to replication, remove the records in the target table or ensure the sys_id values in the producer and consumer are the same.Alternatively, you can use a custom Coalesce field to identify unique records (instead of the default sys_id column) for replication. Use a custom Coalesce column when records on the consumer instance have a different sys_id for the same records on the producer instance. For more information on using a custom Coalesce, please see documentatio on Custom coalescing. As per documentation , records that exist on the producer instance and not on the consumer instance are copied to the consumer instance.If the sys_id on the producer matches an existing record on the consumer instance, the entire record on the consumer instance is updated to match the producer. The sys_id of the record identifies the record on both instances. If you use the custom coalesce option, the field you select is used to coalesce records in both instances.If a replication set changes and no longer includes a table, IDR does not alter the records in the corresponding table on the consumer instances. So , in the scenerio when there are different sys_id on both instances for the records to be expected to have same sys_id , what it could be recommended is: For the records which have different sys_id's in the consumer instance, remove them on consumer instance ( do this with a 1 test user and backup the record by export XML to see the behaviour) and request a new seeding to copy the same record with sys_id as well from producer to consumer instance.Or you can set coalesce with a unique field another than sys_id to make this happen , because coalesce is being done as per sys_id but if the sys_id in the consumer instance is not the same , thenhttps://instancexxxx.service-now.com/nav_to.do?uri=idr_consumer_replication_entry.do?sys_id=xxxxxxx