Migrate from Ashby to BambooHR

Ashby Candidates who have accepted an offer map to BambooHR Employee records with name, email, phone, start date, and compensation pulled from the corresponding Offer. Candidates in earlier pipeline stages (Sourcing through Interview) map to BambooHR Job Application records tied to a BambooHR Job Opening. We separate the migration at offer acceptance status so that the employee record in BambooHR contains the HRIS fields (department, employment status, manager) rather than recruiting fields.

Ashby Application records (candidates linked to specific Jobs and Openings) map to BambooHR Job Application records. The application submission date, current stage, and stage transition history migrate as metadata fields or as notes attached to the BambooHR application. BambooHR's application record does not support the full stage-history timeline that Ashby captures, so we preserve stage history as a note or attachment in the migration.

Ashby Job records (top-level job postings with title, department, team, location, status) map to BambooHR Job Opening records. Job board distribution settings in Ashby are documented for manual reconfiguration in BambooHR because BambooHR manages job distribution through its own integrations. We export the job description, requirements, and hiring team assignments and map them to BambooHR's Job Opening fields.

Ashby Openings (individual headcount slots within a Job) map to the headcount count on a BambooHR Job Opening. Multi-opening positions in Ashby (e.g., 3 backend engineer slots) are represented as a single BambooHR Job Opening with a headcount value of 3. We aggregate opening counts during export and set the corresponding field in BambooHR.

Ashby Offer records carry compensation details (salary, equity, bonus), start date, and e-signature status. These map to BambooHR Employee fields in the jobInformation table (pay rate, pay frequency, hire date). Ashby's default salary offer field maps to BambooHR's payRate. Custom offer fields supported by Ashby's BambooHR integration (jobInformation and employeeStockOptions tables) migrate as Employee custom fields if the customer is on a BambooHR tier that supports custom fields.

Ashby Users (recruiters, hiring managers, admins) with active roles map to BambooHR Employee records. We export role assignments and flag which Ashby users correspond to BambooHR system users versus passive employees. Note that Ashby's elevated seat pricing model (separate from recruiter seats) means the number of active Ashby users may differ from the BambooHR employee count; we scope the user count separately during discovery.

Ashby Interview Plans with stage structures, interviewer assignments, and scorecard templates export as configuration documentation. Automated activity triggers (booking links, assessment invitations) tied to stage entry are tier-gated and do not migrate. We deliver a written map of every active interview plan with its stage sequence, scorecard fields, and automation triggers for the customer's admin to rebuild in BambooHR's Job Opening configuration.

Ashby Activity records (calls, emails, internal notes, scorecards) attached to Candidates and Applications migrate as BambooHR Employee Notes or Job Application Notes. We export activity type, timestamp, author, and content. Note that BambooHR's note model is simpler than Ashby's engagement timeline—ordering and attribution are preserved but the rich activity stream visualization is not. We discuss with the customer whether to migrate full history or a summary.

Ashby custom fields on Candidates, Applications, and Jobs enumerate via customField.list. We export all custom field definitions and values, then map them to corresponding BambooHR custom fields. Critical constraint: BambooHR custom fields are not available on the Foundations plan. If the customer is on a BambooHR tier that restricts custom fields, we flag which Ashby custom fields need to be dropped or consolidated into standard fields.

Ashby Departments and Teams map to BambooHR Department records. Department hierarchy migrates as a nested structure. Team assignments on Jobs and Users map as department associations in BambooHR. We resolve the hierarchy during export and create the matching department tree in BambooHR before migrating any records that reference it.

Ashby Candidate Sources and Tags (recruiting channels, skill tags, boolean tags) migrate as text metadata on the corresponding BambooHR Job Application record. BambooHR does not have a native tagging model equivalent to Ashby's sourcing CRM, so we append tag values as comma-separated text fields or as application notes for the customer's review.