DatriseAI-first ETL

Intacct to DuckDB Integration

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

How Datrise loads Intacct into DuckDB

Datrise syncs Intacct's journal entries, accounts, invoices, bills, customers, and GL transactions into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Intacct: Cloud financial management and general ledger.

DuckDB: In-process analytics database for fast local OLAP.

How Intacct entities map to DuckDB

Intacct entityDuckDB objectNotes
journal entriesintacct_journal_entriesid PK · custom fields → JSON or STRUCT 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 DuckDB?

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

How does the Intacct to DuckDB sync stay up to date?

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

Connect Intacct to DuckDB 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.