Skip to content
Data warehouse ⇄ CRM

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

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

Sync Vitally into MotherDuck continuously and push warehouse results back onto CRM records, one two-way connection instead of two pipelines.

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. Conversation, NPS Response, Custom Trait, Account from Vitally land in MotherDuck as live tables, updated within seconds, and columns computed in MotherDuck write back to fields in Vitally. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

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 Share curated, synced datasets with other teams through read-only database shares
  • 04 Land CRM and operational database records in MotherDuck so a small team gets warehouse-style analytics without cluster management

Common sync patterns

A single customer view

Join Vitally's relationship data with billing, product, and support data in MotherDuck to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

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

CRM analytics on live data

Accounts, contacts, and activity from Vitally are queryable in MotherDuck moments after they change, so dashboards stop lagging the reality they describe.

What you can sync between MotherDuck 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.

MotherDuck objects Vitally objects How this pairing syncs
Schemas Namespaces within a database used to organize synced tables. Account Core customer account records with health scores and lifecycle traits; created, updated, retrieved, and listed via the REST API. Schemas is specific to MotherDuck and Account to Vitally — each maps to any object or custom field on the other side.
Tables The main landing target for synced records and source for analysis. User End users tied to accounts, including activity and custom traits. Tables is specific to MotherDuck and User to Vitally — each maps to any object or custom field on the other side.
Views Modeled projections used as outbound sync sources. Organization Parent organizations for hierarchical B2B account structures. Views is specific to MotherDuck and Organization to Vitally — each maps to any object or custom field on the other side.
Database Shares Read-only copies of a database shared with other users or teams. Task CS tasks and follow-ups, readable and writable for workflow sync. Database Shares is specific to MotherDuck and Task to Vitally — each maps to any object or custom field on the other side.
Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. Note Account and user notes captured by success teams. Attached Local DuckDB Databases is specific to MotherDuck and Note to Vitally — each maps to any object or custom field on the other side.
Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Conversation Customer conversations logged in Vitally; activity objects include parent object details in the payload. Databases is specific to MotherDuck and Conversation to Vitally — each maps to any object or custom field on the other side.

How changes propagate between MotherDuck 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.

MotherDuck Vitally Interval-based propagation

DetectionStacksync polls MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.

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

Vitally MotherDuck Sub-second propagation

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

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

Rate-limit considerations

  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
  • Vitally: Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
What ships with MotherDuck ⇄ Vitally

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the MotherDuck and Vitally connectors work

MotherDuck

Integration surface
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
Change detection
Polling; no log-based CDC or webhook surface is exposed
Capabilities
read · write
Rate limits
Subject to the platform's compute and concurrency limits rather than per-request API rate limits
MotherDuck setup guide

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 MotherDuck 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 MotherDuck 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
    MotherDuck connected
    Vitally connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

Popular · 8 of 390
All MotherDuck 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