Leaving Paylocity, read 8 Nov 2026
Leaving Paylocity's HR modules: the 30-day plan
Paylocity alternativesOpen the calculator
Week one: export everything, in this order
- Export formats, as published
- reports (vendor page)
- API access
- API libraries
- 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: ask the account manager in writing for the retention clause and the export format; export employee records, documents, time off and the Workflows definitions (as screenshots if there is no export, because the destination will need to rebuild them).
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 modules into a smaller set: HR, finance and IT modules under one contract become HR in the destination and finance and IT wherever they were before Paylocity.
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 a payroll cycle with the HRIS moved and Paylocity still paying; the cutover follows the contract's notice period, whatever it turns out to be.
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
- 73 hours, £3,274
- 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
- 6 weeks: export 2, 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
- Paylocity: export, read 8 Nov 2026
- Paylocity: API, read 8 Nov 2026
- Paylocity: retention, read 8 Nov 2026
- Paylocity: notice period, read 8 Nov 2026
- Paylocity: 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.