Real-time
Two-way sync
Changes in Salesforce or Treasuredata instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Salesforce to Treasuredata integration — real-time, two-way sync
Keep Salesforce and Treasuredata in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Salesforce and Treasuredata
Put live Salesforce data behind every dashboard and cohort in Treasuredata, and write the segments and scores Treasuredata computes back onto the Salesforce record — one connection, not a nightly export.
Treasuredata turns data into dashboards, cohorts, and metrics; Salesforce is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.
Stacksync syncs Products and Price Books, Custom Objects, Accounts, Contacts from Salesforce into Treasuredata field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Treasuredata write back to fields in Salesforce, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
- 02 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
- 03 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
- 04 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
Common sync patterns
Report on live CRM data
New records and status changes in Salesforce appear in Treasuredata within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.
Where Salesforce accepts updates: segments and scores back on the record
Cohorts, scores, and computed metrics from Treasuredata sync onto fields in Salesforce, putting the analysis where reps and owners actually work the accounts.
One customer across analytics and CRM
The same account or person is keyed consistently in both systems, so a profile or row in Treasuredata lines up with the contact or account in Salesforce.
What you can sync between Salesforce and Treasuredata
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Salesforce objects | Treasuredata objects | How this pairing syncs | |
|---|---|---|---|
| Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. | Contacts is specific to Salesforce and Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. | Leads is specific to Salesforce and Journeys to Treasuredata — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Predictive Segments AI/ML-scored segments; propensity scores read out and written onto customer records in a CRM or database for prioritization. | Opportunities is specific to Salesforce and Predictive Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. | Cases is specific to Salesforce and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side. | |
| Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. | Campaigns is specific to Salesforce and Query Jobs to Treasuredata — each maps to any object or custom field on the other side. | |
| Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. | Tasks and Events is specific to Salesforce and Databases to Treasuredata — each maps to any object or custom field on the other side. |
How changes propagate between Salesforce and Treasuredata
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Salesforce Treasuredata Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.
Treasuredata Salesforce Interval-based propagation
DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Salesforce: Daily API request allocations vary by edition and license count.
- Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Salesforce ⇄ Treasuredata
Connect Salesforce and Treasuredata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Treasuredata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Salesforce or Treasuredata data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Salesforce or Treasuredata record.
Observability
Monitoring
Track your Salesforce ⇄ Treasuredata sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Salesforce and Treasuredata.
How the Salesforce and Treasuredata connectors work
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
Treasuredata
- Integration surface
- TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
- Authentication
- API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
- Change detection
- Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
- Capabilities
- read · write
- Rate limits
- TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works
How to connect Salesforce to Treasuredata — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Salesforce and Treasuredata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Salesforce
connected
Treasuredata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Salesforce and Treasuredata objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Salesforce ⇄ TreasuredataCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Salesforce TreasuredataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Salesforce and Treasuredata integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Salesforce and Treasuredata: authenticate both systems, choose the objects to sync (such as Salesforce's Contacts and Leads), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Treasuredata: TD is multi-region (US, EU, Tokyo); API calls must target the region-specific endpoint where the account is provisioned, and data does not cross regions. Salesforce: Records are queried with SOQL, and every standard and custom object carries a SystemModstamp field that sync engines use to order incremental changes. Stacksync's field mapping accounts for these differences between Salesforce and Treasuredata without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Salesforce and Treasuredata records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Salesforce and Treasuredata connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Salesforce–Treasuredata integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Salesforce and Treasuredata. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). On Treasuredata: Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 411 integrations available for Salesforce and Treasuredata.
Popular · 4 of 411
No integrations match .
