DatriseAI-first ETL

Harvest Azure Synapse

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

How Datrise loads Harvest into Azure Synapse

Datrise syncs Harvest's time entries, projects, clients, invoices, and utilization 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

Harvest: Time tracking and project profitability for services teams.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Harvest entities map to Azure Synapse

Harvest entityAzure Synapse objectNotes
time entriesharvest_time_entriesid PK · custom fields → NVARCHAR(MAX) JSON columns
projectsharvest_projectsid PK · linked to harvest_time_entries
clientsharvest_clientsid PK · linked to harvest_time_entries
invoicesharvest_invoicesid PK · linked to harvest_time_entries

FAQ

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