Migrate from BambooHR to Zoho Recruit

BambooHR Applicant records map to Zoho Recruit Candidate records. The primary fields (first name, last name, email, phone, address, application date) migrate directly. Last Name is a mandatory field in Zoho Recruit; BambooHR applicants without a Last Name value are populated with the applicant's display name or a 'not provided' placeholder to prevent import rejection. Work history, education, skills, and custom application fields migrate as custom Candidate fields pre-created in the Zoho Recruit layout during scoping.

BambooHR Application records represent a Candidate's application to a Job Opening. We extract the job title from BambooHR's application-to-job linkage and map it to a Zoho Recruit Job Opening. Each BambooHR Application that references the same job title becomes a separate Candidate record linked to the same Job Opening, preserving the one-to-many candidate pipeline relationship.

BambooHR stores job title, department, employment type, and location as job information on an Application. These map to Zoho Recruit Job Opening fields: Job Title, Department, Employment Type, and Location. Active and archived BambooHR jobs are mapped to Zoho Recruit Active and Archived Job Opening states respectively.

BambooHR's configurable applicant pipeline stages (Applied, Phone Screen, Interview, Offer, Hired, Rejected) map to Zoho Recruit's Interview stage workflow. We inventory all custom stage names during scoping and create matching Zoho Recruit stage values in the recruitment process configuration before migration. Stage-specific custom fields (e.g., rejection reason) map to Zoho Recruit Interview custom fields.

BambooHR stores interviewer ratings and notes tied to application records. These map to Zoho Recruit's Interview Feedback Form module. We reconstruct the feedback record with interviewer name, feedback date, rating, and comments as structured fields in the Zoho Recruit Interview module.

BambooHR custom application fields (checkbox, dropdown, text, date, numeric) require a Zoho Recruit custom field to be created in the Candidate module layout before import. We inventory all BambooHR custom fields during scoping, map types (bool to checkbox, text to single-line, multi-select to multi-select with semicolon delimiter), and pre-create the destination fields in Zoho Recruit Setup > Customization > Modules.

BambooHR Employee records with a terminated or active status that originated from a BambooHR ATS hire can be linked to the corresponding Zoho Recruit Candidate record via email match. This is a reference linkage, not a structural migration, since Zoho Recruit does not store full HR records. We deliver a CSV mapping of BambooHR Employee IDs to Zoho Recruit Candidate IDs for the customer's admin to reference during onboarding in Zoho People if needed.

BambooHR Onboarding tasks, checklists, and document requests are HRIS-layer constructs with no Zoho Recruit equivalent. We do not migrate onboarding data as records. We deliver a written inventory of BambooHR onboarding task names, assignees, completion statuses, and pending document requests for the customer's admin to rebuild in Zoho Recruit using Tasks, Events, and Document Library modules.

BambooHR Time-Off requests, balances, and policies are HRIS-layer data with no Zoho Recruit equivalent. Zoho Recruit does not manage time-off accruals or leave requests. We do not migrate time-off data; if the customer also deploys Zoho People, we deliver a data mapping guide for manual or separately scoped time-off data transfer.

BambooHR pay rate, pay type, currency, and compensation bands are HRIS data with no Zoho Recruit module. We do not migrate compensation records. If the customer's Zoho deployment includes Zoho People or Zoho Payroll, we deliver a compensation field mapping guide as a separate deliverable for their admin to configure.

BambooHR documents attached to employee records (offer letters, signed forms, contracts) are accessible via the BambooHR API. We extract document binary data and store it in Zoho Recruit's Document Library under the matching Candidate record. Document export requires the BambooHR API and is scoped as a separate add-on task because binary document handling adds significant time and cost to the migration.

BambooHR custom employee fields on the HRIS side (not ATS application fields) have no Zoho Recruit equivalent in the ATS module. We inventory these fields during scoping and deliver a written mapping to Zoho People custom fields if the customer also licenses Zoho People, noting that the HRIS-layer migration is out-of-scope for this ATS migration.