DatriseAI-first ETL

Intacct to PlanetScale Integration

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

How Datrise loads Intacct into PlanetScale

Datrise syncs Intacct's journal entries, accounts, invoices, bills, customers, and GL transactions 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

Intacct: Cloud financial management and general ledger.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Intacct entities map to PlanetScale

Intacct entityPlanetScale objectNotes
journal entriesintacct_journal_entriesid PK · custom fields → JSON columns
accountsintacct_accountsid PK · linked to intacct_journal_entries
invoicesintacct_invoicesid PK · linked to intacct_journal_entries
billsintacct_billsid PK · linked to intacct_journal_entries

FAQ

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