DatriseAI-first ETL

Apollo Azure Synapse

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

How Datrise loads Apollo into Azure Synapse

Datrise syncs Apollo's sales intelligence records, account engagement, and outbound activity 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

Apollo: Sales intelligence and engagement platform with account-level activity.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Apollo entities map to Azure Synapse

Apollo entityAzure Synapse objectNotes
sales intelligence recordsapollo_sales_intelligence_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
account engagementapollo_account_engagementid PK · linked to apollo_sales_intelligence_records
outbound activityapollo_outbound_activitydatetime2 events

FAQ

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