Migrate from CareerBuilder Applicant Tracking to BambooHR

CareerBuilder Candidates map to BambooHR employee records for hired candidates or candidate records for active applicants. Standard fields (name, email, phone, address, source attribution) migrate 1:1. The CareerBuilder candidate source property (how they entered the system) maps to BambooHR's source field or a custom field depending on the customer's Advantage configuration. We flag records where the resume last-updated timestamp is older than 18 months and hold them in a separate suppression queue for the customer to review before final import.

CareerBuilder Jobs map to BambooHR Job Openings. Job title, description, department, location, and employment type migrate directly. The BambooHR Job Opening must be active in BambooHR before Applications can be linked to it, so we sequence Job creation before Application import. Jobs without an active status in CareerBuilder at migration time are held as draft Job Openings for the customer's admin to activate post-migration.

CareerBuilder Applications (linking a Candidate to a Job with status, submission date, and routing history) map to BambooHR Applications. The Application status migrates as a BambooHR stage value with a custom mapping table because stage names differ between the two systems. Applications in a 'Withdrawn' or 'Rejected' status in CareerBuilder migrate with that status preserved in BambooHR, but BambooHR's default workflow may display only active-stage applications on the hiring board.

CareerBuilder configurable pipeline stages (Applied, Screening, Interview, Offer, etc.) vary by customer configuration and by job. We extract the full pipeline schema on day one of migration, enumerate each stage name and order per pipeline, and map them to BambooHR's hiring stage values or custom stage names if the customer has configured them in BambooHR ATS. Stage ordering is preserved by setting the stage sequence number in BambooHR during import.

CareerBuilder Talent Pools (talent network members held separately from active job applications) map to BambooHR Talent Pools if the customer has BambooHR Advantage with Talent Pools enabled, or to candidate tags if the customer is on the standard ATS tier without dedicated talent pool support. The original CareerBuilder pool name is preserved as the BambooHR talent pool name or as a tag prefix for reconstruction.

Recruiter-assigned numeric ratings and structured scorecards from CareerBuilder migrate as BambooHR custom fields if BambooHR Advantage is configured to store them on candidate records. Scorecard criteria that map to numeric values become custom numeric fields; free-text scorecard comments migrate as long-text custom fields. BambooHR's Custom Field Builder supports short answer, long answer, and list field types, which covers most scorecard structures.

Email threads and recruiter notes attached to candidates migrate as BambooHR employee notes with sender, timestamp, and body text preserved. Attachment filenames are mapped but full attachment files are not transferred unless the customer has document attachment storage configured in BambooHR. Communication thread ordering is preserved by timestamp.

Resume files stored as binary attachments per candidate in CareerBuilder are chunked and mapped to the corresponding candidate record in BambooHR. We chunk large volumes of resume files (500+ per batch) and use BambooHR's file import API to attach each resume to the correct candidate record. The customer must verify that BambooHR's file storage limits under their Advantage package accommodate the total resume volume before migration.

CareerBuilder customers with custom fields on candidate profiles (inherited from Luceo-era configurations or customer-specific setups) migrate to BambooHR custom fields. We extract all custom field definitions (name, type, required/optional, tab placement) and recreate them in BambooHR using the self-service Custom Field Builder where supported. BambooHR does not allow duplicate field names or protected personal information fields (SSN, etc.); any restricted fields are held for manual entry post-migration.

CareerBuilder recruiter and hiring manager user accounts are mapped to BambooHR employee records. Owner assignments on candidates and jobs are translated to BambooHR user assignments based on email matching. Permissions structures are not migrated as CareerBuilder's permission model and BambooHR's HRIS permission model are structurally different; the customer configures BambooHR permissions post-migration.