Efficy CRM to Sisense Integration

How Datrise loads Efficy CRM into Sisense

Datrise syncs Efficy CRM's contacts, companies, opportunities, actions, campaigns, and service tickets into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

Efficy CRM: European CRM suite for sales, marketing, and service.

Sisense: Analytics platform with elastic data models and embedded analytics.

How Efficy CRM entities map to Sisense

Efficy CRM entity	Sisense object	Notes
contacts	`efficy_contacts`	id PK · custom fields → flattened columns for the cube
companies	`efficy_companies`	id PK · linked to efficy_contacts
opportunities	`efficy_opportunities`	id PK · linked to efficy_contacts
actions	`efficy_actions`	id PK · linked to efficy_contacts

FAQ

How does Datrise handle Efficy CRM's custom fields in Sisense?

Flexible values are stored as flattened columns for the cube, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Sisense types.

How does the Efficy CRM to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect Efficy CRM to Sisense 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.