# The HRIS migration checklist

Guide, 8 Nov 2026, read 8 Nov 2026

**The short answer.** The checklist runs in four weeks: notice and export in week one, mapping and cleansing in week two, import and parallel run in week three, cutover and checks in week four. Every line names an owner and a source. It is the skeleton every 30-day plan on this site is built on, with the incumbent's ledger row filled in.

## Week one: notice and export

- Read the incumbent's ledger row: notice period, minimum term, retention after cancellation, export formats. Diarise the notice date (People lead).
- Send the notice or the non-renewal in writing if the term allows it; ask for the export format and the retention terms in writing where the row says 'not published' (People lead).
- Export people records, jobs, compensation history, time off balances and history, documents, e-signed files, review cycles, and the audit trail or change history (People ops).
- Export the reporting line at the leaving date for every leaver in the last two years (People ops).
- Freeze changes to custom fields and policies in the old system (People lead).

## Week two: map and cleanse

- One row per legal entity with its policies, approvers and payroll provider (People lead).
- Field map: every old field to a new field, a custom field or an archive; the guide on custom fields has the template (People ops).
- Cleanse: one manager spelling, one date format, one contract type list, start dates for everyone (People ops).
- Policies: time off, working time, attendance, per office; who approves each (People lead).
- Workflows: list every automation in the old system with its trigger and its approver; count them (People ops).
- Documents: which are signed, by whom, on what date; which need re-signing in the new system (People ops).

## Week three: import and parallel run

- Import into a sandbox or trial first where the destination offers one (Shapes on Plus, Humaans on Enterprise, BambooHR's trial), then into production (People ops).
- Re-point payroll: the export from the new HRIS to the provider, tested on one cycle (Finance and People ops).
- Re-point the ATS: the hire webhook or sync into the new HRIS (People ops and the recruiter).
- Re-point identity: SSO and the provisioning sync (IT).
- Run both systems for a week: every time-off request, every new starter, every document in both (People ops).
- Headcount by entity, open requests, documents awaiting signature: the three reconciliations (People lead).

## Week four: cut over and check

- Tell employees the date, the sign-in route and what to check in their record (People lead).
- Managers: team list, open approvals, onboarding tasks (People lead).
- Day one: the audit log for anything the import wrote (People ops).
- Day five: the first report the CEO asks for, run from the new system (People lead).
- Cancel the old system in writing within its notice period; confirm the retention window in writing (People lead).
- Archive the exports read-only, with the date (People ops).

## Sources

- Shapes: export all employee files: https://shapes.co/releases/export-all-employee-files-at-once (read 8 Nov 2026)
- Shapes: build your directory from a spreadsheet: https://shapes.co/releases/build-your-directory-from-a-spreadsheet (read 8 Nov 2026)
- BambooHR DPA: https://www.bamboohr.com/legal/data-processing-agreement (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://hrisalternatives.com/guides/hris-migration-checklist/
