Real-time
Two-way sync
Changes in Ceridian Dayforce or Odoo instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
Ceridian Dayforce to Odoo integration — real-time, two-way sync
Keep Ceridian Dayforce and Odoo 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 Ceridian Dayforce and Odoo
Sync the workers, org structure, and cost centers that Odoo and Ceridian Dayforce share in real time, so the people Ceridian Dayforce manages stay current in the system that runs finance and operations.
Ceridian Dayforce 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 CRM Leads (crm.lead), Purchase Orders (purchase.order), Inventory Transfers (stock.picking), Employees (hr.employee) in Odoo with Time Away From Work & Balances, Employee (HR / Person Details), Employment Status, Work Assignments in Ceridian Dayforce 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.
Common use cases
- 01 Push e-commerce orders into Odoo as sales orders and sync fulfillment status back.
- 02 Mirror invoices and journal entries into a warehouse for consolidated financial reporting across entities.
- 03 Replicate Compensation Summary and pay data into a warehouse for headcount, labor-cost, and compensation reporting without manual BI exports.
- 04 Sync time data by posting raw clock entries from a third-party scheduling tool into Dayforce, or pulling Employee Punches and Schedules into a workforce-analytics database.
Common sync patterns
Where Ceridian Dayforce is the worker system of record: one employee master
When a worker is hired, moved, or offboarded in Ceridian Dayforce, the matching employee record in Odoo is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
New hires ready to transact in Odoo
A new person set up in Ceridian Dayforce becomes an employee record in Odoo in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.
One org structure
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 Ceridian Dayforce maintains.
What you can sync between Ceridian Dayforce and Odoo
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.
| Ceridian Dayforce objects | Odoo objects | How this pairing syncs | |
|---|---|---|---|
| Compensation Summary & Pay Adjustments Compensation Summary returns pay rate and frequency for reporting; Employee Pay Adjustments are written as effective-dated records via PATCH to post pay changes back to Dayforce. | Employees (hr.employee) HR records read for directory and provisioning syncs. | Compensation Summary & Pay Adjustments is specific to Ceridian Dayforce and Employees (hr.employee) to Odoo — each maps to any object or custom field on the other side. | |
| Employee Punches & Raw Clock Entries Time-and-attendance punches; raw clock entries are added with POST and punches removed with DELETE, so time data flows both ways between Dayforce and scheduling or workforce tools. | Projects and Tasks (project.project / project.task) Work items synced with external project tools. | Employee Punches & Raw Clock Entries is specific to Ceridian Dayforce and Projects and Tasks (project.project / project.task) to Odoo — each maps to any object or custom field on the other side. | |
| Employee Schedules Shift and schedule assignments; created and updated through POST and PATCH schedule endpoints and paged with pageSize, used to push schedules from a WFM tool or pull them for analytics. | Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. | Employee Schedules is specific to Ceridian Dayforce and Contacts (res.partner) to Odoo — each maps to any object or custom field on the other side. | |
| Org Units, Departments, Jobs & Positions Configuration reference data; POST creates org units and departments and PATCH updates job, position, department, and org-unit data. Used to resolve and validate XRefCodes when mapping employee writes. | Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. | Org Units, Departments, Jobs & Positions is specific to Ceridian Dayforce and Sales Orders (sale.order) to Odoo — each maps to any object or custom field on the other side. | |
| Time Away From Work & Balances Time-off requests and accrual balances read per employee; pulled into scheduling, payroll, or absence-reporting databases and used to reconcile leave against downstream systems. | Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. | Time Away From Work & Balances is specific to Ceridian Dayforce and Invoices (account.move) to Odoo — each maps to any object or custom field on the other side. | |
| Employee (HR / Person Details) Core worker record keyed by XRefCode; GET Employees returns matching XRefCodes, then a per-employee GET fetches full HR details. New hires are added with POST and edits made with PATCH, so it is read and write. | Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. | Employee (HR / Person Details) is specific to Ceridian Dayforce and Products (product.template / product.product) to Odoo — each maps to any object or custom field on the other side. |
How changes propagate between Ceridian Dayforce and Odoo
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.
Ceridian Dayforce Odoo Sub-second propagation
DetectionCeridian Dayforce 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.
Odoo Ceridian Dayforce Sub-second propagation
DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.
DeliveryEach detected change is written to Ceridian Dayforce through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Ceridian Dayforce: Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
- Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Ceridian Dayforce ⇄ Odoo
Connect Ceridian Dayforce and Odoo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Ceridian Dayforce–Odoo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Ceridian Dayforce or Odoo 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 Ceridian Dayforce or Odoo record.
Observability
Monitoring
Track your Ceridian Dayforce ⇄ Odoo sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Ceridian Dayforce and Odoo.
How the Ceridian Dayforce and Odoo connectors work
Ceridian Dayforce
- Integration surface
- REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads
- Authentication
- HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account.
- Change detection
- No CDC stream. Broad change detection uses delta polling on GET Employees with filterUpdatedStartDate/filterUpdatedEndDate and filterUpdatedEntities to pull only records changed in a window. Dayforce also has native Event Notifications (the Notification Publisher) for lifecycle events — hire, rehire, terminate, and workflow validation — delivered by push to a receiver service or by querying unacknowledged notifications; the publisher runs roughly hourly and each notification must be acknowledged.
- Capabilities
- read · write · webhooks
- Rate limits
- Dayforce does not publish numeric rate limits; thresholds vary by tenant and exceeding them returns HTTP 429, so large employee reads are paged (pageSize) and throttled with backoff. Employee list calls return XRefCodes only, so each employee needs a follow-up GET.
Odoo
- Integration surface
- 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
- Change detection
- Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
- Capabilities
- read · write · webhooks
- Rate limits
- Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works
How to connect Ceridian Dayforce to Odoo — 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.
- 01
Connect your apps
Authenticate Ceridian Dayforce and Odoo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Ceridian Dayforce
connected
Odoo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Ceridian Dayforce and Odoo 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.
objects · Ceridian Dayforce ⇄ OdooCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Ceridian Dayforce OdooCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Ceridian Dayforce and Odoo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Ceridian Dayforce and Odoo: authenticate both systems, choose the objects to sync (such as Ceridian Dayforce's Compensation Summary & Pay Adjustments and Employee Punches & Raw Clock Entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Odoo side: CRM Leads (crm.lead), Purchase Orders (purchase.order), Inventory Transfers (stock.picking), Employees (hr.employee), plus custom fields where Odoo exposes them. On the Ceridian Dayforce side: Time Away From Work & Balances, Employee (HR / Person Details), Employment Status, Work Assignments. 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 Ceridian Dayforce and Odoo: Where Ceridian Dayforce is the worker system of record: one employee master; New hires ready to transact in Odoo; One org structure. When a worker is hired, moved, or offboarded in Ceridian Dayforce, the matching employee record in Odoo is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
-
Ceridian Dayforce: REST API (Dayforce RESTful Web Services, v1/v2), JSON payloads. Authentication: HTTP Basic authentication with a dedicated Web Services user plus the client namespace (Company ID), or an OAuth 2.0 access token from the Dayforce identity endpoint (POST dfid.dayforcehcm.com/connect/token, client_id Dayforce.HCMAnywhere.Client). Token-based auth is recommended, and the Web Services role with the Read Data subfeature must be enabled on the account. 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Odoo: The external API exposes the ORM generically: any model (res.partner, sale.order, account.move) is accessed with the same execute_kw call pattern rather than per-object endpoints. Ceridian Dayforce: Native Event Notifications (the Dayforce Notification Publisher) cover employee lifecycle events — Hire, Rehire, Terminate (and their cancels) and Workflow Validation — pushed to a receiver service or pulled via unacknowledged-notification queries; the publisher runs about hourly and notifications must be acknowledged. Stacksync's field mapping accounts for these differences between Ceridian Dayforce and Odoo without custom code.
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 520 integrations available for Ceridian Dayforce and Odoo.
Popular · 6 of 520
-
Ceridian Dayforce ⇄ Epicor ERP -
Ceridian Dayforce ⇄ Extensiv (3PL Central) -
Odoo ⇄ BambooHR -
Odoo ⇄ Success Factors -
Odoo ⇄ Hibob -
Odoo ⇄ D2l Brightspace
No integrations match .
