DatriseAI-first ETL

Kyriba to PlanetScale Integration

AI-first ETL from Kyriba into PlanetScale. Governed entities, incremental sync, typed landing tables.

How Datrise loads Kyriba into PlanetScale

Datrise syncs Kyriba's bank accounts, cash positions, payments, transactions, forecasts, and bank statements into PlanetScale 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.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Kyriba: Treasury, cash, and liquidity management.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Kyriba entities map to PlanetScale

Kyriba entityPlanetScale objectNotes
bank accountskyriba_bank_accountsid PK · custom fields → JSON columns
cash positionskyriba_cash_positionsid PK · linked to kyriba_bank_accounts
paymentskyriba_paymentsid PK · linked to kyriba_bank_accounts
transactionskyriba_transactionsid PK · linked to kyriba_bank_accounts

FAQ

How does Datrise handle Kyriba's custom fields in PlanetScale?

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 PlanetScale types.

How does the Kyriba to PlanetScale 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 Kyriba to PlanetScale 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.