Skip to content
HRIS Alternatives

Leaving Humaans, read 8 Nov 2026

Leaving Humaans: the 30-day plan that starts 90 days early

Humaans 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
filter and export data; security audit logs and export on Enterprise
API access
API on Growth; webhooks on Enterprise; MCP for all
Notice to give
90 days' prior written notice to discontinue at the end of the subscription period
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, three months before the end: send the notice. Then export the people data by filter, the documents, the Tables built by asking Humaans AI (as CSV, because the destination will not rebuild them), and the audit logs on Enterprise.

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 custom fields and roles (unlimited on Enterprise, two custom roles on Growth) into the destination's permission model, and Athena's agent-run processes into the destination's workflows, each written down with its trigger and its approver.

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.

There is no payroll to move; preliminary payroll data goes to the provider. The parallel week is the first onboarding run in the destination while Athena runs its last; the cutover is the subscription end.

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: 90 days' prior written notice to discontinue at the end of the subscription period.

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

  1. Humaans: export, read 8 Nov 2026
  2. Humaans: API, read 8 Nov 2026
  3. Humaans: retention, read 8 Nov 2026
  4. Humaans: notice period, read 8 Nov 2026
  5. Humaans: 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.