Two-way sync
Changes in Elasticsearch or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Elasticsearch 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. Elasticsearch is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details in Ukg Pro need to exist as queryable Index templates, Indices, Documents, Index mappings in Elasticsearch 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 Index templates, Indices, Documents, Index mappings in Elasticsearch with Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment Details 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 Elasticsearch, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in Elasticsearch 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 Index templates, Indices, Documents, Index mappings in Elasticsearch, 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.
| Elasticsearch objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Data streams Append-only targets for time-series or event data pushed from source systems. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Data streams is specific to Elasticsearch and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Ingest pipelines Server-side transforms applied to documents as a sync writes them. | 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. | Ingest pipelines is specific to Elasticsearch and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Index templates Reusable settings and mappings applied automatically to new indices a sync creates. | 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. | Index templates is specific to Elasticsearch and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Indices Target containers for synced records; each holds a table-like collection of JSON documents. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Indices is specific to Elasticsearch and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Documents The unit of sync; JSON records created, updated, and deleted by _id. | 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. | Documents is specific to Elasticsearch and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Index mappings Field type definitions that determine how synced fields are indexed and queried. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Index mappings is specific to Elasticsearch and Time & Attendance (UTA) 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 Elasticsearch for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or sequence fields.
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 written to Elasticsearch through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Elasticsearch–Ukg Pro connection.
Changes in Elasticsearch or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Elasticsearch 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 Elasticsearch or Ukg Pro record.
Track your Elasticsearch ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Elasticsearch 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 Elasticsearch 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 Elasticsearch 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 Elasticsearch and Ukg Pro: authenticate both systems, choose the objects to sync (such as Elasticsearch's Data streams and Ingest pipelines), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Elasticsearch side: Index templates, Indices, Documents, Index mappings, plus custom fields where Elasticsearch exposes them. On the Ukg Pro side: Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details), Employment 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 Elasticsearch 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 Elasticsearch, so hierarchy-driven logic and permissions don't drift.
Elasticsearch: REST API (JSON over HTTP). Authentication: API keys or basic authentication; Elastic Cloud also issues service account tokens. 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.
Elasticsearch: Optimistic concurrency uses _seq_no and _primary_term instead of row locks, which matters when two writers touch the same document. 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 Elasticsearch and Ukg Pro without custom code.
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 520 integrations available for Elasticsearch and Ukg Pro.