Real-time sync
Changes in Dun And Bradstreet or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Keep Dun And Bradstreet and MotherDuck in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into MotherDuck, so MotherDuck always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
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. Monitoring Notifications, Company Information (Data Block), Principals & Contacts (Data Block), Company Hierarchy & Connections (Family Tree) from Dun And Bradstreet land in MotherDuck as live tables, updated within seconds, and columns computed in MotherDuck write back to fields in Dun And Bradstreet. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Join Dun And Bradstreet's relationship data with billing, product, and support data in MotherDuck to build the customer picture the CRM alone cannot hold.
Deduplication and normalization done in MotherDuck can be written back, so warehouse-side cleanup actually fixes the CRM.
Accounts, contacts, and activity from Dun And Bradstreet are queryable in MotherDuck moments after they change, so dashboards stop lagging the reality they describe.
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.
| Dun And Bradstreet objects | MotherDuck objects | How this pairing syncs | |
|---|---|---|---|
| Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Databases to MotherDuck — each maps to any object or custom field on the other side. | |
| Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. | Schemas Namespaces within a database used to organize synced tables. | Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Schemas to MotherDuck — each maps to any object or custom field on the other side. | |
| Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | Tables The main landing target for synced records and source for analysis. | Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Tables to MotherDuck — each maps to any object or custom field on the other side. | |
| Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. | Views Modeled projections used as outbound sync sources. | Criteria Search is specific to Dun And Bradstreet and Views to MotherDuck — each maps to any object or custom field on the other side. | |
| Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. | Database Shares Read-only copies of a database shared with other users or teams. | Monitoring Notifications is specific to Dun And Bradstreet and Database Shares to MotherDuck — each maps to any object or custom field on the other side. | |
| Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. | Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | Company Information (Data Block) is specific to Dun And Bradstreet and Attached Local DuckDB Databases to MotherDuck — 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 Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).
DeliveryEach detected change is applied to MotherDuck as a row-level write, with types converted between the two schemas.
DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating MotherDuck records.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–MotherDuck connection.
Changes in Dun And Bradstreet or MotherDuck instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dun And Bradstreet or MotherDuck data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dun And Bradstreet or MotherDuck record.
Track your Dun And Bradstreet ⇄ MotherDuck sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and MotherDuck.
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 Dun And Bradstreet and MotherDuck 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 Dun And Bradstreet and MotherDuck 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 integration between Dun And Bradstreet and MotherDuck — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
Dun And Bradstreet: D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring. Authentication: OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours. MotherDuck: SQL through DuckDB clients and drivers using a MotherDuck (md:) connection. Authentication: Access token created in MotherDuck (Settings > General > Create Token), pasted into Stacksync; database name and schema configurable if not using defaults. Stacksync manages authentication, retries, and rate limits on both sides.
Dun And Bradstreet: Rate limits are per-contract - a transactions-per-second cap plus weekly/monthly/yearly quotas; overage returns HTTP 429 with error 0045/0046 (0047 on spike arrest), and quotas reset on UTC boundaries. MotherDuck: Hybrid execution can split a query between the local DuckDB process and cloud compute. Stacksync's field mapping accounts for these differences between Dun And Bradstreet and MotherDuck 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 Dun And Bradstreet and MotherDuck records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dun And Bradstreet and MotherDuck connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dun And Bradstreet–MotherDuck integration in-house.
Yes — Stacksync ships production-grade connectors for both Dun And Bradstreet and MotherDuck. 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 426 integrations available for Dun And Bradstreet and MotherDuck.