Kyriba to MySQL Integration
AI-first ETL from Kyriba into MySQL. Governed entities, incremental sync, typed landing tables.
How Datrise loads Kyriba into MySQL
Datrise syncs Kyriba's bank accounts, cash positions, payments, transactions, forecasts, and bank statements 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
Kyriba: Treasury, cash, and liquidity management.
MySQL: Widely used OSS relational engine (InnoDB).
How Kyriba entities map to MySQL
| Kyriba entity | MySQL object | Notes |
|---|---|---|
| bank accounts | kyriba_bank_accounts | id PK · custom fields → JSON columns |
| cash positions | kyriba_cash_positions | id PK · linked to kyriba_bank_accounts |
| payments | kyriba_payments | id PK · linked to kyriba_bank_accounts |
| transactions | kyriba_transactions | id PK · linked to kyriba_bank_accounts |
FAQ
How does Datrise handle Kyriba'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 Kyriba 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
More destinations for Kyriba
Early access
Connect Kyriba 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.