DatriseAI-first ETL

SFTP Bulk to PlanetScale Integration

AI-first ETL from SFTP Bulk into PlanetScale. Governed entities, incremental sync, typed landing tables.

How Datrise loads SFTP Bulk into PlanetScale

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

SFTP Bulk: Bulk file drops delivered over SFTP.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How SFTP Bulk entities map to PlanetScale

SFTP Bulk entityPlanetScale objectNotes
filessftp_bulk_filesid PK · custom fields → JSON columns
directoriessftp_bulk_directoriesid PK · linked to sftp_bulk_files
rowssftp_bulk_rowsid PK · linked to sftp_bulk_files
file batchessftp_bulk_file_batchesid PK · linked to sftp_bulk_files

FAQ

How does Datrise handle SFTP Bulk's custom fields in PlanetScale?

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 PlanetScale types.

How does the SFTP Bulk to PlanetScale 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 PlanetScale 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.