DatriseAI-first ETL

PostgreSQL to Metabase Integration

AI-first ETL from PostgreSQL into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads PostgreSQL into Metabase

Datrise syncs PostgreSQL's tables, rows, schemas, indexes, sequences, and replication slots into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

PostgreSQL: Self-managed PostgreSQL instances.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How PostgreSQL entities map to Metabase

PostgreSQL entityMetabase objectNotes
tableshp_postgres_tablesid PK · custom fields → flattened columns for the question builder
rowshp_postgres_rowsid PK · linked to hp_postgres_tables
schemashp_postgres_schemasid PK · linked to hp_postgres_tables
indexeshp_postgres_indexesid PK · linked to hp_postgres_tables

FAQ

How does Datrise handle PostgreSQL's custom fields in Metabase?

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

How does the PostgreSQL to Metabase sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

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