Migrate from CareerBuilder Applicant Tracking to Bullhorn ATS & CRM

CareerBuilder Candidate records map 1:1 to Bullhorn Candidate. We preserve all standard profile fields (name, email, phone, address, source attribution), and we flag every record where the most recent resume update timestamp is older than 18 months so the customer can suppress stale profiles or accept them as-is. Resume files migrate as binary attachments mapped to the corresponding Bullhorn Candidate record in batches of 50 files to avoid timeout errors.

CareerBuilder Jobs (title, description, department, location, employment type) map directly to Bullhorn Job records. We extract the full pipeline stage schema during discovery and map each CareerBuilder stage name to the equivalent Bullhorn JobOrder status value or ATS v2 stage picklist. Any job with an applicant count near the 10-13 cap is documented separately so the customer's Bullhorn admin can reopen sourcing immediately after cutover.

CareerBuilder Applications link Candidates to Jobs with submission date, current pipeline stage, and routing history. For Bullhorn ATS (ATS v1), Applications map to SubmitCandidate records with each stage tracked as a separate record. For Bullhorn Recruitment Cloud (ATS v2), Applications map to Application V2 with the Stage picklist updated to reflect the current stage and Application History records preserving the full stage progression. We confirm the customer's ATS data model during discovery.

CareerBuilder talent network members are stored separately from active job applications. We map these to Bullhorn Talent Pools with the original CareerBuilder pool name preserved as the talent pool name in Bullhorn. Candidate pool membership migrates as a bulk-add operation per pool, and the customer's Bullhorn admin can create additional segmentation or CRM-style lists post-migration.

CareerBuilder pipeline stages (Applied, Screening, Interview, Offer, etc.) vary by customer configuration. We extract the complete stage list from CareerBuilder during discovery and map each to Bullhorn's JobOrder Status values (for ATS v1) or the TR1__Stage__c picklist (for ATS v2). Stage probability percentages transfer where CareerBuilder stores them. Bullhorn's Field Maps UI controls which stage values appear per job, and we configure these before the first job import.

Recruiter-assigned numeric ratings and structured scorecards from CareerBuilder migrate as custom numeric fields on the Bullhorn Candidate record. We create the destination custom fields during the schema design phase and map each CareerBuilder rating property to its Bullhorn equivalent by field name and data type. Scorecard templates do not migrate as templates; individual candidate scores transfer as field values.

Email threads and recruiter notes attached to CareerBuilder Candidates migrate as chronological activity records in Bullhorn. We preserve sender, timestamp, and body text. Attachment filenames are mapped to the Bullhorn candidate record, but full attachment files are migrated as binary file links rather than inline content unless the customer specifies otherwise.

CareerBuilder customers with custom fields on candidate profiles (inherited from the Luceo era in some legacy accounts) are extracted with field name, data type, and all values. We create matching custom fields in Bullhorn during the schema phase and map values during import. Bullhorn's Field Maps controls field visibility, required status, and dropdown option lists for migrated custom fields.

CareerBuilder user accounts are mapped to Bullhorn User records by email match. We resolve every distinct owner referenced on Candidate, Job, and Application records and hold any owner without a matching Bullhorn User in a reconciliation queue. The customer's Bullhorn admin provisions missing Users before record import proceeds, since OwnerId is required on most standard Bullhorn objects.

CareerBuilder's job board distribution logs (which boards received each posting, posting dates, spend per board) are not exposed via any documented export. We do not migrate this object. Customers who need to preserve their job board ROI history capture that reporting manually before the migration cutover date. Post-migration, Bullhorn's native job distribution and the Bullhorn Marketplace job board integrations replace CareerBuilder's distribution reporting.

CareerBuilder calculates time-to-fill, source effectiveness, and recruiter performance as dynamic reports derived from live data, not as stored historical objects. Historical reports are not migratable. Bullhorn Canvas provides staffing-specific reporting from the moment migration completes; we do not recreate CareerBuilder's historical report data in Bullhorn.

CareerBuilder workflow rules and automated candidate engagement emails do not migrate as automation code. We deliver a written inventory of every active CareerBuilder workflow with its trigger, conditions, and actions, plus a recommended Bullhorn Automation equivalent. Bullhorn Automation (formerly Herefish) uses a different automation model with email and text sequences, GDPR consent management, and candidate engagement tracking. The customer's Bullhorn admin or a Bullhorn partner rebuilds these post-migration.