Two-way sync
Changes in Exasol or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol 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 Exasol next to everything else the company measures.
Stacksync syncs Employee (Person Details), Employment Details, Job / Position History, Compensation Details from Ukg Pro into tables in Exasol continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Exasol, 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.
People and organization records from Ukg Pro arrive in Exasol 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 Exasol for reporting the HR system cannot produce on its own.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
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.
| Exasol objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-only query surfaces often used as curated sources for reverse ETL. | 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. | Views is specific to Exasol and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | 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. | Virtual schemas is specific to Exasol and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | UDF scripts is specific to Exasol and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Users and roles Grant read/write access for the dedicated integration account. | 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. | Users and roles is specific to Exasol and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Schemas is specific to Exasol and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | 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. | Tables is specific to Exasol and Employee (Person Details) 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 Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
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 Exasol as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Ukg Pro connection.
Changes in Exasol or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol 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 Exasol or Ukg Pro record.
Track your Exasol ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol 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 Exasol 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 Exasol 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 Exasol and Ukg Pro: authenticate both systems, choose the objects to sync (such as Exasol's Views and Virtual schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. 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 Exasol side: Tables, Views, Virtual schemas, UDF scripts, plus custom fields where Exasol exposes them. On the Ukg Pro side: Employee (Person Details), Employment Details, Job / Position History, Compensation 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 Exasol and Ukg Pro: HR data in the warehouse, minus the pipeline; Headcount and cost joined with everything else; Fresh data instead of last night's load. People and organization records from Ukg Pro arrive in Exasol as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). 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 432 integrations available for Exasol and Ukg Pro.