DatriseAI-first ETL

Mambu to Metabase Integration

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

How Datrise loads Mambu into Metabase

Datrise syncs Mambu's clients, loan accounts, deposit accounts, transactions, repayments, and products 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

Mambu: Cloud core banking and lending engine.

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

How Mambu entities map to Metabase

Mambu entityMetabase objectNotes
clientsmambu_clientsid PK · custom fields → flattened columns for the question builder
loan accountsmambu_loan_accountsid PK · linked to mambu_clients
deposit accountsmambu_deposit_accountsid PK · linked to mambu_clients
transactionsmambu_transactionsid PK · linked to mambu_clients

FAQ

How does Datrise handle Mambu'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 Mambu to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Mambu 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.