Omie CRM to MySQL Integration

How Datrise loads Omie CRM into MySQL

Datrise syncs Omie CRM's clients, opportunities, sales orders, invoices, products, and accounts receivable into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

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

MySQL: Widely used OSS relational engine (InnoDB).

How Omie CRM entities map to MySQL

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

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

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

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

Related pipelines

Early access

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