Leaving HiBob, read 8 Nov 2026
Leaving HiBob: the 30-day plan
HiBob alternativesOpen the calculator
Week one: export everything, in this order
- Export formats, as published
- a copy of all personal data downloadable via the service within 30 days of termination; reports
- API access
- public API with employee data endpoints and webhooks; fair-use rate limits
- Notice to give
- automatic renewal; HiBob gives written notice of renewal at least 45 days before
- Documents and e-signed files
- not stated in the export formats read on 8 Nov 2026; ask for a bulk document export in writing
Week one pulls the reports that hold what the API does not: comp cycle history, performance cycles, survey results and the documents folder. The 30-day download window after termination is a safety net, not the plan; everything should be out before the last paid day.
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.
Bob's policies by location, department or employee group are the mapping risk: each policy becomes a policy in the destination and each group becomes a filter or a role. The twelve named Bob AI agents leave nothing behind; the automations they ran need a person to list them.
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.
Payroll on Bob (US and UK) moves with the HRIS only if the destination runs it; otherwise the parallel month is a payroll month on Bob with the HRIS already moved, and the cutover is the first payroll run from the new connector.
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: automatic renewal; HiBob gives written notice of renewal at least 45 days before.
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
- HiBob: export, read 8 Nov 2026
- HiBob: API, read 8 Nov 2026
- HiBob: retention, read 8 Nov 2026
- HiBob: notice period, read 8 Nov 2026
- HiBob: minimum term, 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.