Moskit CRM to MySQL Integration

How Datrise loads Moskit CRM into MySQL

Datrise syncs Moskit CRM's contacts, companies, deals, funnel stages, tasks, and sales goals 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

Moskit CRM: Sales CRM for Brazilian inside-sales teams.

MySQL: Widely used OSS relational engine (InnoDB).

How Moskit CRM entities map to MySQL

Moskit CRM entity	MySQL object	Notes
contacts	`moskit_contacts`	id PK · custom fields → JSON columns
companies	`moskit_companies`	id PK · linked to moskit_contacts
deals	`moskit_deals`	id PK · linked to moskit_contacts
funnel stages	`moskit_funnel_stages`	id PK · linked to moskit_contacts

FAQ

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