Customer.io to MySQL Integration

How Datrise loads Customer.io into MySQL

Datrise syncs Customer.io's people, segments, campaigns, message events, attributes, and broadcasts into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Customer.io: Behavioral messaging across email, push, and SMS.

MySQL: Widely used OSS relational engine (InnoDB).

How Customer.io entities map to MySQL

Customer.io entity	MySQL object	Notes
people	`customerio_people`	id PK · custom fields → JSON columns
segments	`customerio_segments`	id PK · linked to customerio_people
campaigns	`customerio_campaigns`	id PK · linked to customerio_people
message events	`customerio_message_events`	DATETIME/TIMESTAMP events

FAQ

How does Datrise handle Customer.io's custom fields in MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Customer.io to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Customer.io to MySQL the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.