PeopleSoft to Oracle Fusion HCM: A Migration Playbook

Migrating HR and payroll from PeopleSoft to Oracle Fusion HCM is a well-trodden path — but the data is where projects slip. This playbook walks the stages that actually determine success, from extraction to a reconciled cutover.

1. Scope the modules

Most PeopleSoft → Fusion HCM moves cover Core HR, Absence and Payroll. Decide early what’s in scope, and — critically — how much history (terminated employees, retirees, prior payroll years) you’ll carry versus archive.

2. Extract from PeopleSoft

Automate extraction with a PeopleSoft Application Engine program (extended with PeopleCode) rather than manual pulls: run-control safety checks to prevent parallel runs, dynamic parameters, and Full plus Change (delta) modes using a last-run timestamp. Effective-dated logic keeps current records correct.

3. Map PeopleSoft → Fusion

Build a source-to-target mapping — e.g. EMPLOYEE_ID → PERSON_NUMBER, department codes to Fusion structures — and normalize codes (country, state, business unit) in staging. Map the compliance-critical fields (for Irish payroll, that’s Revenue reporting and PRSI) explicitly.

4. Load via HDL

Transform staged data into HCM Data Loader files — Worker.dat and related objects — and load through Data Exchange. HDL, not FBDI, is the HCM path.

5. Reconcile and cut over

Reconcile record counts and payroll totals source-to-target across iterative cycles, run UAT with the business, and only then cut over — with a parallel pay run to prove payroll before the first live cycle.