EspoCRM → Metabase
AI-first ETL from EspoCRM into Metabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads EspoCRM into Metabase
Datrise syncs EspoCRM's pipeline entities, custom objects, and process automation events 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
EspoCRM: Open-source CRM for pipeline management and custom entity modeling.
Metabase: Open-source analytics with questions, dashboards, and embedded insights.
How EspoCRM entities map to Metabase
| EspoCRM entity | Metabase object | Notes |
|---|---|---|
| pipeline entities | espocrm_pipeline_entities | id PK · custom fields → flattened columns for the question builder |
| custom objects | espocrm_custom_objects | id PK · linked to espocrm_pipeline_entities |
| process automation events | espocrm_process_automation_events | temporal columns for trends events |
FAQ
How does Datrise handle EspoCRM'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 EspoCRM to Metabase sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for EspoCRM
Early access
Connect EspoCRM 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.