Leaving Deel, read 8 Nov 2026
Leaving Deel HR: the 30-day plan
Deel alternativesOpen the calculator
Week one: export everything, in this order
- Export formats, as published
- reports (vendor page)
- API access
- Deel API
- Notice to give
- 30 days' written notice for uncured breach; month-to-month HR pricing
- 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 worker profiles, org chart, time off balances, job architecture and the documents from the HR module; the EOR contracts and payroll records stay in Deel because the employment relationship does. The API is the developer's route for anything the reports miss.
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 simple on HR Core and harder on Advanced and Elite, where performance, learning and planning data have to find a module in the destination or be archived as exports.
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.
The parallel week is the first sync from Deel to the new HRIS, which Shapes documents run by run on its Deel integration page; the cutover is the day the new HRIS becomes the record and Deel becomes the employer in the countries where it already was.
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: 30 days' written notice for uncured breach; month-to-month HR pricing.
What this move costs at 150 people, on the calculator's assumptions
- People time
- 55 hours, £2,464
- Overlap on the old term
- not calculable: Deel HR Core: starting 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
- Deel: export, read 8 Nov 2026
- Deel: API, read 8 Nov 2026
- Deel: retention, read 8 Nov 2026
- Deel: notice period, read 8 Nov 2026
- Deel: 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.