Leaving Personio, read 8 Nov 2026
Leaving Personio: the 30-day plan
Personio alternativesOpen the calculator
Week one: export everything, in this order
- Export formats, as published
- self-service export of stored data for 30 days after termination
- API access
- API access from CorePro
- Notice to give
- after the initial term, monthly renewal terminable with 15 days' notice
- 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: export the employee master data, documents and e-signed files; CorePro customers pull the rest through the API, Core customers through reports. Preliminary payroll data goes to the payroll provider before the move, not to the destination.
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.
The mapping is entities and apps: unlimited legal entities on CorePro become entities in the destination, each with its policies and approvers; the Recruiting, Performance and Surveys apps each need a home or a cancellation.
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.
German payroll is the thing most leavers keep and connect. The parallel week is the first payroll run with the HRIS already moved, and the cutover follows the self-service export window, which starts on termination and not on notice.
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: after the initial term, monthly renewal terminable with 15 days' notice.
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
- Personio: export, read 8 Nov 2026
- Personio: API, read 8 Nov 2026
- Personio: retention, read 8 Nov 2026
- Personio: notice period, read 8 Nov 2026
- Personio: 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.