Omie CRM to Azure Synapse Integration

How Datrise loads Omie CRM into Azure Synapse

Datrise syncs Omie CRM's clients, opportunities, sales orders, invoices, products, and accounts receivable 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

Omie CRM: Brazilian ERP and CRM for SMB sales and finance.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Omie CRM entities map to Azure Synapse

Omie CRM entity	Azure Synapse object	Notes
clients	`omie_clients`	id PK · custom fields → NVARCHAR(MAX) JSON columns
opportunities	`omie_opportunities`	id PK · linked to omie_clients
sales orders	`omie_sales_orders`	id PK · linked to omie_clients
invoices	`omie_invoices`	id PK · linked to omie_clients

FAQ

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