Skip to content
Data warehouse ⇄ CRM

ClickHouse to Dun And Bradstreet integration — real-time data sync

Keep ClickHouse and Dun And Bradstreet 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

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 ClickHouse and Dun And Bradstreet

Flow Dun And Bradstreet data into ClickHouse in real time — no exports, no schedulers, no custom scripts.

Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into ClickHouse, so ClickHouse 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. Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications, Company Information (Data Block) from Dun And Bradstreet land in ClickHouse as live tables, updated within seconds, and columns computed in ClickHouse 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.

Common use cases

  • 01 Pull D&B risk and credit signals (PAYDEX, Failure Score, D&B Rating) into a warehouse for credit-risk, vendor-risk, and third-party-risk analytics.
  • 02 Sync the D&B corporate family tree (parent and subsidiary DUNS) into the CRM so ABM and territory owners see full account hierarchies and roll pipeline up to the global ultimate.
  • 03 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
  • 04 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.

Common sync patterns

A single customer view

Join Dun And Bradstreet's relationship data with billing, product, and support data in ClickHouse to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

Deduplication and normalization done in ClickHouse can be written back, so warehouse-side cleanup actually fixes the CRM.

CRM analytics on live data

Accounts, contacts, and activity from Dun And Bradstreet are queryable in ClickHouse moments after they change, so dashboards stop lagging the reality they describe.

What you can sync between ClickHouse and Dun And Bradstreet

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.

ClickHouse objects Dun And Bradstreet objects How this pairing syncs
Databases Namespaces that group tables and scope permissions for sync users. 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. Databases is specific to ClickHouse and Company Information (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. Views is specific to ClickHouse and Principals & Contacts (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Materialized views is specific to ClickHouse and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. 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. Distributed tables is specific to ClickHouse and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. 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. Dictionaries is specific to ClickHouse and Identity Resolution (Match / cleanseMatch) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. 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. Tables (MergeTree family) is specific to ClickHouse and Criteria Search to Dun And Bradstreet — each maps to any object or custom field on the other side.

How changes propagate between ClickHouse and Dun And Bradstreet

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.

ClickHouse Dun And Bradstreet Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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 ClickHouse records.

Dun And Bradstreet ClickHouse Interval-based propagation

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 ClickHouse as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
What ships with ClickHouse ⇄ Dun And Bradstreet

Connect ClickHouse and Dun And Bradstreet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every ClickHouse–Dun And Bradstreet connection.

Real-time

Real-time sync

Changes in ClickHouse or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever ClickHouse or Dun And Bradstreet 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 ClickHouse or Dun And Bradstreet record.

Observability

Monitoring

Track your ClickHouse ⇄ Dun And Bradstreet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between ClickHouse and Dun And Bradstreet.

How the ClickHouse and Dun And Bradstreet connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

Dun And Bradstreet

Integration surface
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.
Change detection
Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
Capabilities
read
Rate limits
Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
How it works

How to connect ClickHouse to Dun And Bradstreet — 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.

  1. 01

    Connect your apps

    Authenticate ClickHouse and Dun And Bradstreet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    ClickHouse connected
    Dun And Bradstreet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ClickHouse and Dun And Bradstreet 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · ClickHouse ⇄ Dun And Bradstreet
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    ClickHouse Dun And Bradstreet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

ClickHouse and Dun And Bradstreet integration FAQ

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
CSA STAR
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 517 integrations available for ClickHouse and Dun And Bradstreet.

Popular · 7 of 517
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.