Two-way sync
Changes in Salesloft or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Salesloft and Starburst Enterprise in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Meetings, Users, Custom Fields, People from Salesloft land in Starburst Enterprise as live tables, updated within seconds, and columns computed in Starburst Enterprise write back to fields in Salesloft. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Deduplication and normalization done in Starburst Enterprise can be written back, so warehouse-side cleanup actually fixes the CRM.
Accounts, contacts, and activity from Salesloft are queryable in Starburst Enterprise moments after they change, so dashboards stop lagging the reality they describe.
Lead scores, churn risk, or usage segments computed in Starburst Enterprise appear as fields in Salesloft, where the people working accounts actually see them.
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.
| Salesloft objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Meetings Booked meeting records tied to people and users. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Meetings is specific to Salesloft and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Users Seller records used for ownership mapping and activity attribution. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Users is specific to Salesloft and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Custom Fields Per-person and per-account fields commonly populated by enrichment syncs for personalization. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Custom Fields is specific to Salesloft and Tables to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| People Prospect records with contact data and CRM ID mappings, the primary sync target. | Views Engine-level SQL views used to shape federated data before syncing it out. | People is specific to Salesloft and Views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Accounts Company records mirrored from the CRM for account-based workflows. | Materialized views Precomputed results that make repeated sync reads cheaper. | Accounts is specific to Salesloft and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Cadences Multi-step outreach sequences that people are enrolled in and reported on. | Columns Typed per the Trino type system, mapped from each source's native types. | Cadences is specific to Salesloft and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. |
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.
DetectionSalesloft notifies Stacksync of record changes through webhook events. Webhook event subscriptions plus polling on updated_at timestamps.
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is written to Salesloft through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesloft–Starburst Enterprise connection.
Changes in Salesloft or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Salesloft or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Salesloft or Starburst Enterprise record.
Track your Salesloft ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Salesloft and Starburst Enterprise.
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.
Authenticate Salesloft and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Salesloft and Starburst Enterprise 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Salesloft and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Salesloft's Meetings and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
Salesloft: REST API (v2). Authentication: OAuth 2.0. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
Salesloft: People and Accounts carry native CRM ID mappings, so syncs can join Salesloft engagement data to CRM records without fuzzy matching. Starburst Enterprise: It is built on open-source Trino, so Trino drivers, clients, and SQL semantics apply. Stacksync's field mapping accounts for these differences between Salesloft and Starburst Enterprise 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 Salesloft and Starburst Enterprise records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Salesloft and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Salesloft–Starburst Enterprise integration in-house.
Yes — Stacksync ships production-grade connectors for both Salesloft and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 434 integrations available for Salesloft and Starburst Enterprise.