The Reverse ETL sources support two sync modes that let you define how to sync your data to the destination:
- Upsert mode
- Mirror mode
By default, these modes sync the data incrementally, meaning they only sync the new data. However, you can choose to run a full sync manually.
In this mode, RudderStack supports insertion of new records and updates to the existing records, while syncing data to the destination.
In this mode, RudderStack 'mirrors' the source by keeping the destination data the same as the source data. It performs insertion, updates, and deletion of records while syncing data to the destination.
Whenever the columns mapping is changed, RudderStack runs a full sync the next time. While performing a full sync, RudderStack first deletes all the existing records and then syncs the records as per the latest column mappings.
What happens to the records that have not been successfully sent to the destination in the previous sync?
In case of an unsuccessful delivery, RudderStack retries sending the events in the next sync.