Workday and Oracle HCM Cloud both store HR data, but they think about it differently. Workday's worker model is fundamentally flat — one Worker record, with Compensation, Position, and Org Assignment as related entities. Oracle uses a Worker → Assignment → Position → Job hierarchy where each layer is independently effective-dated. Migrating between them is an exercise in expanding flat data into Oracle's deeper structure without losing history.
The 4 mapping rules that matter
- Rule 1: Every Workday Worker becomes one Oracle Worker. Easy.
- Rule 2: Every Workday Job becomes ONE Oracle Position (not Job — Position). Oracle Position is the FTE slot; Job is the abstract role. This trips up half of all migrations.
- Rule 3: Workday's Compensation history collapses into Oracle's Salary effective-dated rows. Date precision matters — load with the original effective dates from Workday.
- Rule 4: Workday's Organisation Assignments map to Oracle's Department + Cost Center + Location, three separate fields. Don't try to cram them all into Department.
Effective dating — the trickiest part
Workday treats most fields as date-effective by default. Oracle treats some as effective-dated, some as point-in-time. The mapping needs to know which is which.
- Salary, Position, Assignment Status, Department, Manager: all effective-dated in Oracle. Migrate full history.
- Person Name, Date of Birth, National Identifier: point-in-time only in Oracle. Migrate the latest value.
- Address: effective-dated in Oracle for primary, but most secondary addresses are point-in-time. Check the type before deciding.
What we always recommend doing first
Run a worker-count reconciliation BEFORE you load anything. Compare:
- Active workers in Workday, by location.
- Active workers in Workday, by department.
- Sum of FTE in Workday, by department.
If those three numbers don't match what Finance has on the books, fix the source data BEFORE migrating. Loading bad data into Oracle and trying to fix it after is 10x more expensive.
Use HDL, not REST
For bulk HCM loads, Oracle HCM Data Loader (HDL) is the only realistic option. REST works for small daily integrations, but for the historical migration you'll be loading hundreds of thousands of rows across Worker, Assignment, Salary, Position, etc. — HDL handles the volume, gives you proper error files, and integrates with Oracle's data integration jobs natively.
The Syntra ETL team has run more than 100 enterprise data migrations to Oracle Fusion Cloud. We share what we learn so your migration is faster, cleaner, and more boring than ours were.