Skip to content
HRIS Alternatives

Leaving Rippling, read 8 Nov 2026

Leaving Rippling: the 30-day plan

Rippling 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 and exports (vendor page)
API access
public API and plug-ins; data cloud
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 contract's notice period, minimum term, retention clause and export format, and export every custom report while waiting. The Data Cloud and the public API reach the records for a developer; the reports reach them for everyone else.

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 the hardest on the card because Rippling keys policies and permissions to any employee attribute across HR, IT and finance. Write every policy down with its attribute and its effect; the destination will hold policies per office or role and the attributes it has.

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 is a parallel month, devices are an IT project and identity is an SSO migration; none of the three belongs in the 30-day plan for the HRIS, and the plan says so. The calculator's grade D export multiplier is why the Rippling example is eight weeks.

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: Platform (products chosen): starting 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

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