Firebolt to MySQL Integration

How Datrise loads Firebolt into MySQL

Datrise syncs Firebolt's databases, tables, aggregating indexes, query jobs, table schemas, and partitions 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

Firebolt: Cloud data warehouse tuned for fast analytics.

MySQL: Widely used OSS relational engine (InnoDB).

How Firebolt entities map to MySQL

Firebolt entity	MySQL object	Notes
databases	`firebolt_databases`	id PK · custom fields → JSON columns
tables	`firebolt_tables`	id PK · linked to firebolt_databases
aggregating indexes	`firebolt_aggregating_indexes`	id PK · linked to firebolt_databases
query jobs	`firebolt_query_jobs`	id PK · linked to firebolt_databases

FAQ

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