BambooHR to Rippling: two systems of record, then one.
BambooHR holds the people record and something else runs payroll. Here is what the split costs, what breaks in a DIY move, and the playbook we run instead.
Why teams move
Rarely a problem with BambooHR. Always the seam beside it.
HR and payroll stopped being one thing.
Every hire, leaver and comp change has to land in both systems, and the thing keeping them in step is a person with a checklist.
IT provisioning is still manual.
The HR record knows someone started on Monday. It cannot open their accounts, ship their laptop or close any of it on the way out.
Reporting stopped being trustworthy.
Headcount from one system, cost from another, and a spreadsheet reconciling them before a board meeting. Once two records disagree, neither is authoritative, and diligence finds that fast.
What breaks in a DIY move
Five things, in the order teams discover them.
Custom fields do not map one-to-one
Years of custom fields accumulate quietly, and many encode a process rather than a fact. Moved as-is they recreate the mess in a new system; the work is deciding which are still true before anything migrates.
Every report built on those fields breaks
Reporting is the last thing anyone checks and the first thing leadership notices. If the fields change shape, so does every saved report and dashboard built on them, including the ones that go to the board.
Two systems of record disagree about history
The HR record and the payroll provider each hold a version of the same events, and they diverge on effective dates, comp changes and leavers. One has to win, field by field, and not during cutover week.
Permissions get rebuilt from memory
Nobody documented who could see what, so the new structure is recreated from what people remember. That is how a manager ends up seeing compensation for a team that is not theirs.
Time-off balances are not what they look like
Accrual rules, carryover caps and three years of manual adjustments do not survive a straight export. Balances that move without reconciliation are the first thing employees notice.
Our playbook
Six phases, and the second is the one nobody plans for.
Audit
Both systems, not one: the HR record, the payroll provider, and every custom field, report and integration nobody documented.
Decide
Field by field, which system is authoritative. This is what separates a migration from a copy, and why the two records stop disagreeing afterwards.
Design
Permissions by role, the module map, and provisioning rules so a start date opens accounts and a leave date closes them.
Build
Configuration and integrations, data migrated in reconciled passes, and reports rebuilt against the new fields as they land.
Parallel
One payroll cycle in both places, compared line by line. This is the step that makes go-live boring.
Cutover
The first live payroll on Rippling with hypercare around it, then the operating cadence starts.
Scope sets the weeks. How far the two records have drifted is the deciding factor.
What it costs
A fixed project,from$35k
Under 50 people, sized to your team on a fit call.
- Covers
- Two systems into one
- After go-live
- 30 days of hypercare
- Who owns it
- Your lead, with a named backup
In writing before anything begins. Additional entities, a historical rebuild, or a wider scope decide where it lands from $35k, and none of them move the number after it is signed.
What people ask before committing to a date.
How long does a BambooHR to Rippling migration take?
Scope decides it rather than a standard clock. Because this move usually collapses two systems into one, the deciding factor is how far the HR record and the payroll provider have drifted apart. We tell you which case you are in during the audit week, and put the date in writing before you commit to it.
Do we have to move payroll at the same time?
No, and sometimes you should not. Moving the people record first and payroll at a clean quarter or plan-year boundary is a legitimate sequence. What does not work is leaving both live indefinitely: that is the split you are paying to close.
What happens to our custom fields and reports?
They get triaged, not copied. We work out which fields still describe something true, map those, and rebuild reporting against the new structure as part of the build rather than after it.
Can we keep our BambooHR data?
Yes. Records migrate, and historical detail usually stays accessible in BambooHR for its retention period. We document what lives where, because the question returns at year end or in diligence.
What does it cost?
A fixed project, from $35k, in writing before anything begins. Additional entities, a historical rebuild, or a wider scope decide where it lands from there, and none of them move the number after it is signed. Under 50 people, sized to your team on a fit call.
20 minutes. No deck. No pitch.
You talk. We map what you’re running and where to start. The fixed quote follows the call, in writing.