Configure field mapping for reverse ETL

Field mapping defines which columns from your reverse ETL model map to which fields (or properties) in the destination. This guide covers primary keys and column-to-field mapping. For concepts, see How reverse ETL works.

Where to Configure

• When creating a new integration: In the Configure step (step 3), once a RETL model has been successfully previewed and the destination object was selected you'll need to configure the required mapping. You must set primary keys and at least one field mapping before syncing.
• On an existing integration: Open a Reverse ETL integration → Settings tab → Field mapping section.

Set Primary Keys

• Primary key in the source: Choose the column from your model that uniquely identifies each row (e.g. id, email). Matia relies on this field to match rows for updates or deletes when using Mirror or Upsert.
• Primary key in the destination: Choose the destination field that holds the same identifier (e.g. Contact ID, Email). Matia uses this pair to decide whether to insert or update a record.

Primary keys are required for Mirror and Upsert. They must be unique and non-null in both source and destination.

Map Columns to Destination Fields

• Add mappings manually: For each destination field you want to populate, select the model column that supplies the value. You can add as many mappings as the destination supports. Matia also supports syncing integration related variables (e.g. integration run ID, sync timestamp)
• Auto-mapping: Use Auto-mapping to let Matia suggest mappings based on semantic naming (e.g. email → Email, company_name → Company Name). Review and adjust the suggestions, then add or remove mappings as needed.

You can start from the source (pick a column, then choose destination field) or from the destination (pick a field, then choose column). Ensure data types are compatible; casting may be required in your model SQL if the destination expects a specific format.

Save and Test

Save the settings. Use Test Sync to push one sample record and confirm the mapped values appear correctly in the destination.

For reference, see Models and destination objects.