DatriseAI-first ETL

LionDesk Azure Synapse

AI-first ETL from LionDesk into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads LionDesk into Azure Synapse

Datrise syncs LionDesk's contacts, accounts, deals, activities, and lifecycle events into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

LionDesk: Real estate CRM for leads, listings, and agent follow-up.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How LionDesk entities map to Azure Synapse

LionDesk entityAzure Synapse objectNotes
contactsliondesk_contactsid PK · custom fields → NVARCHAR(MAX) JSON columns
accountsliondesk_accountsid PK · linked to liondesk_contacts
dealsliondesk_dealsid PK · linked to liondesk_contacts
activitiesliondesk_activitiesdatetime2 events

FAQ

How does Datrise handle LionDesk's custom fields in Azure Synapse?

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

How does the LionDesk to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect LionDesk to Azure Synapse 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.