DatriseAI-first ETL

Lofty to Metabase Integration

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

How Datrise loads Lofty into Metabase

Datrise syncs Lofty's leads, contacts, listings, property searches, smart plans, and tour requests 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

Lofty: Real estate CRM with IDX search and AI lead nurture.

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

How Lofty entities map to Metabase

Lofty entityMetabase objectNotes
leadslofty_leadsid PK · custom fields → flattened columns for the question builder
contactslofty_contactsid PK · linked to lofty_leads
listingslofty_listingsid PK · linked to lofty_leads
property searcheslofty_property_searchesid PK · linked to lofty_leads

FAQ

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

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

Related pipelines

Early access

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