Skip to content
Data warehouse ⇄ Database

ClickHouse to DuckDB integration — real-time, two-way sync

Keep ClickHouse and DuckDB 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 DuckDB

Connect DuckDB and ClickHouse with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want DuckDB's rows in ClickHouse, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in DuckDB where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in DuckDB sync into ClickHouse in real time, and result tables in ClickHouse sync back into DuckDB, with schema and type mapping between the two systems handled for you.

Common use cases

  • Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
  • Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
  • Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.

Fresh analytics without loading windows

Because changes stream continuously, analysts query current data instead of waiting for last night's load.

Offload heavy reads

Point analytical queries at the synced copy in ClickHouse and keep DuckDB focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from DuckDB land in ClickHouse as they change, replacing hand-built CDC and batch extract jobs.

What you can sync between ClickHouse and DuckDB

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 DuckDB objects
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Attached databases Additional database files or external systems attached into one session for cross-source queries.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Schemas Namespaces within a database used to organize tables in sync outputs.
Databases Namespaces that group tables and scope permissions for sync users. Tables Columnar tables created via SQL; the destination for materialized sync data.
Views Saved queries used as curated, read-only sync sources. Views SQL views used to shape or filter data for downstream consumers.
What ships with ClickHouse ⇄ DuckDB

Connect ClickHouse and DuckDB for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your ClickHouse ⇄ DuckDB 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 DuckDB.

How the ClickHouse and DuckDB 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

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O
How it works

How to connect ClickHouse to DuckDB — 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 DuckDB 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
    DuckDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the ClickHouse and DuckDB 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 ⇄ DuckDB
    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 DuckDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

ClickHouse and DuckDB integration FAQ

SECURITY

Security teams love 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for ClickHouse and DuckDB.

Popular · 8 of 386
All ClickHouse integrations All DuckDB integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own