SFTP Bulk to PostgreSQL Integration

How Datrise loads SFTP Bulk into PostgreSQL

Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats into PostgreSQL as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on each entity's updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative range partitioning by load date for high-volume tables. PostgreSQL folds unquoted identifiers to lowercase, so Datrise normalizes mixed-case source fields to snake_case.

Ideal for operational analytics and application backends that need fresh, queryable copies of your data.

Endpoints

SFTP Bulk: Bulk file drops delivered over SFTP.

PostgreSQL: Open-source relational database with strong SQL and extensions.

How SFTP Bulk entities map to PostgreSQL

SFTP Bulk entity	PostgreSQL object	Notes
files	`sftp_bulk_files`	id PK · custom fields → jsonb 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 PostgreSQL?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PostgreSQL types.

How does the SFTP Bulk to PostgreSQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on each entity's updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect SFTP Bulk to PostgreSQL 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.