DatriseAI-first ETL

Outreach Azure Synapse

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

How Datrise loads Outreach into Azure Synapse

Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement 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

Outreach: Sales execution platform for sequence activity and pipeline outcomes.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Outreach entities map to Azure Synapse

Outreach entityAzure Synapse objectNotes
sequence activityoutreach_sequence_activitydatetime2 events
pipeline execution metricsoutreach_pipeline_execution_metricsid PK · linked to outreach_sequence_activity
sales engagement eventsoutreach_sales_engagement_eventsdatetime2 events

FAQ

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