Workday RaaS to DuckDB Integration

How Datrise loads Workday RaaS into DuckDB

Datrise syncs Workday RaaS's workers, organizations, job profiles, compensation records, absence records, and report rows 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

Workday RaaS: Workday HR reports delivered as a service.

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

How Workday RaaS entities map to DuckDB

Workday RaaS entity	DuckDB object	Notes
workers	`workday_raas_workers`	id PK · custom fields → JSON or STRUCT columns
organizations	`workday_raas_organizations`	id PK · linked to workday_raas_workers
job profiles	`workday_raas_job_profiles`	id PK · linked to workday_raas_workers
compensation records	`workday_raas_compensation_records`	id PK · linked to workday_raas_workers

FAQ

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