Migrate from Alpha Hire to BambooHR

Alpha Hire Candidate profiles, including screening data, vetting records, application history, and any AI-generated match scores, map to BambooHR Employee records created in Applicant status. We preserve the candidate's full name, email, phone, source attribution, and screening notes in the Employee record. Status in BambooHR's applicant pipeline (Applied, Phone Screen, Interview, Offer, Hired, Rejected) maps from Alpha Hire's pipeline stage values. If the candidate was hired, we set the BambooHR hire date and transition the record from Applicant to Active Employee.

Alpha Hire Job Orders (sourced from VMS feeds, manual entry, and other recruiting channels) map to BambooHR Job Opening records. We preserve the job title, department, location, employment type (full-time, part-time, contract), and job description. VMS-sourced job orders may arrive with incomplete metadata; we validate every record against BambooHR's required fields during migration and flag records with missing required values for customer review before final load. The source attribution field (VMS feed name or manual) migrates to a custom text field on the Job Opening.

Alpha Hire Talent Partner records have no native BambooHR equivalent. During scoping, the customer chooses one of two approaches: (1) create Talent Partners as Company records with a talent-partner designation checkbox and contact records attached, or (2) create a custom Employee record type called Talent Partner with the appropriate fields. We implement whichever approach the customer selects, preserving partner name, contact information, associated clients, and assignment history. The choice affects reporting and filter views in BambooHR's ATS pipeline.

Alpha Hire's refined 3-step hiring process templates map to BambooHR's Job Opening pipeline stages. We create a BambooHR pipeline template matching the customer's active Alpha Hire process definition, including stage names, stage order, and stage requirements. If the customer uses custom stage names per client, we create separate pipeline templates and associate them with the corresponding Job Openings.

Alpha Hire screening records (AI-generated scores, vetting notes, qualification ratings) map to custom fields on the corresponding BambooHR Employee record if the fields are structured (numeric score, yes/no flags). Free-text screening notes map to an Employee Note attached to the record. We ask the customer during scoping to identify which screening fields are actionable versus archival so we allocate them appropriately.

Alpha Hire's auto-assignment rule engine handles job order routing based on custom logic. Custom rules are configuration-heavy and do not export from Alpha Hire. During scoping, we ask the customer to document their active rule configurations. We deliver a written inventory of every rule with its trigger, conditions, and routing logic, along with a recommended BambooHR Automation equivalent. BambooHR's Automation builder supports task assignment triggers and approval chains but not the full conditional routing that Alpha Hire's engine provides; rules that cannot be replicated are flagged for manual rebuild post-migration.

Candidate attachments, offer letters, and onboarding documents stored within Alpha Hire migrate as files attached to the corresponding BambooHR Employee record. Export availability depends on the customer's data export capability from Alpha Hire. We attempt to include all accessible attachments in the migration package and map them to the correct Employee record by candidate email as the dedupe key.

Alpha Hire subscription metadata (plan tier, billing model, start date) does not map to BambooHR. We extract this information during scoping for reference but do not replicate billing relationships in the destination system. The customer re-establishes their BambooHR subscription directly through BambooHR's sales team.

Alpha Hire integrates with Microsoft Outlook, ADP, and QuickBooks. We document active integrations during scoping, identify equivalents in BambooHR (Outlook via BambooHR email sync, ADP via native integration, QuickBooks via third-party connector), and flag any integrations that require reconfiguration post-migration. The BambooHR setup wizard handles reconnection; we provide the configuration parameters from the scoped inventory.

Alpha Hire user accounts and owner assignments on Candidates and Job Orders map to BambooHR Employee records with active user access. We resolve by email match during migration. Any Alpha Hire owner without a matching BambooHR user account goes to a reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on Job Opening assignments.