DatriseAI-first ETL

PipeRun Azure Synapse

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

How Datrise loads PipeRun into Azure Synapse

Datrise syncs PipeRun'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

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

Azure Synapse: Microsoft analytics workspace with SQL pools.

How PipeRun entities map to Azure Synapse

PipeRun entityAzure Synapse objectNotes
contactspiperun_contactsid PK · custom fields → NVARCHAR(MAX) JSON columns
accountspiperun_accountsid PK · linked to piperun_contacts
dealspiperun_dealsid PK · linked to piperun_contacts
activitiespiperun_activitiesdatetime2 events

FAQ

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