Migrate from Candidate Management System to BambooHR

Candidate Manager Job records map 1:1 to BambooHR Job requisitions. We preserve the job title, description (as rich text), department, location, and internal job ID as a reference field. Job status (Open, Closed, Draft) maps to BambooHR's status field. If BambooHR's ATS add-on is not active, Jobs may be created as Employee records with a Hire Date in the future rather than as formal Job requisitions—customer confirms their BambooHR tier and ATS module status during scoping. Posting dates and expiration dates transfer as-is.

Each Candidate Manager Application record maps to a BambooHR Applicant record linked to the corresponding Job. We preserve application status (Applied, Under Review, Interview, Offer, Hired, Rejected), submission timestamp, and source attribution. If the candidate was already hired and is now an employee in BambooHR's HR module, the Applicant record is linked to the Employee record. Active applications in pipeline stages that have no BambooHR equivalent are flagged for explicit status mapping during scoping.

Candidate Manager Candidate records map to either BambooHR Applicant (if the candidate is still in the hiring pipeline) or BambooHR Employee (if the candidate was hired and is now an active or terminated employee). We separate active candidates from historical hire records during the transform phase. Name, email, phone, address, work history, education, and skills transfer to the corresponding BambooHR object. Any candidates with duplicate email addresses are flagged for customer review before import.

Tenant-specific custom properties on Candidate Manager Candidate records map to BambooHR custom fields on the Employee object. We enumerate every custom field during discovery, match by name, and resolve type conflicts (e.g., a text field used as a numeric score is mapped to a BambooHR Number field). BambooHR API cannot pass information fields, section headers, or multiple-selection lists; these are flagged as manual-reentry candidates and stored in a written inventory for the customer's admin to handle post-migration. Any custom properties without a clear destination are held in a catch-all text area field for review.

Application-level custom properties from Candidate Manager map to BambooHR Applicant custom fields. These include screening questions, scored criteria, and intake form responses that vary by organization. BambooHR's applicant custom field API supports text, number, date, dropdown, and checkbox types. Fields that do not match these types (e.g., section headers used as visual separators) are excluded from the API pass and documented for manual rebuild in BambooHR's applicant form builder.

Candidate Manager's configurable per-job or global pipeline stage sequences do not have a direct BambooHR equivalent. BambooHR uses a fixed Applicant Status model (Applied, Phone Screen, Interview, Offer, Hired, Rejected) with limited customization. We map each Candidate Manager stage explicitly to the nearest BambooHR status value, flag any stages that cannot map cleanly (e.g., custom stages like Background Check or Skills Assessment), and deliver a written pipeline configuration guide for the customer's admin to implement the closest equivalent in BambooHR's ATS settings.

Numeric ranking scores and pre-profiling ratings on Candidate Manager Application or Candidate records migrate to BambooHR custom number fields on the Applicant object. We preserve the original field name and value range. Textual scoring rubrics or matrix-based assessments that are not reducible to a single numeric value are flagged as candidates for manual re-entry in BambooHR's applicant notes or a separate assessment tool. The customer confirms during scoping whether rubric-based assessments need a dedicated workflow rebuild.

Recruiter notes attached to Candidate Manager Candidates or Applications export as free-text blobs. We preserve note content and authorship (recruiter name and timestamp) and map to BambooHR Employee Notes or Applicant Notes depending on whether the candidate is a current employee or still in the pipeline. Because BambooHR does not support structured note fields, all free-text content migrates into a single Notes text area per record. If notes reference other records (e.g., cross-candidate notes), those references are stored as plain text and flagged for the customer to resolve manually.

Candidate Manager exports resume files, cover letters, and portfolio documents as binary blobs. We extract text content where parsable (PDF text extraction, DOCX body text) and re-upload the original file type to BambooHR's document storage under the corresponding Employee or Applicant record. Large attachments are chunked for upload to stay within BambooHR API size limits. Any attachments that cannot be parsed to text are re-uploaded as-is. If the original file type is not supported by BambooHR's file viewer, the file is attached as a downloadable link.

Candidate Manager's hiring manager self-service portal assignments (which managers can review which candidates, leave scorecards, move pipeline stages) have no direct BambooHR equivalent. We document the existing portal configuration during discovery—including role-based access assignments, manager-to-job mappings, and self-service permission scopes—and deliver a written configuration guide for the customer's admin to implement equivalent permissions in BambooHR's role-based access settings and ATS sharing rules.