Two-way sync
Changes in Google Cloud Spanner or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner 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. Google Cloud Spanner is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Time & Attendance (UTA), Employee (Person Details), Employment Details, Job / Position History in Ukg Pro need to exist as queryable Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner 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 Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner with Time & Attendance (UTA), Employee (Person Details), Employment Details, Job / Position History 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 Google Cloud Spanner, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in Google Cloud Spanner 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 Tables, Rows, Interleaved tables, Secondary indexes in Google Cloud Spanner, 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.
| Google Cloud Spanner objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Rows The unit of read and write in each sync cycle, keyed by primary key. | 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. | Rows is specific to Google Cloud Spanner and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Interleaved tables is specific to Google Cloud Spanner and Time & Attendance (UTA) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | 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. | Secondary indexes is specific to Google Cloud Spanner and Employee (Person Details) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Employment Details Employment status, hire and service dates, and company assignment; the record that drives active/terminated state for provisioning downstream. | Change streams is specific to Google Cloud Spanner and Employment Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Views is specific to Google Cloud Spanner and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Databases Top-level containers that scope schema and sync configuration. | 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. | Databases is specific to Google Cloud Spanner and Compensation 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.
DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.
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 Google Cloud Spanner as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Ukg Pro connection.
Changes in Google Cloud Spanner or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner 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 Google Cloud Spanner or Ukg Pro record.
Track your Google Cloud Spanner ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner 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 Google Cloud Spanner 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 Google Cloud Spanner 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 Google Cloud Spanner and Ukg Pro: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Rows and Interleaved tables), 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 Google Cloud Spanner 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 Google Cloud Spanner, so hierarchy-driven logic and permissions don't drift.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). 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.
Google Cloud Spanner: Interleaved tables physically store child rows with their parent rows, which affects how related records are read. 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 Google Cloud Spanner 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 Google Cloud Spanner 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 427 integrations available for Google Cloud Spanner and Ukg Pro.