Leaving Workday, read 8 Nov 2026
Leaving Workday: the 30-day plan that is a quarter
Workday alternativesOpen the calculator
Week one: export everything, in this order
- Export formats, as published
- standard data export tooling throughout the term
- API access
- Workday APIs and Extend
- Notice to give
- not published (checked 2026-11-08)
- 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: the export tooling the privacy page describes, run by the platform team, into the destination's import format; the Workday APIs for anything the standard exports miss. The agreement's notice clause is the first thing to read, because an enterprise term can end a year away.
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 security groups, business processes and the integrations built in Extend; each business process becomes a workflow in the destination, and the ones that touch finance stay in Workday if finance stays.
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 period is a month at least, with payroll (US, UK, Canada, France) the deciding cycle. The cutover is the day the Agent System of Record stops being the record for HR, which the destination's audit log takes over.
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: not published (checked 2026-11-08).
What this move costs at 150 people, on the calculator's assumptions
- People time
- 64 hours, £2,869
- 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
- Workday: export, read 8 Nov 2026
- Workday: API, read 8 Nov 2026
- Workday: retention, read 8 Nov 2026
- Workday: notice period, read 8 Nov 2026
- Workday: 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.