Skip to content
Sendora Cloud
Create account
2026-05-29 · Docs

Data Sync renamed Import & Export — biggest copy-vs-code gap in the audit

  • Fourth integrity gap surfaced. Marketing claimed: scheduled exports to S3 / GCS / Azure Blob / R2, reverse-ETL to Snowflake / BigQuery / Postgres pushed on cron, backfill jobs with safe-pause / safe-resume, bcrypt / scrypt / argon2 hash-import. Code shipped: CSV import of 3 entity types, on-demand export of 4 to CSV/JSON in R2, 15-min presigned download URL. No cron, no scheduled push, no destination connectors, no backfill resume. Hash-import lives in auth-service, not here.
  • Renamed to **Import & Export** in product page + dashboard sidebar + module registry. Honest about the scope: ad-hoc migration + ad-hoc data pulls, not continuous warehouse sync.
  • Hightouch comparison rewritten as a clear non-replacement. Hightouch wins on every destination + cron + connector row; Sendora's only win is "you may not need it at all if all your destinations live in Sendora". 5 FAQ entries explicitly call out what's missing.
  • useCases trimmed to the 3 honest jobs: migration on/off, ad-hoc analyst pull, periodic warehouse load you trigger yourself.
  • Scheduled-push + destination connectors moved to public roadmap (no committed date) so prospects evaluating against Hightouch see the gap upfront instead of in the contract.