Hightouch or Sendora — pick the trade-off, not the marketing.
Hightouch moves data FROM your warehouse TO your operational tools — Customer.io, Salesforce, Mixpanel, paid-ads platforms. Required because those tools live in separate vendors. Sendora collapses the destinations: messaging, audiences, support, analytics all share one tenant, so audience updates land in the senders without a reverse-ETL pipeline. The Import & Export module ships CSV/JSON export of 4 entity types to R2 (presigned download URL) — that's a manual migration path, not a continuous warehouse sync, and explicitly NOT scheduled push to Snowflake / BigQuery / Postgres or any external destination. If your destinations are mostly Sendora, you don't need Hightouch. If they aren't, you do.
Reverse-ETL pipeline. Push warehouse data into your operational tools on cron, with destination-by-destination connectors.
Honest non-replacement. Sendora collapses the destinations so reverse-ETL has nowhere to push, but if you need scheduled push to Salesforce / Marketo / paid ads, Hightouch wins.
Side-by-side
| Capability | Hightouch | Sendora |
|---|---|---|
| Reverse-ETL warehouse → ops tools (the product) | ✅ — multiple destinations + connectors | ❌ — destinations are inside Sendora; nothing to ETL into |
| Scheduled push to Snowflake / BigQuery / Postgres | ✅ cron + incremental | ❌ — on-demand CSV/JSON to R2 only |
| Destination push to Salesforce / Marketo / HubSpot / paid ads | ✅ — 200+ connectors | ❌ — none |
| Audience computation in warehouse | ✅ SQL-modeled | ✅ Customers module (compute over native event stream, no warehouse) |
| Real-time audience updates inside platform senders | Sync cadence | ✅ real-time same tenant |
| Identity resolution across tools | Via destination identifiers | ✅ one `user_id` across every Sendora module |
| Pricing model | Starter from $350/mo, scales per-destination + per-MAR | Bundled — no destination push at any tier |
Why teams switch to Sendora
- If every destination you'd push from Hightouch is a Sendora module (Email, Push, SMS, Audiences, Automation, In-App), there's no reverse-ETL to do. The data is already in the senders.
- Audience updates are real-time inside Sendora — no warehouse-sync cadence.
- Same `user_id` everywhere — no destination-specific identity stitching.
When Hightouch is the right call
- You reverse-ETL to Salesforce / HubSpot / Marketo / paid ads / non-Sendora destinations — Hightouch's connectors are the right answer there.
- You need scheduled push to your warehouse on cron — Sendora's export is on-demand fire-and-poll, no scheduling, no incremental, no destination push.
- You've built deep Hightouch SQL-modeled audiences your data team owns.
Common questions
Is Sendora's Import & Export module a Hightouch replacement?
No. It's a CSV/JSON import + on-demand export module — useful for migration on/off + ad-hoc data pulls. There's no scheduled-push, no destination connectors, no warehouse cron. If you reverse-ETL to non-Sendora destinations, keep Hightouch.
What's the actual export shape?
POST a job (type = `profiles` | `events` | `analytics` | `survey_responses`, format = `csv` | `json`, optional filters + date range). Background runner writes to R2. Poll the job until `status='completed'`, download via 15-minute presigned URL. ADMIN-gated + audit-logged.
Can I run real-time audiences without warehouse joins?
Yes — Customers module audiences compute over Sendora's native event stream in real time. Warehouse joins are not a requirement when your senders are all in the same tenant.
Push to Snowflake / BigQuery / Postgres on cron?
Not today. Export lands as a CSV/JSON file in R2; you'd Snowflake COPY / BigQuery LOAD from that file yourself. No native destination push, no cron, no incremental. On the roadmap, no committed date.
Import & Export
CSV import for profiles / events / contacts + on-demand export of 4 entity types to CSV or JSON. Honest about not being Hightouch.
Hightouch + Census do scheduled reverse-ETL from your warehouse INTO operational tools — that's a different product than what this module is. Sendora's Import & Export module ships two surfaces: CSV import with column mappings + dry-run preview (for profiles / events / contacts), and on-demand export of profiles / events / analytics / survey_responses to CSV or JSON. Exports land in R2 and you download via a 15-min presigned URL. No cron, no scheduled-push to Snowflake / BigQuery / Postgres, no backfill-resume — fire-and-poll only. The win is a clean migration on/off path, not a continuous warehouse sync.
Switch from Hightouch. Keep your weekend.
Free plan covers real product use, no credit card. Bulk hash import for auth, CSV import for profiles, schema-validated event import for analytics — Data Sync module handles the migration in a day.