DatriseAI-first ETL

SFTP Bulk to Qlik Integration

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

How Datrise loads SFTP Bulk into Qlik

Datrise syncs SFTP Bulk's files, directories, rows, file batches, modification timestamps, and file formats into Qlik as tables loaded into Qlik's associative engine (often via QVD). Flexible or custom fields land in flattened columns for the data model, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental QVD loads merged on stable id, so re-runs update only what changed. QVD files per entity and load date. Qlik's associative model joins on identically named fields, so Datrise standardizes key names so associations link correctly.

Ideal for associative, in-memory exploration in Qlik Sense.

Endpoints

SFTP Bulk: Bulk file drops delivered over SFTP.

Qlik: Associative analytics with Qlik Sense apps and governed data models.

How SFTP Bulk entities map to Qlik

SFTP Bulk entityQlik objectNotes
filessftp_bulk_filesid PK · custom fields → flattened columns for the data model
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 Qlik?

Flexible values are stored as flattened columns for the data model, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Qlik types.

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

It runs incrementally — Datrise uses incremental QVD loads merged on stable id.

Related pipelines

Early access

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