DatriseAI-first ETL

Help Scout Azure Synapse

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

How Datrise loads Help Scout into Azure Synapse

Datrise syncs Help Scout'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

Help Scout: Customer service platform with ticket and conversation context.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Help Scout entities map to Azure Synapse

Help Scout entityAzure Synapse objectNotes
contactshelp_scout_contactsid PK · custom fields → NVARCHAR(MAX) JSON columns
accountshelp_scout_accountsid PK · linked to help_scout_contacts
dealshelp_scout_dealsid PK · linked to help_scout_contacts
activitieshelp_scout_activitiesdatetime2 events

FAQ

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