Skip to content
HRIS Alternatives

Leaving Sage HR, read 8 Nov 2026

Leaving Sage HR: the 30-day plan

Sage HR 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
reports (Leave Management report)
API access
Sage HR API
Notice to give
monthly modular plans (pricing page)
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 the employee database and org chart, the leave management report, performance history, timesheets and expenses, each from its module; ask the trust page's contact in writing what happens to the record after cancellation.

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 small-business simple: leave policies, a few custom fields and the org chart. Sage Payroll, a separate product, stays and connects; Sage People customers are on a different product and a different plan.

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 leave request approved in the destination while Sage HR still shows the balance; the cutover is the end of the month, module by module.

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: monthly modular plans (pricing page).

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

People time
59 hours, £2,666
Overlap on the old term
£2,282 (Core HR and Leave Management at $6.5, 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. Sage HR: export, read 8 Nov 2026
  2. Sage HR: API, read 8 Nov 2026
  3. Sage HR: retention, read 8 Nov 2026
  4. Sage HR: notice period, read 8 Nov 2026
  5. Sage HR: 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.