Sync Modes and Destinations

This page is the authoritative reference for reverse ETL sync modes and how they relate to destinations. Sync mode is set at the integration level in Settings (not per table). Support for Update only and Delete only depends on the destination.

Mirror

• Behavior: Matia syncs inserts, updates, and deletes. The destination is kept in sync with the model result: new records are inserted, changed records are updated, and records that no longer appear in the model are deleted in the destination.
• When to use: When the destination should exactly reflect the model (e.g. a full list that can shrink or grow).
• Requirements: Primary key in source and destination so Matia can match records and detect deletes.

Upsert

• Behavior: Matia syncs inserts and updates only. New records are inserted; existing records (matched by primary key) are updated. Records that disappear from the model are not deleted in the destination.
• When to use: When you only add and update records (e.g. contact sync) and never want Matia to delete destination records.
• Requirements: Primary key in source and destination for matching.

Update only

• Behavior: Only updates to existing destination records are applied. No inserts, no deletes. Rows in the model that do not exist in the destination are skipped (or handled per destination).
• When to use: When the destination is populated elsewhere and you only want to update specific fields.
• Support: Depends on the destination connector; not all destinations support Update only.

Delete only

• Behavior: Only deletes are applied — records that exist in the destination but no longer in the model are removed. No inserts or updates.
• When to use: When you want Matia to only delete records in the destination and never want Matia to update or create new records.
• Support: Depends on the destination connector; not all destinations support Delete only.

Destination Objects

Each destination (e.g. HubSpot, Salesforce) exposes objects (Contact, Company, custom object). You select one destination object per integration. The same destination asset can be used in multiple integrations with different objects or models. Field mapping and primary key must match what the destination API expects for that object.

For model and destination object reference, see Models and destination objects. For configuration, see Create and configure a reverse ETL model and Configure field mapping.