DatriseAI-first ETL

Sellsy Azure Synapse

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

How Datrise loads Sellsy into Azure Synapse

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

Sellsy: European CRM for SMB and mid-market sales teams.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Sellsy entities map to Azure Synapse

Sellsy entityAzure Synapse objectNotes
contactssellsy_contactsid PK · custom fields → NVARCHAR(MAX) JSON columns
accountssellsy_accountsid PK · linked to sellsy_contacts
dealssellsy_dealsid PK · linked to sellsy_contacts
activitiessellsy_activitiesdatetime2 events

FAQ

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