Merge to Birst Integration
AI-first ETL from Merge into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads Merge into Birst
Datrise syncs Merge's linked accounts, employees, candidates, contacts, invoices, and sync statuses into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.
Ideal for networked, governed enterprise BI.
Endpoints
Merge: Unified API across HR, CRM, and accounting tools.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How Merge entities map to Birst
| Merge entity | Birst object | Notes |
|---|---|---|
| linked accounts | merge_linked_accounts | id PK · custom fields → flattened columns |
| employees | merge_employees | id PK · linked to merge_linked_accounts |
| candidates | merge_candidates | id PK · linked to merge_linked_accounts |
| contacts | merge_contacts | id PK · linked to merge_linked_accounts |
FAQ
How does Datrise handle Merge's custom fields in Birst?
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 Birst types.
How does the Merge to Birst sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.
Related pipelines
More destinations for Merge
Early access
Connect Merge to Birst 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.