LionDesk to MySQL Integration

How Datrise loads LionDesk into MySQL

Datrise syncs LionDesk's leads, contacts, deals, drip campaigns, tasks, and video messages 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

LionDesk: Real estate CRM with video messaging and drip campaigns.

MySQL: Widely used OSS relational engine (InnoDB).

How LionDesk entities map to MySQL

LionDesk entity	MySQL object	Notes
leads	`liondesk_leads`	id PK · custom fields → JSON columns
contacts	`liondesk_contacts`	id PK · linked to liondesk_leads
deals	`liondesk_deals`	id PK · linked to liondesk_leads
drip campaigns	`liondesk_drip_campaigns`	id PK · linked to liondesk_leads

FAQ

How does Datrise handle LionDesk'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 LionDesk 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 LionDesk 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.