Migrate from CareerBuilder Applicant Tracking to Recruit CRM & ATS

CareerBuilder Jobs (Positions) map 1:1 to Recruit CRM Jobs. We extract the full job schema including title, description, department, location, employment type, and the associated pipeline stage assignments. Each CareerBuilder pipeline attached to a job maps to a Recruit CRM pipeline with the same stage order. Job status (Open, Paused, Closed) migrates directly. We flag any job with an applicant count near the 10-13 cap for admin review before migration.

CareerBuilder Candidates map to Recruit CRM Candidates as the central recruiting object. Standard fields (name, email, phone, location, source attribution) migrate directly. We flag Candidates whose last resume update timestamp predates 18 months before migration so the admin can suppress or include them selectively. Source attribution (how the candidate entered the system) maps to Recruit CRM's source field.

Each CareerBuilder Application links a Candidate to a Job with a status, submission date, and pipeline stage progression history. We migrate full application history including submission timestamp, current stage, and all historical stage transitions with dates. Application status maps to the equivalent Recruit CRM status: Applied, Screening, Interview, Offer, Hired, or Rejected.

CareerBuilder Talent Pools (talent network members maintained separately from active job applications) map to Recruit CRM Talent Pools or Categories. We preserve the original pool name as a tag on the candidate record and create the corresponding pool in Recruit CRM before candidate migration. Candidates are linked to pools by candidate ID resolution during import.

CareerBuilder configurable stages (Applied, Screening, Interview, Offer, etc.) vary by customer configuration and by job or department. We extract the full pipeline schema on day one, document each stage name and position, and map them to identically named Recruit CRM pipeline stages. Stages that have no exact match in Recruit CRM are flagged for the admin to confirm the closest equivalent.

Numeric ratings and structured scorecards assigned by recruiters in CareerBuilder migrate as custom numeric fields on the Candidate record in Recruit CRM. The rating value, the evaluator name, and the evaluation date are preserved. Scorecard criteria migrate as individual numeric fields named to match the CareerBuilder criterion label.

Email threads and recruiter notes attached to candidates in CareerBuilder migrate as chronological Activity records in Recruit CRM. We preserve sender, timestamp, subject, and body text. Attachment filenames are mapped to note entries referencing the original filename; full binary attachments are transferred separately and linked by filename reference.

Resume files stored as binary attachments per candidate are chunked by volume (batches of 500) and uploaded to the corresponding Candidate record in Recruit CRM. Each file is linked to the candidate by email or candidate ID lookup. Customers should confirm the Recruit CRM plan supports the expected resume storage volume before migration.

CareerBuilder customers with custom fields on candidate profiles (inherited from Luceo-era configurations or added later) are extracted with their field types and values. We map each custom field to a Recruit CRM custom field of the equivalent type: text to text, numeric to number, dropdown to picklist. Luceo-era field names are preserved in the field label for admin reference.

CareerBuilder recruiter and hiring manager accounts are mapped to Recruit CRM User records by email address match. Owner assignments on Jobs, Candidates, and Applications resolve to the corresponding Recruit CRM User. Permissions and role structures vary between platforms and are documented in the migration handoff; Recruit CRM role assignment is the customer's responsibility post-migration.

CareerBuilder job board distribution logs (which boards received each posting, posting dates, spend per board) are not exposed in any customer export. We do not migrate this object. Customers who need historical ROI data by board should capture Recruit CRM's built-in job board analytics from the date of first posting in the new system.