Skip to content
CRM ⇄ Data warehouse

6sense to MotherDuck integration — real-time data sync

Keep 6sense 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.

  • 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 6sense and MotherDuck

Flow 6sense data into MotherDuck in real time — no exports, no schedulers, no custom scripts.

6sense 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 6sense — 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. People / Contacts, Reach Scores, Accounts, Segments from 6sense land in MotherDuck as live tables, updated within seconds, and columns computed in MotherDuck write back to fields in 6sense. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • 01 Feed in-market account lists to sales engagement tools to start sequences automatically.
  • 02 Sync 6sense buying stage and intent scores onto CRM accounts so sellers prioritize in-market targets.
  • 03 Sync modeled MotherDuck tables outward to operational tools for activation
  • 04 Share curated, synced datasets with other teams through read-only database shares

Common sync patterns

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 6sense are queryable in MotherDuck moments after they change, so dashboards stop lagging the reality they describe.

Scores and segments back on the record

Lead scores, churn risk, or usage segments computed in MotherDuck appear as fields in 6sense, where the people working accounts actually see them.

What you can sync between 6sense and MotherDuck

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.

6sense objects MotherDuck objects How this pairing syncs
Intent Signals Keyword-level research activity used to flag in-market accounts. Database Shares Read-only copies of a database shared with other users or teams. Intent Signals is specific to 6sense and Database Shares to MotherDuck — each maps to any object or custom field on the other side.
People / Contacts Persona and contact data surfaced for accounts, used to build outreach lists. Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. People / Contacts is specific to 6sense and Attached Local DuckDB Databases to MotherDuck — each maps to any object or custom field on the other side.
Reach Scores Model scores reflecting the level and recency of outreach to an account or contact, used to prioritize follow-up. Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. Reach Scores is specific to 6sense and Databases to MotherDuck — each maps to any object or custom field on the other side.
Accounts Company records enriched with firmographics and intent data, matched to CRM accounts. Schemas Namespaces within a database used to organize synced tables. Accounts is specific to 6sense and Schemas to MotherDuck — each maps to any object or custom field on the other side.
Segments Dynamic account lists built from intent and fit criteria, read out to drive targeting. Tables The main landing target for synced records and source for analysis. Segments is specific to 6sense and Tables to MotherDuck — each maps to any object or custom field on the other side.
Buying Stage Scores Model-predicted stage per account, synced onto CRM records for prioritization. Views Modeled projections used as outbound sync sources. Buying Stage Scores is specific to 6sense and Views to MotherDuck — each maps to any object or custom field on the other side.

How changes propagate between 6sense and MotherDuck

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.

6sense MotherDuck Interval-based propagation

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

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

MotherDuck 6sense Interval-based propagation

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

Delivery6sense does not accept inbound record writes, so this direction carries requests rather than records: 6sense's output flows back as field updates on the originating MotherDuck records.

Rate-limit considerations

  • 6sense: Subject to the platform's API rate limits, which vary by contracted API package.
  • MotherDuck: Subject to the platform's compute and concurrency limits rather than per-request API rate limits.
What ships with 6sense ⇄ MotherDuck

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the 6sense and MotherDuck connectors work

6sense

Integration surface
REST API
Authentication
API key (token passed in request headers)
Change detection
Polling; scores and segment membership are typically refreshed on the platform's model update cadence
Capabilities
read
Rate limits
Subject to the platform's API rate limits, which vary by contracted API package

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
How it works

How to connect 6sense to MotherDuck — 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 6sense 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    6sense connected
    MotherDuck connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the 6sense 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · 6sense ⇄ MotherDuck
    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
    6sense MotherDuck
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

6sense and MotherDuck 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
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 375 integrations available for 6sense and MotherDuck.

Popular · 6 of 375
All 6sense integrations All MotherDuck 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