Skip to content
Data warehouse ⇄ Human resources

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

Keep Dremio 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 Dremio and Ukg Pro

Land the people and organization records from Ukg Pro in Dremio as live tables for workforce reporting, without extract jobs, and write computed results back where Ukg Pro can use them.

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 Dremio next to everything else the company measures.

Stacksync syncs Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings), Terminations from Ukg Pro into tables in Dremio continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Dremio, 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.

Common use cases

  • 01 Consolidate data from multiple lake sources through one Dremio semantic layer into a single warehouse target.
  • 02 Sync curated Dremio views into an operational Postgres so applications get low-latency access to lakehouse data.
  • 03 Push new hires (Employee, Employment, Job) into an ERP, IdP, or app database when onboarding completes so account, cost-center, and payroll setup fire on hire instead of manual report exports.
  • 04 Replicate Compensation and pay-statement / earnings history into a warehouse for headcount, labor-cost, and payroll reporting without manual BI exports.

Common sync patterns

HR data in the warehouse, minus the pipeline

People and organization records from Ukg Pro arrive in Dremio as queryable tables, current within seconds instead of a day behind, replacing hand-built extract jobs.

Headcount and cost joined with everything else

Analysts combine Ukg Pro's workforce records with finance, product, or operational data already in Dremio for reporting the HR system cannot produce on its own.

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

What you can sync between Dremio 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.

Dremio objects Ukg Pro objects How this pairing syncs
Jobs Query execution records useful for monitoring sync workloads. Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. Jobs is specific to Dremio and Employment Details to Ukg Pro — each maps to any object or custom field on the other side.
Sources Connected storage and database systems (S3, ADLS, relational databases) Dremio queries in place. Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. Sources is specific to Dremio and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side.
Physical datasets Tables and files promoted from sources; the raw data a sync ultimately reads. 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. Physical datasets is specific to Dremio and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side.
Virtual datasets (views) SQL views layering semantics over physical data; the preferred sync target for curated extracts. 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 datasets (views) is specific to Dremio and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side.
Apache Iceberg tables Lakehouse tables supporting DML and snapshot metadata usable for incremental reads. Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. Apache Iceberg tables is specific to Dremio and Terminations to Ukg Pro — each maps to any object or custom field on the other side.
Spaces and folders Namespaces that organize virtual datasets and govern access. 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. Spaces and folders is specific to Dremio and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side.

How changes propagate between Dremio 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.

Dremio Ukg Pro Interval-based propagation

DetectionStacksync polls Dremio for changes on an incremental schedule, reading only records changed since the previous pass. Polling via SQL.

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

Ukg Pro Dremio Sub-second propagation

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

DeliveryEach detected change is applied to Dremio as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Dremio: Bounded by engine capacity and workload management rather than API rate limits.
  • 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 Dremio ⇄ Ukg Pro

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dremio 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 Dremio or Ukg Pro record.

Observability

Monitoring

Track your Dremio ⇄ 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 Dremio and Ukg Pro.

How the Dremio and Ukg Pro connectors work

Dremio

Integration surface
Arrow Flight SQL, JDBC/ODBC, and a REST API
Authentication
Personal access tokens or username/password; OAuth-based SSO on Dremio Cloud
Change detection
Polling via SQL; Iceberg table snapshots can anchor incremental reads; no consumer-facing change feed
Capabilities
read · write
Rate limits
Bounded by engine capacity and workload management rather than API rate limits

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 Dremio 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 Dremio 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
    Dremio connected
    Ukg Pro connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dremio 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 · Dremio ⇄ 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
    Dremio Ukg Pro
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dremio 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 434 integrations available for Dremio and Ukg Pro.

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

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