Migrate from JobScore to Bullhorn ATS & CRM

JobScore Candidate records map directly to Bullhorn Candidate. We extract name, email, phone, address, tags, notes, and resume blob. JobScore's phone-number deduplication logic during bulk import is flagged pre-migration; we detect phone collisions in the export and present the customer with skip, merge, or overwrite options before loading. Bullhorn Candidate requires an owning User assignment resolved by email match against the destination User table.

JobScore published Jobs map to Bullhorn JobOrder. Only published jobs appear in JobScore's v2 API and job feed; unpublished/draft jobs are invisible to the API and require manual extraction. We warn customers to publish all roles before migration and cross-reference the API export against the admin job list to surface any missing jobs. Title, description, location (mapped to Bullhorn address fields), employment type, and salary range transfer as typed fields. Job status (Open, Paused, Closed) maps to Bullhorn JobOrder status values.

JobScore Application records (the Candidate-to-Job join) map to Bullhorn Candidate records with a JobOrder reference. Bullhorn natively links Candidates to JobOrders through the CandidateJobOrder join entity. Application date, stage, stage history timestamps, and custom form field responses transfer. Disposition codes (Declined, Withdrawn reasons) migrate to Bullhorn CandidateJobOrder status values.

JobScore Interview records (scheduled events tied to Application) map to Bullhorn Appointment records with interviewer assignment, date, type, and outcome preserved. Bullhorn Appointment links to the Candidate and JobOrder. For interviews without a calendar-level record, we attach as a Note with interview metadata. We resolve the Application uid to the corresponding Bullhorn CandidateJobOrder at migration time.

JobScore Scorecards (post-interview ratings and comments submitted by interviewers) migrate as Bullhorn Note records attached to the corresponding Appointment or Candidate. Ratings, comments, interviewer uid, and submission timestamp transfer. If the customer uses Bullhorn's built-in scorecard templates post-migration, we document the scorecard schema separately for admin configuration.

JobScore Location records (address, city, state, country) map to Bullhorn JobOrder address fields. We map each location component to the corresponding Bullhorn field and validate address completeness during the load.

JobScore Documents linked to Candidates (resumes, cover letters, attachments) export as binary blobs and reattach to the Bullhorn Candidate record. Bullhorn parses resumes natively. Resume parsing is included in Bullhorn Starter and above; we attach the raw blob so the parser populates structured fields in Bullhorn.

JobScore Users/Employees who appear as interviewers, owners, or recruiters on any record resolve by email match against Bullhorn Users. Users without a Bullhorn match enter a reconciliation queue for admin provisioning before record migration begins. JobScore's unlimited-user model means owner assignment density can be high; we batch-resolve all distinct owner emails before the main migration run.

JobScore custom form fields per job store responses at the Application level. We extract the full custom field schema from the source account, map each field to a Bullhorn CandidateJobOrder custom field (with __c suffix), and pre-create the field definitions in the Bullhorn org before import. Custom field types (text, picklist, number, date) map to equivalent Bullhorn field types.

JobScore's five locked top-level stages (New, Active, Declined, Withdrawn, Hired) map to Bullhorn CandidateJobOrder status values. Custom Active sub-stages collapse into the Active status with the original sub-stage name stored as a custom field on CandidateJobOrder for audit and reporting continuity.

JobScore tags on Candidates migrate to Bullhorn Candidate categories if the customer enables the Bullhorn categories feature, or to a custom text field (multi-select or comma-separated) on the Candidate record. The customer selects the strategy during scoping.

JobScore configurable disposition codes (Declined reasons, Withdrawn reasons) migrate to Bullhorn CandidateJobOrder status values. We export all configured codes from JobScore and create equivalent values in Bullhorn before migration so reporting continuity is maintained.