DatriseAI-first ETL

Copper Azure Synapse

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

How Datrise loads Copper into Azure Synapse

Datrise syncs Copper's Google Workspace CRM entities, opportunities, and relationship timelines 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

Copper: Google Workspace-native CRM.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Copper entities map to Azure Synapse

Copper entityAzure Synapse objectNotes
Google Workspace CRM entitiescopper_google_workspace_crm_entitiesid PK · custom fields → NVARCHAR(MAX) JSON columns
opportunitiescopper_opportunitiesid PK · linked to copper_google_workspace_crm_entities
relationship timelinescopper_relationship_timelinesdatetime2 events

FAQ

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