DatriseAI-first ETL

Nectar CRM Azure Synapse

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

How Datrise loads Nectar CRM into Azure Synapse

Datrise syncs Nectar CRM'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

Nectar CRM: CRM widely used in Latin America for sales pipeline and customer ops.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Nectar CRM entities map to Azure Synapse

Nectar CRM entityAzure Synapse objectNotes
contactsnectar_crm_contactsid PK · custom fields → NVARCHAR(MAX) JSON columns
accountsnectar_crm_accountsid PK · linked to nectar_crm_contacts
dealsnectar_crm_dealsid PK · linked to nectar_crm_contacts
activitiesnectar_crm_activitiesdatetime2 events

FAQ

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