Odoo CRM → GoodData
AI-first ETL from Odoo CRM into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Odoo CRM into GoodData
Datrise syncs Odoo CRM's modular CRM entities, opportunities, and revenue process data 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
Odoo CRM: Modular CRM in the Odoo suite for leads, opportunities, and revenue.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Odoo CRM entities map to GoodData
| Odoo CRM entity | GoodData object | Notes |
|---|---|---|
| modular CRM entities | odoo_crm_modular_crm_entities | id PK · custom fields → flattened columns |
| opportunities | odoo_crm_opportunities | id PK · linked to odoo_crm_modular_crm_entities |
| revenue process data | odoo_crm_revenue_process_data | id PK · linked to odoo_crm_modular_crm_entities |
FAQ
How does Datrise handle Odoo CRM'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 Odoo CRM to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Odoo CRM
Early access
Connect Odoo CRM 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.