Reverse ETL

Reverse ETL inverts the usual warehouse load: the Job’s source is a warehouse (or curated views), and the destination is an operational system your team uses day to day.

Create a Reverse ETL Job

Go to Data → Jobs → New Job.
Complete Source → Destination → Tables → Field Mapping → Configure.
On Configure (advanced), set Job Type to Reverse ETL.
Set sync mode and Destination Mode, then click Create Job.

Role	Typical connections
Source	Snowflake, BigQuery, or another warehouse / curated view
Destination	PostgreSQL, MySQL, MongoDB, or other operational stores

Other warehouse and SaaS destinations may be available or on demand.

Views and curated tables

Prefer syncing a warehouse view or modeled table rather than raw landing tables:

CREATE OR REPLACE VIEW public.active_customer_segments AS
SELECT customer_id, segment, ltv_score, last_updated
FROM analytics.customer_model
WHERE is_active = true;

Select that view on the Tables step. It evaluates fresh on each run.

Write modes

Scenario	Destination Mode
Keep destination aligned with the model	Upsert — insert + update by PK
Append-only event-style output	Append — add new rows
Replace the whole target each run	Overwrite — replace table (with Full Refresh)

Schedule Reverse ETL to land after warehouse models refresh (for example after a dbt run).

What Reverse ETL is not

Warehouse-to-warehouse replication is a normal ETL Job (warehouse as both source and destination), not Reverse ETL.

Last modified on October 10, 2026

Getting Started

Guides

Move

Know

Trust

Match

Core Concepts

Connectors

Platform

Support

Create a Reverse ETL Job

Views and curated tables

Write modes

What Reverse ETL is not

​Create a Reverse ETL Job

​Views and curated tables

​Write modes

​What Reverse ETL is not

​Related articles

Create a Reverse ETL Job

Views and curated tables

Write modes

What Reverse ETL is not

Related articles