DatriseAI-first ETL

Oracle CX DuckDB

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

How Datrise loads Oracle CX into DuckDB

Datrise syncs Oracle CX's enterprise CX entities across sales, service, and customer operations 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

Oracle CX: Enterprise customer experience suite with sales and service data.

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

How Oracle CX entities map to DuckDB

Oracle CX entityDuckDB objectNotes
enterprise CX entities across salesoracle_cx_enterprise_cx_entities_across_salesid PK · custom fields → JSON or STRUCT columns
serviceoracle_cx_serviceid PK · linked to oracle_cx_enterprise_cx_entities_across_sales
customer operationsoracle_cx_customer_operationsid PK · linked to oracle_cx_enterprise_cx_entities_across_sales

FAQ

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