Skip to content
HRIS Alternatives

Leaving BambooHR, read 8 Nov 2026

Leaving BambooHR: the 30-day plan

BambooHR 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
custom reports with CSV export (product updates); data export provisions in the DPA
API access
public API under developer terms
Notice to give
month-to-month subscriptions end on the last day of the month cancelled; extended terms renew for 12 months
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: build one custom report per table (people, jobs, compensation, time off, training, assets) and export each to CSV; export the documents folder; pull the Audit Trail for the last two years, because the destination will not have the change history. Hiring data from the ATS stays where it is unless the destination has a hiring module.

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 mostly custom fields and access levels; BambooHR holds one company record with locations, so the second entity that caused the move is created fresh in the destination with its own policies. Time-off policies map one to one.

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.

Payroll (US add-on) and benefits need their own cutover if they run on Bamboo; most leavers keep them for a cycle. An extended-term customer should check the order form's auto-renewal before diarising anything.

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: month-to-month subscriptions end on the last day of the month cancelled; extended terms renew for 12 months.

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

People time
55 hours, £2,464
Overlap on the old term
£3,598 (Core at $10.25, 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. BambooHR: export, read 8 Nov 2026
  2. BambooHR: API, read 8 Nov 2026
  3. BambooHR: retention, read 8 Nov 2026
  4. BambooHR: notice period, read 8 Nov 2026
  5. BambooHR: 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.