Help Scout to MySQL Integration

How Datrise loads Help Scout into MySQL

Datrise syncs Help Scout's conversations, customers, mailboxes, threads, tags, and satisfaction ratings 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

Help Scout: Shared inbox help desk with customer conversation history.

MySQL: Widely used OSS relational engine (InnoDB).

How Help Scout entities map to MySQL

Help Scout entity	MySQL object	Notes
conversations	`help_scout_conversations`	id PK · custom fields → JSON columns
customers	`help_scout_customers`	id PK · linked to help_scout_conversations
mailboxes	`help_scout_mailboxes`	id PK · linked to help_scout_conversations
threads	`help_scout_threads`	id PK · linked to help_scout_conversations

FAQ

How does Datrise handle Help Scout'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 Help Scout 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 Help Scout 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.