Two-way sync
Changes in MySQL or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep MySQL 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. MySQL is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details) in Ukg Pro need to exist as queryable JSON Columns, Stored Procedures, Triggers, Databases (Schemas) in MySQL 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 JSON Columns, Stored Procedures, Triggers, Databases (Schemas) in MySQL with Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person 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.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details) replicate into MySQL where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Ukg Pro stay consistent in MySQL, so hierarchy-driven logic and permissions don't drift.
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.
| MySQL objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Columns Field-level mapping targets with engine-typed values. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Columns is specific to MySQL and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | 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. | Primary and Unique Keys is specific to MySQL and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| JSON Columns Validated semi-structured payloads for nested SaaS data. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | JSON Columns is specific to MySQL and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic that can post-process synced rows. | 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. | Stored Procedures is specific to MySQL and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Triggers An alternative change-capture mechanism when binlog access is unavailable. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Triggers is specific to MySQL and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Databases (Schemas) is specific to MySQL and Job / Position History 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 MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
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 MySQL as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Ukg Pro connection.
Changes in MySQL or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MySQL 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 MySQL or Ukg Pro record.
Track your MySQL ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MySQL 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 MySQL 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 MySQL 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 MySQL and Ukg Pro: authenticate both systems, choose the objects to sync (such as MySQL's Columns and Primary and Unique Keys), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 MySQL and Ukg Pro: One directory of record; Reporting and analytics on current data; Org and structure stay aligned. When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). 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.
MySQL: The binary log in ROW format records every row-level change, enabling log-based CDC without adding triggers to user tables. Ukg Pro: Two auth models exist: core HCM REST APIs use HTTP Basic auth with a web service account plus a Customer API Key and User API Key, while the Onboarding and Recruiting APIs require a bearer Authorization Token from the token endpoint. Stacksync's field mapping accounts for these differences between MySQL 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 MySQL and Ukg Pro records are not retained after a sync operation.
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 546 integrations available for MySQL and Ukg Pro.