Migrate from Happy Hire to BambooHR

Happy Hire Candidate records map to BambooHR Employee records. The conversion includes first name, last name, email, phone, address, resume file URL, source attribution, and current application status. We preserve the original Happy Hire candidate ID and any sourcing channel (referral, job board, direct) as custom fields on the Employee record. Candidates with no active Application become Employee records with a custom hire_source__c field set to the original source value; candidates with an active Application link to the corresponding BambooHR Job Requisition.

Happy Hire Applications carry stage (applied, screening, interview, offer, hired, rejected), timestamps for each stage transition, and reviewer assignments. Since BambooHR does not have a standalone Application object separate from Employee, we embed the application history as a custom text field application_history__c on the Employee record, storing stage name, transition date, and reviewing user in JSON-serialized format. Active applications still in progress at migration time are flagged with a migration_status__c custom field set to pending_hire.

Happy Hire Jobs map to BambooHR Job Requisitions with job title, description, location, department, and employment status. Active and closed jobs migrate with their posting metadata. We check the job count against the destination BambooHR plan tier (5, 25, or 50 openings) and flag any over-limit jobs before migration so the customer can close or archive postings in Happy Hire before cutover. Custom job fields from Happy Hire map to BambooHR custom fields on the Job Requisition object.

Happy Hire User accounts (name, email, role: Admin, Recruiter, Hiring Manager) map to BambooHR Employee records with access levels assigned to match Happy Hire role permissions. We preserve the role assignment in a custom field happyhire_role__c and note the recommended BambooHR access level for each user. Note: BambooHR does not have a separate non-employee user model; contractors or external recruiters who were Happy Hire Users must be created as Employee records or managed through BambooHR's external sharing settings.

Happy Hire post-hire Employee records (start date, department, employment status, title) map to BambooHR Employee records using the same schema as the Candidate conversion. Custom employee properties from Happy Hire map to BambooHR custom fields on Employee, though Information field types and section headers must be noted as API-incompatible and flagged for manual re-entry post-migration.

Happy Hire onboarding workflows with named checklists and task assignments migrate as onboarding templates in BambooHR. We export task names, assignees, and completion statuses. BambooHR's onboarding checklist uses a task-level structure where each item has a name and optional assignee; nested subtasks in Happy Hire may flatten to top-level checklist items. We document the nesting structure in the migration notes for the customer's admin to reassemble in BambooHR's checklist builder.

Happy Hire Interview Scorecard templates and completed evaluations are exported as structured data. Completed scorecard ratings and evaluator notes are stored as a custom text field scorecard_history__c on the associated Employee record, with evaluator name, interview stage, rating values, and free-text comments serialized. The scorecard template structure itself is documented separately as a configuration note for the customer's admin to rebuild in BambooHR's custom form builder or as a PDF attachment to the Employee record.

Happy Hire tracks which external job boards a job was posted to and the posting URL where available. This metadata migrates as a custom text field job_board_postings__c on the BambooHR Job Requisition, storing an array of board name and URL pairs. Board-level analytics (posting performance, applicant volume per board) do not migrate because BambooHR's ATS does not natively track board-level analytics; we document the original board URLs for the customer's reference.

Resume files and attachments stored against Happy Hire Candidate records are exported as files and linked to the corresponding BambooHR Employee record via ContentDocument and ContentDocumentLink. File type, original filename, and upload date are preserved in the ContentVersion metadata. We flag any file attachments that exceed BambooHR's file size limits for manual upload during the post-migration review period.

Happy Hire custom fields across Candidate, Application, Job, and Employee objects are mapped to BambooHR custom fields on the equivalent destination object. BambooHR supports text, number, date, dropdown, checkbox, and URL custom field types. Fields of type Information, Section Header, or Multiple-Select List cannot pass via BambooHR API; these are flagged during the data audit with a field-level impact note, and the customer decides whether to re-enter these values manually post-migration or convert to a supported field type.