DatriseAI-first ETL

Nimble Azure Synapse

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

How Datrise loads Nimble into Azure Synapse

Datrise syncs Nimble's relationship records, deals, tasks, and activity intelligence 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

Nimble: Relationship-focused CRM for SMB sales teams.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Nimble entities map to Azure Synapse

Nimble entityAzure Synapse objectNotes
relationship recordsnimble_relationship_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
dealsnimble_dealsid PK · linked to nimble_relationship_records
tasksnimble_tasksid PK · linked to nimble_relationship_records
activity intelligencenimble_activity_intelligencedatetime2 events

FAQ

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