Skip to content
Database ⇄ CRM

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

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

Treat Vitally like part of your database: its records live in DuckDB as real tables, and writes in either place sync to the other in seconds.

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 DuckDB, where it can be queried and joined like everything else.

Stacksync mirrors Note, Conversation, NPS Response, Custom Trait from Vitally into Database files, Schemas, Tables, Views in DuckDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Vitally 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.

Common use cases

  • 01 Push billing and subscription changes from an ERP or billing system into Vitally to keep success playbooks accurate.
  • 02 Keep CS tasks and notes aligned between Vitally and ticketing or project tools.
  • 03 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • 04 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.

Common sync patterns

Internal tools without API code

Back-office apps read and write the synced tables; Stacksync handles the Vitally API, limits, and retries.

Trigger workflows from CRM changes

Field and stage updates in Vitally arrive as row changes in DuckDB, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Vitally become tables in DuckDB you can join with application data directly.

What you can sync between DuckDB and Vitally

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.

DuckDB objects Vitally objects How this pairing syncs
Views SQL views used to shape or filter data for downstream consumers. Conversation Customer conversations logged in Vitally; activity objects include parent object details in the payload. Views is specific to DuckDB and Conversation to Vitally — each maps to any object or custom field on the other side.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. NPS Response NPS survey responses for account-health reporting. External files (Parquet/CSV/JSON) is specific to DuckDB and NPS Response to Vitally — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. Custom Trait Custom account and user traits for segmentation. Attached databases is specific to DuckDB and Custom Trait to Vitally — each maps to any object or custom field on the other side.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. Account Core customer account records with health scores and lifecycle traits; created, updated, retrieved, and listed via the REST API. Database files is specific to DuckDB and Account to Vitally — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. User End users tied to accounts, including activity and custom traits. Schemas is specific to DuckDB and User to Vitally — each maps to any object or custom field on the other side.
Tables Columnar tables created via SQL; the destination for materialized sync data. Organization Parent organizations for hierarchical B2B account structures. Tables is specific to DuckDB and Organization to Vitally — each maps to any object or custom field on the other side.

How changes propagate between DuckDB and Vitally

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.

DuckDB Vitally Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

DeliveryEach detected change is written to Vitally through its API, with automatic retries and rate-limit backoff.

Vitally DuckDB Sub-second propagation

DetectionVitally notifies Stacksync of record changes through webhook events. Incremental polling on updatedAt cursors.

DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • Vitally: Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
What ships with DuckDB ⇄ Vitally

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your DuckDB ⇄ Vitally sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between DuckDB and Vitally.

How the DuckDB and Vitally connectors work

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

Vitally

Integration surface
REST API with cursor-based pagination (sortable by createdAt/updatedAt)
Authentication
API key via Basic Auth; keys created in Settings -> Integrations -> REST API and individually revocable
Change detection
Incremental polling on updatedAt cursors; playbook-triggered webhooks can push events for near real-time updates
Capabilities
read · write · webhooks
Rate limits
Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
How it works

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

    Choose tables

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

DuckDB and Vitally 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.

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 390 integrations available for DuckDB and Vitally.

Popular · 8 of 390
All DuckDB integrations All Vitally 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