Two-way sync
Changes in Azure Cosmos DB or DealCloud instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Cosmos DB and DealCloud in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Azure Cosmos DB, where it can be queried and joined like everything else.
Stacksync mirrors User, Deal, Company, Contact from DealCloud into Partition keys, Change feed entries, Stored procedures and triggers, Databases in Azure Cosmos DB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in DealCloud with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Field and stage updates in DealCloud arrive as row changes in Azure Cosmos DB, ready to drive jobs and notifications.
Accounts, contacts, and custom objects from DealCloud become tables in Azure Cosmos DB you can join with application data directly.
Signup, usage, or lifecycle changes written to Azure Cosmos DB sync onto the matching records in DealCloud, giving go-to-market teams live product context.
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.
| Azure Cosmos DB objects | DealCloud objects | How this pairing syncs | |
|---|---|---|---|
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Investment Synced with incremental and full sync. | Partition keys is specific to Azure Cosmos DB and Investment to DealCloud — each maps to any object or custom field on the other side. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Relationship Synced with incremental and full sync. | Change feed entries is specific to Azure Cosmos DB and Relationship to DealCloud — each maps to any object or custom field on the other side. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Activity Synced with incremental and full sync. | Stored procedures and triggers is specific to Azure Cosmos DB and Activity to DealCloud — each maps to any object or custom field on the other side. | |
| Databases Top-level namespaces that scope containers and throughput provisioning. | Task Synced with incremental and full sync. | Databases is specific to Azure Cosmos DB and Task to DealCloud — each maps to any object or custom field on the other side. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | User Synced with incremental and full sync. | Containers is specific to Azure Cosmos DB and User to DealCloud — each maps to any object or custom field on the other side. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Deal Synced with incremental and full sync. | Items (JSON documents) is specific to Azure Cosmos DB and Deal to DealCloud — 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.
DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.
DeliveryEach detected change is written to DealCloud through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls DealCloud for changes on an incremental schedule, reading only records changed since the previous pass. Incremental via each entry's last-modified timestamp.
DeliveryEach detected change is applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–DealCloud connection.
Changes in Azure Cosmos DB or DealCloud instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Cosmos DB or DealCloud data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Cosmos DB or DealCloud record.
Track your Azure Cosmos DB ⇄ DealCloud sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and DealCloud.
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 Azure Cosmos DB and DealCloud 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 Azure Cosmos DB and DealCloud 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 Azure Cosmos DB and DealCloud: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Partition keys and Change feed entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the DealCloud side: User, Deal, Company, Contact, plus custom fields where DealCloud exposes them. On the Azure Cosmos DB side: Partition keys, Change feed entries, Stored procedures and triggers, Databases. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Azure Cosmos DB and DealCloud: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in DealCloud arrive as row changes in Azure Cosmos DB, ready to drive jobs and notifications.
Azure Cosmos DB: REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces. Authentication: Account keys, resource tokens, or Microsoft Entra ID role-based access. DealCloud: REST API (DealCloud Data API v2). Authentication: OAuth 2.0 client-credentials; a DealCloud administrator generates a client ID and secret in the DealCloud admin API settings and grants Stacksync the required scopes. Stacksync manages authentication, retries, and rate limits on both sides.
DealCloud: DealCloud is Intapp's deal and relationship management platform, purpose-built for private capital markets (private equity, venture capital, investment banking, and advisory firms). Azure Cosmos DB: Items are JSON with no enforced schema, so field mapping must handle heterogeneous documents within one container. Stacksync's field mapping accounts for these differences between Azure Cosmos DB and DealCloud without custom code.
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 392 integrations available for Azure Cosmos DB and DealCloud.