Two-way sync
Changes in DuckDB or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Ukg Pro in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Ukg Pro is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. DuckDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA) in Ukg Pro need to exist as queryable Database files, Schemas, Tables, Views in DuckDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Database files, Schemas, Tables, Views in DuckDB with Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA) in Ukg Pro field by field, in real time. You decide which system owns which fields — Ukg Pro typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Records maintained in Ukg Pro land as queryable Database files, Schemas, Tables, Views in DuckDB, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA) replicate into DuckDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| DuckDB objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces within a database used to organize tables in sync outputs. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Schemas is specific to DuckDB and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Configuration Setup (Code Tables) Reference data such as jobs, locations, positions, earnings, and deduction codes; used to resolve and validate field values when mapping records during sync. | Tables is specific to DuckDB and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Views is specific to DuckDB and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Employee (Person Details) Core worker record with demographics and identifiers; read by listing employee IDs then fetching each profile, and created on hire via the personnel/onboarding endpoints. | External files (Parquet/CSV/JSON) is specific to DuckDB and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Attached databases is specific to DuckDB and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Database files is specific to DuckDB and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is written to Ukg Pro through its API, with automatic retries and rate-limit backoff.
DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.
DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Ukg Pro connection.
Changes in DuckDB or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Ukg Pro data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Ukg Pro record.
Track your DuckDB ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Ukg Pro.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate DuckDB and Ukg Pro with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the DuckDB and Ukg Pro objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Ukg Pro: authenticate both systems, choose the objects to sync (such as DuckDB's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On Ukg Pro: No CDC stream. UKG Pro publishes Pro HCM Webhook Events for changes such as new hire, employee and job detail changes, termination, and PTO, which Stacksync subscribes to for near-real-time triggers; bulk and historical loads use paged reads with each service's modified-since filters. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the DuckDB side: Database files, Schemas, Tables, Views, plus custom fields where DuckDB exposes them. On the Ukg Pro side: Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for DuckDB and Ukg Pro: Mirror people records into the database; One directory of record; Reporting and analytics on current data. Records maintained in Ukg Pro land as queryable Database files, Schemas, Tables, Views in DuckDB, so internal apps and dashboards read live data instead of a periodic export.
DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). Ukg Pro: REST API (UKG Pro HCM REST services) with separate Onboarding and Recruiting REST APIs, plus legacy SOAP-based UKG Pro Web Services. Authentication: Core HCM REST APIs use HTTP Basic authentication with a dedicated web service account, plus a Customer API Key and a User API Key sent as headers (found under System Configuration > Security > Service Account Administration); the Onboarding and Recruiting REST APIs instead require a bearer Authorization Token from the token endpoint. Stacksync manages authentication, retries, and rate limits on both sides.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 448 integrations available for DuckDB and Ukg Pro.