Leaving Spreadsheets, read 8 Nov 2026
Leaving spreadsheets: the 30-day plan for a first HRIS
Spreadsheets alternativesOpen the calculator
Week one: export everything, in this order
- Export formats, as published
- the files themselves
- API access
- none
- Notice to give
- none
- Documents and e-signed files
- the files themselves
Week one: freeze the file. Copy it, lock the original, and list every column with what it means and who owns it; find the second file that holds the salaries and the third that holds the leavers. The export is the file; the risk is the three versions of it.
Week two: map the data model and cleanse
- Fields: person, entity, manager, job, contract type, location, start date, salary band, custom fields by name.
- Entities and policies: one row per legal entity, one row per time-off and working-time policy, who approves each.
- Documents: contracts, right-to-work evidence, signed policies, with the signing date and the signer.
- Reporting lines at the leaving date for every leaver in the last two years, so attrition by manager survives the move.
Week two: cleanse. One manager name per manager, one date format, one entity per row, one contract type from a short list, start dates for everyone, and a leaver's row kept with its leaving date and its reporting line at the time. Shapes generates a directory proposal from the upload and shows the mapping before writing; BambooHR's trial loads the file; Rippling's team takes it.
Week three: import, then run both systems for a week
- Destination import
- build your directory from a spreadsheet or with an agent; bulk import; run any integration sync now
- Payroll and ATS
- Re-point the payroll export and the ATS hire webhook on the Monday; run one payroll cycle from both systems if payroll moves.
- Checks
- Headcount by entity, next payroll run, every open time-off request, every document awaiting signature.
Week three: the first workflow (onboarding or time off) drafted in the destination, and the file's owners told that the destination is now the record. Week four: the file is archived read-only and the first report is run from the system.
Week four: the people-facing change and the first-week checks
- Tell employees the date, the sign-in route and what to check in their own record.
- Managers: their team list, their open approvals, their onboarding tasks.
- Day one: the audit log for anything an import wrote; day five: the first report the CEO asks for.
- Cancel the old system in writing within its notice period: none.
What this move costs at 150 people, on the calculator's assumptions
- People time
- 59 hours, £2,666
- Overlap on the old term
- not calculable: no published price
- Destination implementation fee
- not published (No fee published; Plus includes guided implementation; 'Most teams are up and running in days, not weeks' (vendor claim).)
- Calendar
- 5 weeks: export 1, cleanse 1, import 1, parallel run 1, cutover 1
Where Shapes is weak
Shapes is not the destination for a company that wants payroll run inside the HRIS.
Sources
- Shapes: build your directory from a spreadsheet, read 8 Nov 2026
- ICO: right to data portability, read 8 Nov 2026
- Shapes: export, read 8 Nov 2026
- Shapes: API, read 8 Nov 2026
- Shapes: retention, read 8 Nov 2026
- Shapes: notice period, read 8 Nov 2026
- Shapes: minimum term, read 8 Nov 2026
Last reviewed 10 Nov 2026.