HRIS migration
HRIS migration, as part of your project team.
A migration is not just cleaning data and loading it. I work as part of the project team: understanding the system you are moving from and the one you are moving to, what legacy data there is and where it lives, whether it is consistent, how it has to change to fit the new system, and proving through testing that it has.
I manage the extraction, cleansing, and mapping of complex workforce data from legacy systems and EUCs into Workday, Oracle, PeopleXD, ResourceLink and other platforms. Beyond the cutover, I rebuild your reporting natively in the new HRIS, establish zero-disruption reporting routines, and deploy Manager Self-Service (MSS) so leaders aren't bottlenecked by HR.
The migration, end to end
Nine stages, and what I do in each.
The failure points of a migration are almost always the data, not the system.
-
Scope the move
The system you are moving from and the one you are moving to, the modules in scope, every source of legacy data including the EUCs and spreadsheets kept beside the HRIS, who owns each, and what must move, what is archived and what is retired.
-
Audit the legacy data
Every source profiled: what is complete, consistent and current, and what is duplicated or contradictory, ranked by what it would break, with a correction list your admin teams fix at source before anything moves.
-
Know the target
Before transforming anything, know what you are transforming it into: the new system’s data model and load rules, its mandatory fields, accepted formats and code lists, how it handles effective dates, and how it builds the hierarchies of organisations, positions, cost centres and managers.
-
Map the fields and the values
Not only which column goes where, but what every value becomes. Do your absence reasons map to the absence reasons in the new system? Your leaver reasons, grades, job codes and contract types? One versioned mapping document, signed off by the people who own the data.
-
Transform the shape of the data
Legacy data rarely arrives in the shape the new system needs. Absence kept day by day, row by row, on a spreadsheet has to become one record per absence, and a date range with fifty days on one line may need splitting the other way. History, effective dates and every transformation rule are written down.
-
Build the loads and run mock conversions
Load files built to the new system’s specification and run as several mock conversions. Each one is reconciled, its defects are logged and fixed at source or in the rules, and it is run again until the data is ready.
-
Test and reconcile
Record counts and values reconciled from source to target after every load; data validated before functional testing begins; support for end-to-end and user acceptance testing, and for reconciling payroll parallel runs.
-
Cut over
A cutover plan with the data freeze, the order of the loads, the final reconciliation, the sign-offs and the point at which you would roll back, so go-live is a checklist rather than a leap.
-
Go live and keep going
Native reporting suites and reports rebuilt in the new HRIS, Manager Self-Service in place, data issues fixed through the settling-in period, and the legacy data archived or retired as agreed.
The engine as my assistant
The HR Intelligence engine cleans the data to a high standard first.
It reads raw HR exports from any HRIS or EUC, maps the columns to over 150 canonical fields and builds a clean, historical model, all in the browser, without sending the data anywhere. That makes it a tool for a migration as well as for MI.
-
Migration Assistant
Fifteen steps from set-up to outputs: project, modules, detail, inputs, inventory, mapping, values, quality, cleansing, cycles, defects, reconciliation, workshops, plan and outputs.
-
Migration Readiness
File by file: ready to move, or what has to be corrected first.
-
Audit before you load
A ranked list of what is wrong in the data, each with a count and what it affects.
-
Value mapping
Unknown columns and wordings decided once, one click each, and remembered: the place where absence reasons and leaver reasons are mapped.
-
Reconciliation
Every file joined to the staff list by employee ID: uploaded, mapped, unmapped or excluded, file by file.
-
Old and new compared
Two extracts compared person by person: who is new, who has gone, what changed, with a bridge that always adds up.
Where I have done this
HRIS migrations in regulated financial services.
Managing data extraction, mapping, and cutover checks for migrations averaging over 3,000 people each, across Workday, Oracle, PeopleXD, ResourceLink and RMS, then engineering the native reporting so nothing is lost at go-live. On one Workday migration that included a job code remap and a band migration.
Every picture is the running product on Meridian Bank 2, a synthetic organisation. No real person, client or organisation appears in it. See the full journey, screen by screen, or watch the five-minute demo.
Talk it through
Start with the question your board keeps asking, or the data problem behind it.