Two-way sync
Changes in Close or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Close 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.
Close runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Ukg Pro. Ukg Pro is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Opportunities, Activities, Tasks, Custom Activities in Close with Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person Details) in Ukg Pro field by field, in real time, and in both directions. You decide which system owns which fields, so Ukg Pro stays authoritative on roles and org structure while Close keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
When Ukg Pro marks a worker as departed, the matching user in Close is flagged or deactivated, so former employees do not keep CRM access after their last day.
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
A person recorded in Ukg Pro, such as a candidate or applicant, can create or update the matching contact in Close, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
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.
| Close objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Custom Activities is specific to Close and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | 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. | Custom Fields is specific to Close and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | 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. | Users is specific to Close and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Smart Views is specific to Close and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | 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. | Leads is specific to Close and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Contacts is specific to Close 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.
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
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 Close through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Ukg Pro connection.
Changes in Close or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Close 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 Close or Ukg Pro record.
Track your Close ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Close 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 Close 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 Close 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 Close and Ukg Pro: authenticate both systems, choose the objects to sync (such as Close's Custom Activities and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and Ukg Pro connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Ukg Pro integration in-house.
Yes — Stacksync ships production-grade connectors for both Close and Ukg Pro. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. On Ukg Pro: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Close side: Opportunities, Activities, Tasks, Custom Activities, plus custom fields where Close exposes them. On the Ukg Pro side: Terminations, Configuration Setup (Code Tables), Time & Attendance (UTA), Employee (Person 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.
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 529 integrations available for Close and Ukg Pro.