Skip to content
Database ⇄ Human resources

Reltio to Ukg Pro integration — real-time, two-way sync

Keep Reltio 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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Reltio and Ukg Pro

Put your workforce data where your apps can reach it: Reltio and Ukg Pro share the same people, positions, and org structure in real time.

Ukg Pro is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Reltio is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Employee (Person Details), Employment Details, Job / Position History, Compensation Details in Ukg Pro need to exist as queryable Data Change Requests (DCR), Reference Data (RDM), Entities, Relations in Reltio 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 Data Change Requests (DCR), Reference Data (RDM), Entities, Relations in Reltio with Employee (Person Details), Employment Details, Job / Position History, Compensation 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.

Common use cases

  • 01 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
  • 02 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 03 Replicate Compensation and pay-statement / earnings history into a warehouse for headcount, labor-cost, and payroll reporting without manual BI exports.
  • 04 Deprovision accounts by subscribing to UKG Pro termination and job-change webhook events to disable IdP and app access as changes become effective.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in Reltio write onto the matching record in Ukg Pro where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Ukg Pro land as queryable Data Change Requests (DCR), Reference Data (RDM), Entities, Relations in Reltio, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Reltio and Ukg Pro

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.

Reltio objects Ukg Pro objects How this pairing syncs
Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. 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. Matches (Potential Matches) is specific to Reltio and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side.
Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. Activity Log is specific to Reltio and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side.
Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. 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. Data Change Requests (DCR) is specific to Reltio and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side.
Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. Reference Data (RDM) is specific to Reltio and Employment Details to Ukg Pro — each maps to any object or custom field on the other side.
Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. Entities is specific to Reltio and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side.
Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. 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. Relations is specific to Reltio and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side.

How changes propagate between Reltio and Ukg Pro

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.

Reltio Ukg Pro Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

DeliveryEach detected change is written to Ukg Pro through its API, with automatic retries and rate-limit backoff.

Ukg Pro Reltio Sub-second propagation

DetectionUkg Pro notifies Stacksync of record changes through webhook events. No CDC stream.

DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
  • Ukg Pro: An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
What ships with Reltio ⇄ Ukg Pro

Connect Reltio and Ukg Pro for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Reltio–Ukg Pro connection.

Real-time

Two-way sync

Changes in Reltio or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Reltio or Ukg Pro data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Reltio or Ukg Pro record.

Observability

Monitoring

Track your Reltio ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Reltio and Ukg Pro.

How the Reltio and Ukg Pro connectors work

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.

Ukg Pro

Integration surface
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.
Change detection
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.
Capabilities
read · write · webhooks
Rate limits
An API gateway throttles calls per client over a rolling window (typically per minute); UKG does not publish exact numeric thresholds. Exceeding the limit returns HTTP 429, and UKG recommends a roughly one-second looping backoff before resuming (a Retry-After header is not yet standard). Reads are offset-paginated.
Ukg Pro setup guide
How it works

How to connect Reltio to Ukg Pro — three steps, no code

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.

  1. 01

    Connect your apps

    Authenticate Reltio 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Reltio connected
    Ukg Pro connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Reltio 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Reltio ⇄ Ukg Pro
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Reltio Ukg Pro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Reltio and Ukg Pro integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 431 integrations available for Reltio and Ukg Pro.

Popular · 8 of 431
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.