---
schema_version: "1"
id: 957c58b17556a3547b10c6ffd1181daef4acf3b3de10a57ebb74985ec8fba6d9
title: Syncing Copy Field Enrichments
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_syncing_copy_field_enrichments.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_syncing_copy_field_enrichments.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: edfec19fb94de4c54a4f2fcb6d8255ed871f3a36c1bae1ec4520c80596b31bbe
description: Learn how data is copied and synced between Data 360 and your org for copy field enrichments. Get tips for troubleshooting data syncing and changing enrichments.
products:
  - Data 360
release: "264"
---
# Syncing Copy Field Enrichments

Learn how data is copied and synced between Data 360 and your org for copy field enrichments. Get tips for troubleshooting data syncing and changing enrichments.

The last step in creating a copy field enrichment is to start a data sync. The first sync is always a full sync.

## Full Sync And Incremental Sync

Copy field enrichments use two types of sync.

- Full Sync is a series of bulk jobs that started when you create the enrichment. The bulk jobs copy records in batches. It can take hours for all of the jobs to be complete. A full sync job can run for a maximum of 24 hours. It can process 60–100 million records, depending on the environment. Each job must be completed before the data is fully available. The log for each job is available separately in the Sync History tab for the enrichment.
- Incremental Sync uses batched events to keep your field data up to date. Incremental sync is triggered by any change in Data 360 data for the fields you're copying.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note If more than 250,000 data changes occur in a transaction after any filter conditions are applied for copy field enrichment, the incremental sync is replaced by a full sync. A full sync reduces latency in data syncs for large volumes of changes. After the full sync completes, the system switches to incremental sync again. To learn about the cost of copy field enrichment for each sync method, see [Considerations for Enrichment Cost Impact](https://help.salesforce.com/s/articleView?id=data.c360_a_enrichment_considerations_cost.htm&type=5&language=en_US).

## Stopping and Restarting Syncs

If you stop syncing your enrichment, no more data is copied into your org, but no data or fields are removed. If you restart your sync, it performs a full sync again and copies all of the data from Data 360, which can take days. However, Salesforce recommends periodically restarting the sync, because incremental syncs behave like events and can occasionally have incomplete data for transactions with over 100,000 changes.

## Troubleshooting Sync

The Sync History tab shows every sync that changes a record in your org. It lists the type of sync and indicates its status. To see the Sync History tab, click the name of an enrichment in the list screen.

For full syncs, the Sync History tab Details column shows links to logs for each batch of changes. The logs expire after 7 days and are no longer accessible.

In some cases, a sync job succeeds as a whole, but specific records fail to be copied over. To see if individual records are failing to sync, check the Sync History tab Records Excluded column.

For incremental syncs, any errors that are encountered are shown in the Sync History tab Details column. If no records are changed in an incremental sync, the sync doesn’t appear in the Sync History tab.

If you have a key qualifier specified and the sync seems to be copying over the wrong data, check to make sure that the key qualifer is correct. If it’s incorrect, stop the sync, specify the correct key qualifier, and restart the sync.

## Record Exclusions and Errors

Records are excluded from sync for several reasons.

- Locked data—data locked by another user at the time of sync is excluded from the sync
- Orphaned data—records that don't have a corresponding user in the org are excluded from the sync. For example, assume that org A and org B have records ingested into Data 360 and you're syncing records from org A. Some amount of the records to sync are customers that only exist in org B and those records are excluded. You only sync records that are relevant for your customers. These records are orphaned records because they don't have a parent object in your org.
- Mismatched Data—data that contains characters or other issues that can’t be included in the org. These records fail validation and can’t be synced.