SFTP Bulk to MySQL Integration

How Datrise loads SFTP Bulk into MySQL

Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats 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

SFTP Bulk: Bulk file drops delivered over SFTP.

MySQL: Widely used OSS relational engine (InnoDB).

How SFTP Bulk entities map to MySQL

SFTP Bulk entity	MySQL object	Notes
files	`sftp_bulk_files`	id PK · custom fields → JSON columns
directories	`sftp_bulk_directories`	id PK · linked to sftp_bulk_files
rows	`sftp_bulk_rows`	id PK · linked to sftp_bulk_files
file batches	`sftp_bulk_file_batches`	id PK · linked to sftp_bulk_files

FAQ

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