Two-way sync
Changes in Odoo or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Keep Odoo 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 people: who was hired, which department and location they sit in, who they report to, and how they are paid. Odoo runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order), Invoices (account.move) in Odoo with Employment Details, Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings) in Ukg Pro field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Odoo keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Odoo roll up to the same structure Ukg Pro maintains.
Manager and reporting-hierarchy changes in Ukg Pro keep expense and purchase approval chains in Odoo pointed at the right people.
Pay and compensation data from Ukg Pro posts into Odoo as labor cost, so finance sees workforce spend without re-entering it by hand.
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.
| Odoo objects | Ukg Pro objects | How this pairing syncs | |
|---|---|---|---|
| Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Job / Position History Effective-dated job, position, department, supervisor, location, and cost center; the most-synced record for org charts, provisioning, and analytics. | Contacts (res.partner) is specific to Odoo and Job / Position History to Ukg Pro — each maps to any object or custom field on the other side. | |
| Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | 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. | Sales Orders (sale.order) is specific to Odoo and Compensation Details to Ukg Pro — each maps to any object or custom field on the other side. | |
| Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | 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. | Invoices (account.move) is specific to Odoo and Payroll (Pay Statements, Direct Deposit, Earnings) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. | Terminations Termination transactions posted with a terminationDate and a reason code that must match the tenant's configured reason table; drives account deprovisioning. | Products (product.template / product.product) is specific to Odoo and Terminations to Ukg Pro — each maps to any object or custom field on the other side. | |
| CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | 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. | CRM Leads (crm.lead) is specific to Odoo and Configuration Setup (Code Tables) to Ukg Pro — each maps to any object or custom field on the other side. | |
| Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. | Time & Attendance (UTA) Timekeeping and worked-hours data exposed by the UTA services; synced into scheduling, payroll, or workforce-analytics databases. | Purchase Orders (purchase.order) is specific to Odoo 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.
DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.
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 Odoo through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Odoo–Ukg Pro connection.
Changes in Odoo or Ukg Pro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Odoo 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 Odoo or Ukg Pro record.
Track your Odoo ⇄ Ukg Pro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Odoo 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 Odoo 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 Odoo 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 Odoo and Ukg Pro: authenticate both systems, choose the objects to sync (such as Odoo's Contacts (res.partner) and Sales Orders (sale.order)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. 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 Odoo side: Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order), Invoices (account.move), plus custom fields where Odoo exposes them. On the Ukg Pro side: Employment Details, Job / Position History, Compensation Details, Payroll (Pay Statements, Direct Deposit, Earnings). 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.
Common patterns for Odoo and Ukg Pro: One org structure; Reporting lines drive approvals; Where Ukg Pro runs payroll: labor cost in the books. Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Odoo roll up to the same structure Ukg Pro maintains.
Odoo: XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink). Authentication: Database user credentials or per-user API keys. 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.
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 520 integrations available for Odoo and Ukg Pro.