Question 1

Why put Plain data in MotherDuck rather than a larger warehouse?

Accepted Answer

Because support data is usually modest in size and the questions are exploratory. Thread and message volumes for most teams sit comfortably within what DuckDB handles interactively, so you get fast iteration without provisioning capacity you will not use. It also makes the ETL cheap to run often, which matters when you want today's conversations rather than yesterday's, and joining a billing extract alongside is a small step rather than a project.

Question 2

How do Plain's nested structures arrive in DuckDB?

Accepted Answer

As typed LIST and STRUCT columns rather than JSON text, which is a good fit because Plain leans on nesting for labels and thread fields. Timestamps convert from ISO 8601 into native DuckDB timestamps. Worth knowing that identifiers, both Plain's own and external ones, are strings rather than integers, and that some union types carry a __typename discriminator column through to the destination.

Question 3

Which Plain objects can I sync?

Accepted Answer

A fixed list. Customers, companies, tenants, threads, users, tiers and label types cover the core records; messages, notes, attachments, message components, thread links, timeline events and discussions cover conversation detail. Plain has no ticket object, so threads is what you build reporting on. Seven prebuilt reports are also available, including new thread daily counts by label, open thread counts by channel and priority, agent daily activity, and SLA compliance percentage.

Question 4

How much moves on each run?

Accepted Answer

Only what changed, for the main objects. Threads, customers, companies, tenants and several reports read incrementally against Plain's updated timestamp, and each run starts its window ten minutes before the previous one finished so records updated near a boundary are not missed. Child records are fetched for the threads that changed. That overlap means the same record can arrive more than once, so the sync should merge on the key rather than append.

Connect Plain with MotherDuck

Connect Plain and MotherDuck with Polytomic

LIST and STRUCT preserved

No cluster to size

Plain's own reports included

Trusted by businesses worldwide

Step-by-step integration guide

Connect Plain in Polytomic

Connect MotherDuck in Polytomic

Create a sync between Plain and MotherDuck

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Plain with MotherDuck?