DatriseAI-first ETL

Manatal to MicroStrategy Integration

AI-first ETL from Manatal into MicroStrategy. Governed entities, incremental sync, typed landing tables.

How Datrise loads Manatal into MicroStrategy

Datrise syncs Manatal's candidates, jobs, applications, pipeline stages, match scores, and clients into MicroStrategy as warehouse tables for MicroStrategy's schema objects. 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 warehouse tables behind attributes and metrics, so re-runs update only what changed. Date-partitioned facts. MicroStrategy maps attributes to columns, so Datrise lands stable keys and names so metrics don't break.

Ideal for large-scale enterprise reporting and governance.

Endpoints

Manatal: AI recruitment software with candidate scoring.

MicroStrategy: Enterprise BI with dossiers, governed metrics, and mobility.

How Manatal entities map to MicroStrategy

Manatal entityMicroStrategy objectNotes
candidatesmanatal_candidatesid PK · custom fields → flattened columns
jobsmanatal_jobsid PK · linked to manatal_candidates
applicationsmanatal_applicationsid PK · linked to manatal_candidates
pipeline stagesmanatal_pipeline_stagesid PK · linked to manatal_candidates

FAQ

How does Datrise handle Manatal's custom fields in MicroStrategy?

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 MicroStrategy types.

How does the Manatal to MicroStrategy sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the warehouse tables behind attributes and metrics.

Related pipelines

Early access

Connect Manatal to MicroStrategy 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.