Two-way sync
Changes in DealCloud or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep DealCloud and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Finance and sales describe the same customers in different systems. DealCloud knows the relationship: who the contacts are and what is in motion with the account. Rillet knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Account, Customer, Vendor, Invoice in Rillet to Activity, Task, User, Deal in DealCloud with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
When a contact or address is corrected in DealCloud, Rillet gets the update before the next invoice goes out.
Finance sees the account owner and relationship history from DealCloud when chasing a balance, and sales sees that the chase is happening.
A won opportunity creates or updates the customer in Rillet with the right billing details, so invoicing starts without re-keying.
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.
| DealCloud objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| User Synced with incremental and full sync. | Bill Synced with incremental and full sync per the Stacksync docs. | User is specific to DealCloud and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Deal Synced with incremental and full sync. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Deal is specific to DealCloud and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| Company Synced with incremental and full sync. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Company is specific to DealCloud and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| Contact Synced with incremental and full sync. | Charge Synced with incremental and full sync per the Stacksync docs. | Contact is specific to DealCloud and Charge to Rillet — each maps to any object or custom field on the other side. | |
| Fund Synced with incremental and full sync. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Fund is specific to DealCloud and Reimbursement to Rillet — each maps to any object or custom field on the other side. | |
| Investment Synced with incremental and full sync. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Investment is specific to DealCloud and Custom Field to Rillet — 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.
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 written to Rillet through its API, with automatic retries and rate-limit backoff.
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is written to DealCloud through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DealCloud–Rillet connection.
Changes in DealCloud or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DealCloud or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DealCloud or Rillet record.
Track your DealCloud ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DealCloud and Rillet.
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 DealCloud and Rillet 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 DealCloud and Rillet 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 DealCloud and Rillet: authenticate both systems, choose the objects to sync (such as DealCloud's User and Deal), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Rillet side: Account, Customer, Vendor, Invoice, plus custom fields where Rillet exposes them. On the DealCloud side: Activity, Task, User, Deal. 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 DealCloud and Rillet: Billing detail changes flow back; Collections with context; Where DealCloud tracks deals: closed-won creates the finance record. When a contact or address is corrected in DealCloud, Rillet gets the update before the next invoice goes out.
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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: Several objects (Subsidiary, Tax Rate, Product, Contract, Bank Account, Bank Transaction) do not support incremental sync — historic sync only. DealCloud: DealCloud's data model is fully configurable: each firm defines its own entry types (objects) and fields, so syncs map to a firm-specific schema rather than a fixed one. Stacksync's field mapping accounts for these differences between DealCloud and Rillet 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 DealCloud and Rillet.