.png)
Migrate from Criterion HCM to Rippling with structured payroll history transfer, custom field reconstruction, and benefits election migration — preserving HR and payroll continuity through a clean, validated go-live.
thePeopleStack approaches Criterion HCM migrations with a discovery phase that audits the existing configuration — payroll codes, custom fields, PTO policies, approval workflows, and benefits carrier data — before any Rippling build work begins. We build the field mapping from Criterion's data model to Rippling's, validate a test data load, and resolve discrepancies before migrating the full employee population.
For clients migrating mid-year, we conduct a payroll history audit early in the project to confirm YTD figures and tax withholding records are correctly structured for Rippling import — with payroll sign-off before the go-live date to prevent W-2 issues at year-end.
Criterion HCM is deployed by thePeopleStack's Rippling clients primarily as a US HR and payroll platform, with the migration to Rippling structured around US payroll, benefits, and compliance configurations.
Canadian and cross-border operations: For clients with Canadian employees in Criterion HCM, thePeopleStack manages a parallel Canadian migration workstream — ensuring Canadian employment records, provincial tax data, and CRA account configurations migrate correctly into Rippling's Canadian payroll module as part of the same go-live sequence.
A standard Criterion HCM to Rippling migration for a company with 50–300 employees typically takes 8–14 weeks from discovery to go-live, depending on payroll configuration complexity, custom field count, and whether benefits elections are migrating mid-year or at an open enrollment boundary.
Yes. YTD payroll figures, tax withholding records, and prior period earnings histories from Criterion HCM are extracted and structured for Rippling's payroll history import. thePeopleStack validates payroll history data against Criterion's export format before import to ensure field alignment and W-2 accuracy.
Criterion HCM's custom fields are rebuilt natively in Rippling's custom field framework rather than imported directly. thePeopleStack conducts a custom field audit before migration — identifying which fields are actively used, which can be consolidated, and which should be retired — so the Rippling build reflects your current operational needs rather than accumulated legacy configuration.
Active benefit elections, coverage tiers, and dependent data from Criterion HCM are extracted, mapped to Rippling's benefits structure, and validated against carrier records before the cutover date. thePeopleStack coordinates with HR and benefits carriers to verify plan code alignment before import, preventing enrollment discrepancies at go-live.
Criterion HCM's approval workflow configurations — PTO requests, expense approvals, personnel change forms — are documented and rebuilt in Rippling's workflow automation framework. Each workflow is tested against your approval hierarchy in Rippling before go-live to confirm routing and permissions work as expected.
