Skip to content
HRIS Alternatives

Leaving Shapes, read 8 Nov 2026

Leaving Shapes: the 30-day plan

Shapes alternativesOpen the calculator

Week 1 exportWeek 2 map and cleanseWeek 3 import and parallelWeek 4 cut over

Week one: export everything, in this order

Export formats, as published
export all employee files at once; export a performance review as a PDF; reports; API
API access
integrations and API access on Core (all plans); webhooks on Plus
Notice to give
non-renewal notice at least 30 days before the renewal term; Shapes gives 60 days' notice before expiry
Documents and e-signed files
export all employee files at once; export a performance review as a PDF; reports; API

The bulk export of all employee files and the per-review PDF export are release-noted features, and the API is on Core, so a developer can pull fields, tables and workflow history without a ticket. Documents signed inside Shapes come out with the employee files.

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.

Map the custom fields and tables first; Shapes holds more of both than most destinations, and a table built from a sentence has no obvious home in a system that holds only fields. Policies per office and the workflow steps that assign them are the second thing to write down, because the destination will need a person to assign what a workflow assigned.

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.

Notice is 30 days before the renewal term, with Shapes giving 60 days' notice before expiry, and the minimum subscription is on request, so check the order form for the end date before diarising the cutover.

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: non-renewal notice at least 30 days before the renewal term; Shapes gives 60 days' notice before expiry.

What this move costs at 150 people, on the calculator's assumptions

People time
55 hours, £2,464
Overlap on the old term
£2,808 (Core at $8, 3 months)
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

  1. Shapes: export, read 8 Nov 2026
  2. Shapes: API, read 8 Nov 2026
  3. Shapes: retention, read 8 Nov 2026
  4. Shapes: notice period, read 8 Nov 2026
  5. Shapes: minimum term, read 8 Nov 2026
  6. Shapes: export, read 8 Nov 2026
  7. Shapes: API, read 8 Nov 2026
  8. Shapes: retention, read 8 Nov 2026
  9. Shapes: notice period, read 8 Nov 2026
  10. Shapes: minimum term, read 8 Nov 2026

Last reviewed 10 Nov 2026.