JSON File to MySQL Integration

How Datrise loads JSON File into MySQL

Datrise syncs JSON File's documents, nested objects, arrays, keys, file batches, and schemas 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

JSON File: Structured JSON documents from exports and drops.

MySQL: Widely used OSS relational engine (InnoDB).

How JSON File entities map to MySQL

JSON File entity	MySQL object	Notes
documents	`json_file_documents`	id PK · custom fields → JSON columns
nested objects	`json_file_nested_objects`	id PK · linked to json_file_documents
arrays	`json_file_arrays`	id PK · linked to json_file_documents
keys	`json_file_keys`	id PK · linked to json_file_documents

FAQ

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