Two-way sync
Changes in Citus or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Citus 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. Citus is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables) in Ukg Pro need to exist as queryable Sequences, Distributed tables, Reference tables, Local tables in Citus 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 Sequences, Distributed tables, Reference tables, Local tables in Citus with Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations, Configuration Setup (Code Tables) 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.
Groups, departments, managers, and reporting lines from Ukg Pro stay consistent in Citus, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in Citus write onto the matching record in Ukg Pro where those fields are writable, keeping the people system enriched.
Records maintained in Ukg Pro land as queryable Sequences, Distributed tables, Reference tables, Local tables in Citus, so internal apps and dashboards read live data instead of a periodic export.
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.
| Citus objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | 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. | Local tables is specific to Citus and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Schemas is specific to Citus and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Views is specific to Citus and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | 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. | Sequences is specific to Citus and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | 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. | Distributed tables is specific to Citus and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Reference tables is specific to Citus 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.
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
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 Citus as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Ukg Pro connection.
Changes in Citus or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus 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 Citus or Ukg Pro record.
Track your Citus ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus 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 Citus 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 Citus 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 Citus and Ukg Pro: authenticate both systems, choose the objects to sync (such as Citus's Local tables and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Citus and Ukg Pro: Org and structure stay aligned; Computed and operational fields flow back; Mirror people records into the database. Groups, departments, managers, and reporting lines from Ukg Pro stay consistent in Citus, so hierarchy-driven logic and permissions don't drift.
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). 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.
Citus: Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards. Ukg Pro: Writes are modeled as HR events, not raw field edits: new hire (POST), termination (POST with a reason code that must match the tenant's configured reason table), and job or pay changes go through dedicated endpoints rather than a single PATCH. Stacksync's field mapping accounts for these differences between Citus and Ukg Pro without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Citus and Ukg Pro records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Ukg Pro connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Ukg Pro integration in-house.
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 432 integrations available for Citus and Ukg Pro.