Omie CRM to Supabase Integration

How Datrise loads Omie CRM into Supabase

Datrise syncs Omie CRM's clients, opportunities, sales orders, invoices, products, and accounts receivable into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

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

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Omie CRM entities map to Supabase

Omie CRM entity	Supabase object	Notes
clients	`omie_clients`	id PK · custom fields → jsonb 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 Supabase?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Supabase types.

How does the Omie CRM to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Omie CRM to Supabase 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.