Migrate from LiveHire to BambooHR

Active candidates currently in a LiveHire hiring process map to BambooHR Applicant records. Candidates who have progressed past offer acceptance and into onboarding map to BambooHR Employee records via the Add Employee form. Historical candidates no longer in active processes may be imported as Applicant records or archived as an Employee export depending on the customer's reporting needs. We resolve the split using LiveHire's candidate status and most recent application stage at migration time.

Talent Community members are passive candidates who expressed interest but have no active application. LiveHire stores these separately from Applicants. BambooHR has no native Talent Community equivalent. We migrate Talent Community members as Applicant records with a talent_pool tag that reconstructs the audience segment. The customer's admin recreates Talent Pool names as BambooHR tags or custom fields during configuration. Automated re-pooling rules from LiveHire do not migrate and must be rebuilt as manual tagging workflows in BambooHR.

Active LiveHire job requisitions map to BambooHR Job records. Job title, description, location, employment type, and department migrate directly. Job status (open, paused, closed) maps to BambooHR's Job Status values. Job approval workflows attached to job postings do not migrate; we document the approval chain as a written handoff for the customer's admin to configure in BambooHR's workflow settings.

The application record linking Candidate to Job migrates to BambooHR's Application object. Application date, source channel, and current pipeline stage transfer directly. Stage transition timestamps migrate as custom fields on the Application record. Custom application form fields require explicit field mapping because LiveHire's application schema varies by organization.

LiveHire Talent Pools are many-to-many candidate collections with automated re-pooling rules. BambooHR has no native Talent Pool object. We export current pool membership as a candidate-to-pool lookup table and recreate pool names as Tags in BambooHR. Each migrated candidate receives tags matching their LiveHire Talent Pool memberships. Automated re-pooling rules and pool segmentation criteria do not migrate; the customer documents these for manual recreation as BambooHR tag-based audience filters.

LiveHire configurable stage sequences defining hiring processes for different job types do not migrate as executable code. We deliver a written inventory of every LiveHire workflow including stage names, required approvals, automation triggers, and conditional branching logic. BambooHR uses checklist-based approval workflows rather than stage-sequenced pipelines. The customer's admin rebuilds workflow logic using BambooHR's workflow builder post-migration.

Recruiter and hiring manager notes attached to candidates and applications migrate to BambooHR Note records. Interview scores, ratings, and internal commentary transfer as note body text with formatting preserved where possible. Notes are linked to the corresponding Applicant or Employee record in BambooHR.

LiveHire communication threads (including 2-way SMS which is a distinctive LiveHire feature) migrate as Note records attached to the candidate timeline. We preserve message content, sender, recipient, and timestamp. BambooHR does not support native SMS within the ATS; the customer should note this gap if SMS communication history is a compliance or audit requirement.

LiveHire offer records including proposed compensation, start date, and acceptance status migrate to BambooHR. BambooHR Onboarding includes e-signature capability for offer letters and new hire documents. Offer history attached to applications transfers to preserve compensation negotiation records for compliance and audit purposes.

Resumes, cover letters, portfolio files, and signed agreements attached to candidate profiles are binary file transfers handled separately from structured records. We map file associations to candidate records in BambooHR's document storage. The customer should verify that BambooHR's file storage limits on their tier accommodate the attachment volume.

Organization-specific data fields on Candidates, Jobs, and Applications require explicit field mapping. LiveHire's custom field schema varies significantly between tenants. We document every custom field with its data type, validation rules, and picklist values, then map each to an equivalent BambooHR custom field or standard field during migration.

Audit trails, approval signatures, background check results, and right-to-work documentation require careful handling during migration. We flag compliance records for explicit customer authorization before transfer. BambooHR's Compliance Intelligence (Elite tier) or built-in compliance features may serve as the destination for regulatory documentation. Compliance workflows do not migrate; the customer documents their compliance process for rebuild in BambooHR's compliance module.