Real-time
Two-way sync
Changes in Microsoft Dynamics 365 Sales or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Data warehouse
Microsoft Dynamics 365 Sales to Starburst Enterprise integration — real-time, two-way sync
Keep Microsoft Dynamics 365 Sales 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Live sync
stacksync.com - <1s
- latency
- 2-way
- sync
- 100M+
- records
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 Microsoft Dynamics 365 Sales and Starburst Enterprise
Sync Microsoft Dynamics 365 Sales into Starburst Enterprise continuously and push warehouse results back onto CRM records, one two-way connection instead of two pipelines.
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. Opportunities, Quotes, Orders, Invoices from Microsoft Dynamics 365 Sales land in Starburst Enterprise as live tables, updated within seconds, and columns computed in Starburst Enterprise write back to fields in Microsoft Dynamics 365 Sales. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Common use cases
- 01 Run a two-way dual-run between Dynamics and another CRM during a migration.
- 02 Feed BI models with continuously updated CRM data instead of scheduled exports.
- 03 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
- 04 Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
Common sync patterns
Cleanup that sticks
Deduplication and normalization done in Starburst Enterprise can be written back, so warehouse-side cleanup actually fixes the CRM.
CRM analytics on live data
Accounts, contacts, and activity from Microsoft Dynamics 365 Sales are queryable in Starburst Enterprise moments after they change, so dashboards stop lagging the reality they describe.
Scores and segments back on the record
Lead scores, churn risk, or usage segments computed in Starburst Enterprise appear as fields in Microsoft Dynamics 365 Sales, where the people working accounts actually see them.
What you can sync between Microsoft Dynamics 365 Sales and Starburst Enterprise
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.
| Microsoft Dynamics 365 Sales objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Accounts Company records in Dataverse; the usual anchor for two-way sync with databases and ERPs. | Materialized views Precomputed results that make repeated sync reads cheaper. | Accounts is specific to Microsoft Dynamics 365 Sales and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Contacts Person records linked to accounts; synced with marketing and support systems. | Columns Typed per the Trino type system, mapped from each source's native types. | Contacts is specific to Microsoft Dynamics 365 Sales and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Leads Prospect records; written in from enrichment or web forms, read out on qualification. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Leads is specific to Microsoft Dynamics 365 Sales and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Opportunities is specific to Microsoft Dynamics 365 Sales and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Quotes Pricing proposals; often synced with CPQ or ERP pricing data. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Quotes is specific to Microsoft Dynamics 365 Sales and Tables to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. | Views Engine-level SQL views used to shape federated data before syncing it out. | Orders is specific to Microsoft Dynamics 365 Sales and Views to Starburst Enterprise — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics 365 Sales and Starburst Enterprise
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.
Microsoft Dynamics 365 Sales Starburst Enterprise Sub-second propagation
DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
Starburst Enterprise Microsoft Dynamics 365 Sales Interval-based propagation
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 Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
- Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with Microsoft Dynamics 365 Sales ⇄ Starburst Enterprise
Connect Microsoft Dynamics 365 Sales and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365 Sales–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics 365 Sales or Starburst Enterprise 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 Microsoft Dynamics 365 Sales or Starburst Enterprise record.
Observability
Monitoring
Track your Microsoft Dynamics 365 Sales ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics 365 Sales and Starburst Enterprise.
How the Microsoft Dynamics 365 Sales and Starburst Enterprise connectors work
Microsoft Dynamics 365 Sales
- Integration surface
- Dataverse Web API (OData v4 REST)
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- Dataverse change tracking with delta tokens, plus registered webhooks on table events
- Capabilities
- read · write · webhooks
- Rate limits
- Requests are governed by Dataverse service protection limits evaluated per user and time window.
Starburst Enterprise
- Integration surface
- ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
- Authentication
- Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
- Change detection
- Query-based polling; Starburst is a query engine and exposes no change log of its own
- Capabilities
- read · write
- Rate limits
- Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works
How to connect Microsoft Dynamics 365 Sales to Starburst Enterprise — 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 Microsoft Dynamics 365 Sales 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.
Microsoft Dynamics 365 Sales
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics 365 Sales 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.
objects · Microsoft Dynamics 365 Sales ⇄ Starburst EnterpriseCustomers 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.
Microsoft Dynamics 365 Sales Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics 365 Sales and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics 365 Sales and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365 Sales's Accounts and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Microsoft Dynamics 365 Sales and Starburst Enterprise: Cleanup that sticks; CRM analytics on live data; Scores and segments back on the record. Deduplication and normalization done in Starburst Enterprise can be written back, so warehouse-side cleanup actually fixes the CRM.
-
Microsoft Dynamics 365 Sales: Dataverse Web API (OData v4 REST). Authentication: OAuth 2.0 via Microsoft Entra ID. 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.
-
Microsoft Dynamics 365 Sales: Data lives in Dataverse tables exposed through an OData v4 Web API, so standard query options handle filtering, expansion, and paging. Starburst Enterprise: A single SQL statement can join tables across catalogs, meaning one query can span several distinct backend systems. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics 365 Sales–Starburst Enterprise integration in-house.
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 363 integrations available for Microsoft Dynamics 365 Sales and Starburst Enterprise.
Popular · 3 of 363
-
Microsoft Dynamics 365 Sales ⇄ BigQuery -
Microsoft Dynamics 365 Sales ⇄ Databricks -
Microsoft Dynamics 365 Sales ⇄ AWS S3
No integrations match .
