Migrate from Rival Recruit to BambooHR

Rival Recruit Employee records map directly to BambooHR Employee. We preserve hireDate, jobTitle, department, division, location, supervisor (manager), and employmentStatus. Rival Recruit's effective-dated employment change history migrates as rows in BambooHR's employmentStatus custom table, inserted in chronological order. Any Rival Workflow step assignees that reference an employee record are preserved as Supervisor lookups in BambooHR. The BambooHR /employees/changed endpoint supports incremental sync after initial load for any delta records during the migration window.

Rival Recruit Candidate records map to BambooHR Applicant. The BambooHR ATS module stores Applicants as a distinct object with name, email, phone, social media URLs, and application status. We map candidate source attribution from Rival Recruit to the Applicant's sourcedFrom field, and stage history from Rival's pipeline to BambooHR's hiringWorkflowStageName. Active offers with pending start dates are flagged for priority sequencing at cutover.

Rival Recruit Position records map to BambooHR Job postings. The position title, department, location, and hiring manager migrate. Rival's open/closed status maps to BambooHR's jobActive field. The BambooHR ATS add-on is required for active job posting management; the migration is functional without it but job board distribution features require the ATS tier to be active on the BambooHR account.

Rival Recruit stores resumes, cover letters, offer letters, and compliance documents as binary attachments against Candidate and Employee records. We extract the file content and binary metadata separately from the record metadata, then remap to BambooHR's Employee Files or Applicant Files attachments using the appropriate employee or applicant ID. We flag any files stored outside the Rival document store (e.g., in an external S3 bucket referenced by URL) for manual re-upload during cutover.

Rival Recruit Tags applied to Candidates for segmentation and sourcing campaigns are extracted as a flat lookup table mapping tag names to candidate IDs. In BambooHR, we create a multi-select custom field on the Applicant object (field ID discovered via /meta/fields) and populate it with the extracted tag names per applicant. If BambooHR's ATS tier is not active, tags are delivered as a standalone CSV lookup for the customer's admin to reapply manually.

Rival Workflow onboarding journeys with their step sequences, assignees, and conditional logic map to BambooHR's new hire packet and onboarding checklist template. BambooHR does not replicate the conditional branching model of Rival Workflow; steps are linear checklist items. We deliver the Rival onboarding journey as a written configuration guide (step sequence, assignee mapping, I-9 and tax form references) for the customer's BambooHR admin to rebuild as an onboarding checklist template. Active journeys in progress at cutover are flagged and handed over with a status note to prevent new hire onboarding from going dark.

Rival Recruit custom fields on Candidate records are discovered via API schema enumeration before any mapping begins. We fetch the full active custom field list, map each to a corresponding custom field on BambooHR Applicant (created during the pre-migration schema phase), and resolve BambooHR field IDs via GET /v1/meta/fields for the specific account. BambooHR custom field IDs are assigned dynamically per account and cannot be hardcoded; this discovery step is mandatory for every migration and is never skipped.

Rival Recruit custom fields on Position records follow the same discovery-and-mapping pattern as candidate custom fields. We enumerate all active Position custom fields in Rival Recruit, create matching custom fields in BambooHR on the Job object, and map values during import. If a custom field in Rival has a type that BambooHR does not support (e.g., a multi-value array), we flag it for manual review and store the raw JSON value in a text field.

Rival Recruit platform users (recruiters, hiring managers, admins) map to BambooHR account users by email address. We resolve Rival owner references on Candidate and Position records to the corresponding BambooHR user accounts. Any Rival User without a matching BambooHR account enters a reconciliation queue; the customer provisions the account before record import resumes. Inactive Rival users are mapped to inactive BambooHR users to preserve historical assignment records.

Rival Recruit Interview events with date, time, interviewer, candidate, and position are extracted as structured records. BambooHR does not have a native interview scheduling object; interview records migrate as Notes on the corresponding Applicant record with the scheduling metadata preserved in the note body. We recommend that customers use BambooHR's calendar integration (Settings > Integrations > Calendar) post-migration to re-establish scheduling continuity.