Recruitee to MySQL Integration

How Datrise loads Recruitee into MySQL

Datrise syncs Recruitee's candidates, offers, jobs, interviews, pipeline stages, and evaluations into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Recruitee: Collaborative hiring and candidate pipelines.

MySQL: Widely used OSS relational engine (InnoDB).

How Recruitee entities map to MySQL

Recruitee entity	MySQL object	Notes
candidates	`recruitee_candidates`	id PK · custom fields → JSON columns
offers	`recruitee_offers`	id PK · linked to recruitee_candidates
jobs	`recruitee_jobs`	id PK · linked to recruitee_candidates
interviews	`recruitee_interviews`	id PK · linked to recruitee_candidates

FAQ

How does Datrise handle Recruitee's custom fields in MySQL?

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

How does the Recruitee to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Recruitee to MySQL 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.