Lofty to GoodData Integration
AI-first ETL from Lofty into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Lofty into GoodData
Datrise syncs Lofty's leads, contacts, listings, property searches, smart plans, and tour requests into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Lofty: Real estate CRM with IDX search and AI lead nurture.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Lofty entities map to GoodData
| Lofty entity | GoodData object | Notes |
|---|---|---|
| leads | lofty_leads | id PK · custom fields → flattened columns |
| contacts | lofty_contacts | id PK · linked to lofty_leads |
| listings | lofty_listings | id PK · linked to lofty_leads |
| property searches | lofty_property_searches | id PK · linked to lofty_leads |
FAQ
How does Datrise handle Lofty's custom fields in GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Lofty to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Lofty
Early access
Connect Lofty to GoodData 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.