A few months ago, a customer asked us: "When are you going to do reverse ETL?"
Their reasoning: they were already paying us for SnowExporter to deliver scheduled reports to email and SFTP. They were also paying $X/month for a separate reverse ETL tool — a service that copies data out of Snowflake, into the vendor's cloud, and forwards it to their CRM. Two tools, two contracts, two security reviews, two audit logs.
The data lived in Snowflake. The action happened in Salesforce. The middle hop existed only because of vendor architecture.
So we built reverse ETL into SnowExporter.
What's in v2.2
Two connectors at launch — Salesforce and HubSpot — covering roughly 80% of the reverse ETL demand surface. Both connectors include:
- Real upsert semantics (not "copy a CSV") — composite-API upsert
against Salesforce
sobjects, batch upsert against HubSpot CRM objects - Schema discovery — pull the destination's real fields and show them in the wizard, so you're not hunting through API docs
- Field mapping UI with auto-detection of likely matches
- State fingerprints to skip unchanged records on subsequent runs
- Rate-limit retry with
Retry-Afterhonored - Reconciliation — count destination-side records after each run and compare to what we sent. Surfaces silent drift.
-
Per-sync
COMPLIANCE_AUDITtrail
The compliance loop applies
If you've read about v2.1 — the compliance enforcement loop that gates every scheduled email, Slack message, and SFTP push — here's the kicker:
v2.2.11 extends that loop to reverse ETL.
Wrote a policy that says "PII to Salesforce requires Compliance team approval"? It works today. Wrote "PCI cardholder data cannot leave the warehouse to any external destination"? Salesforce and HubSpot are external destinations — blocked automatically.
The compliance engine sits above the network call. Blocked syncs never touch the destination at all, never burn API quota, never sit in a silently-failing state on the SaaS side. Approval-required syncs enqueue a request for your compliance team and re-run cleanly after approval.
This is the actual differentiator. Census and Hightouch can be governed, but you have to build a separate compliance integration on top — different team, different tool, different audit log. v2.2.11 gives you one policy surface for everything that leaves the warehouse.
What's not in v2.2 (and what's coming next)
We were honest in the design phase: v2.2 covers Salesforce + HubSpot, with upsert + snapshot modes, with the compliance loop. We did not ship Zendesk, Marketo, Intercom, or Salesforce / HubSpot custom-object support. Those are v2.2.x patches based on customer demand.
What's coming next, in v2.3: Incremental Extract for audit-tracked tables.
If your tables have CREATE_KEY / UPDATE_KEY columns (or any
monotonic counter or modified-at timestamp), v2.3 turns them into a "tick this box to
make this sync incremental" experience. First run does a full backfill and captures
the high-water mark; subsequent runs only emit rows where the watermark has advanced —
typically less than 1% of the table.
For Snowflake shops in regulated industries — banks, healthcare, insurance, public companies — v2.3 is the feature that turns your existing audit-column investment into a one-checkbox capability.
Get it today
Install SnowExporter from the Snowflake Marketplace. Free for v2.0, v2.1, and v2.2 features. The first paid tier introduces with v2.3 — early-access applications are open now for regulated-industry customers with 100+ audit-tracked tables.