I'm currently evaluating a switch from SuccessFactors to Rippling for our mid-sized team. The main draw for us is the promise of having HRIS, IT, and payroll in one system.
For those who have made this move, how smooth was the data migration and integration? I'm particularly curious about payroll setup and whether any historical data from SuccessFactors caused issues. Also, how does Rippling's support handle the transition compared to SAP's?
Any insight from your experience would be really helpful! ?^?
Still learning.
We made this transition last year for a team of about 350. The integration is the main selling point, but you should plan for it to be a sequential rollout, not a big bang.
> how smooth was the data migration and integration?
The actual data extraction from SuccessFactors via SFTP was straightforward. The complexity was in the mapping and transformation. Rippling's implementation team provided templates, but you'll need significant internal bandwidth to clean and validate the data, especially custom fields and historical employment records. The payroll setup cannot begin until the core employee data is live in Rippling, so there's a necessary gap. We ran a parallel payroll for two cycles as a safety net, which I would strongly recommend.
> how does Rippling's support handle the transition compared to SAP's?
It's a different model. SAP support is famously byzantine. Rippling's is more responsive and hands-on during implementation, but they operate on a "ticket" basis. You'll have a dedicated implementation manager, but post-go-live, you're back to their general support channels. The quality is good, but the scope is narrower - they support their platform but won't advise on your specific payroll regulations. You'll need a knowledgeable internal payroll person to own that side.
The IT and device management modules are genuinely integrated well, but treat them as phase two. Getting the HRIS and payroll stable is a full-time project for several months.
infra nerd, cost hawk
Parallel payroll cycles are a wise move, but they come with a hidden cost many overlook: you're effectively paying two vendors for the same service during that period, and that overlap can blow a hole in your transition budget. Rippling's pricing model isn't kind to these interim states.
Their support being "more responsive" is a double-edged sword. It's faster because the platform's scope is narrower. They'll help you click through their own UI, but if you have a complex, legacy data scenario that doesn't fit their template, you'll hit a wall. SAP's support is a maze, but sometimes you need that depth for a messy, one-off problem. Rippling's approach is to standardize you out of it.
-- cost first