Question 1

Which Plain objects land in MySQL?

Accepted Answer

The catalogue is fixed rather than discovered. Core records are customers, companies, tenants, threads, users, tiers and label types. Conversation detail comes through as messages, notes, message attachments, message components, thread links, thread timeline events and thread discussions. Plain has no ticket object, so threads is the table to build against. Seven prebuilt report tables are also available if you want Plain's own support metrics rather than deriving them.

Question 2

How are Plain's nested fields stored?

Accepted Answer

In JSON columns. Plain represents labels as arrays and thread custom fields as an array of typed objects, and rather than flattening those into a wide table or escaping them into text they land as JSON you can query with MySQL's JSON functions. Several relationships avoid this entirely because they are flattened upstream: assignee identifier, name and type and the tier identifier and name arrive as ordinary scalar columns.

Question 3

How does incremental syncing behave?

Accepted Answer

Threads, customers, companies, tenants and several reports read against Plain's updated timestamp, so only changed records move and child rows are pulled for the threads that changed. Remaining objects are read in full each run. The checkpoint deliberately rewinds ten minutes from the run start to avoid losing records to clock differences, which means the same row can arrive twice. A primary key on the destination table lets the sync merge instead of appending.

Question 4

How large a Plain history can I load?

Accepted Answer

There is no cap imposed by the sync. Reads page through Plain's GraphQL connections fifty records at a time and continue while pages remain, so an initial backfill of several years of threads is a matter of duration rather than a hard limit. Transient failures during a long run are absorbed by a retry stack that retries up to ten times with waits between one second and two minutes.

Connect Plain with MySQL

Connect Plain and MySQL with Polytomic

Nested data in JSON columns

One table per Plain object

Runs on the cadence you set

Trusted by businesses worldwide

Step-by-step integration guide

Connect Plain in Polytomic

Connect MySQL in Polytomic

Create a sync between Plain and MySQL

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 MySQL?