Two-way sync
Changes in MotherDuck or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep MotherDuck 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.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Ukg Pro is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in MotherDuck next to everything else the company measures.
Stacksync syncs Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details) from Ukg Pro into tables in MotherDuck continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in MotherDuck, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Ukg Pro where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Segments, rollups, or risk flags computed in MotherDuck sync back onto the matching records in Ukg Pro, where the HR team sees them in the system they already use.
People and organization records from Ukg Pro arrive in MotherDuck as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Analysts combine Ukg Pro's workforce records with finance, product, or operational data already in MotherDuck for reporting the HR system cannot produce on its own.
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.
| MotherDuck objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Attached Local DuckDB Databases Local files attached alongside cloud databases for hybrid queries. | 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. | Attached Local DuckDB Databases is specific to MotherDuck and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Databases Cloud-hosted DuckDB databases that scope a sync's reads and writes. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Databases is specific to MotherDuck and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize synced tables. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Schemas is specific to MotherDuck and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Tables The main landing target for synced records and source for analysis. | Compensation Details Effective-dated pay rate and salary; usually read into a warehouse for comp reporting and writable as new dated changes through the compensation endpoints. | Tables is specific to MotherDuck and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Views Modeled projections used as outbound sync sources. | Payroll (Pay Statements, Direct Deposit, Earnings) Pay statements, direct-deposit accounts, and earnings history; read-only pay data replicated into finance and warehouse systems for labor-cost reporting. | Views is specific to MotherDuck and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Database Shares Read-only copies of a database shared with other users or teams. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Database Shares is specific to MotherDuck and Terminations 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 MotherDuck for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
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 MotherDuck as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MotherDuck–Ukg Pro connection.
Changes in MotherDuck or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MotherDuck 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 MotherDuck or Ukg Pro record.
Track your MotherDuck ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MotherDuck 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 MotherDuck 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 MotherDuck 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 MotherDuck and Ukg Pro: authenticate both systems, choose the objects to sync (such as MotherDuck's Attached Local DuckDB Databases and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both MotherDuck and Ukg Pro. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on MotherDuck: Polling; no log-based CDC or webhook surface is exposed. 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 MotherDuck side: Attached Local DuckDB Databases, Databases, Schemas, Tables, plus custom fields where MotherDuck exposes them. On the Ukg Pro side: Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details). 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 MotherDuck and Ukg Pro: Write-back of computed values; HR data in the warehouse, minus the pipeline; Headcount and cost joined with everything else. Segments, rollups, or risk flags computed in MotherDuck sync back onto the matching records in Ukg Pro, where the HR team sees them in the system they already use.
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 449 integrations available for MotherDuck and Ukg Pro.