Migrate from 100Hires to Bullhorn ATS & CRM

100Hires Jobs migrate directly to Bullhorn Job records. We preserve job title, description, employment type, pay rate, and status. Bullhorn Job requires a ClientCorporation reference, so we create or look up the ClientCorporation first and attach it before job insert. Job publishing status (active/paused/closed) maps to Bullhorn's status field; any job board distribution settings in 100Hires are documented for manual re-configuration in Bullhorn JobAd Distribution.

100Hires Candidates map to Bullhorn Candidate records. The primary email is the dedupe key. Bullhorn Candidate requires a clientCorporation reference (unlike 100Hires where Company is a sub-object), so we create a default ClientCorporation placeholder or map to an existing Bullhorn ClientCorporation if a company-level record exists. Candidate name, phone, address, and custom properties migrate as typed fields. We run email-based deduplication before insert to resolve records imported via 100Hires Chrome extension that may duplicate manually entered profiles.

100Hires Company records (stored as sub-objects on Candidate) are extracted as distinct rows and mapped to Bullhorn ClientCorporation. We use company name as the primary field and populate address, industry, and phone from 100Hires. ClientCorporation is inserted before Candidate import so that Candidate.clientCorporationID is satisfied at the moment of Candidate insert. If 100Hires candidates share a company without a formal Company record, we aggregate by domain or company name string before insert.

100Hires Application records (linking Candidate to Job with pipeline stage, timestamps, and rejection reasons) map to Bullhorn CandidateJobOrder (JobSubmission). We preserve the full pipeline stage history as CandidateJobOrder status changes with timestamps, and migration reason from 100Hires becomes a custom field on CandidateJobOrder. The CandidateID and JobID references are resolved from the preceding migration phases.

100Hires Interviews (scheduled dates, times, interviewers, interview types, calendar integration status) map to Bullhorn CandidateInterview records linked to the CandidateJobOrder. We preserve interview type, scheduled date and time, interviewer user references (resolved via User mapping), and the G Suite calendar integration status as a custom field noting re-authentication is required in Bullhorn.

100Hires custom evaluation scorecards (with custom criteria and submitted scores) are exported with their form definitions. Bullhorn's standard reference check feature does not cover general interview evaluations, so we either populate custom fields on CandidateInterview (if criteria count is low) or create a Bullhorn custom object for evaluations with a lookup to Candidate. The scoring rubric (e.g., 1-5 scale vs pass/fail) must be explicitly mapped; we flag any unresolvable custom criteria in the pre-migration audit and document them for Bullhorn admin reconfiguration.

100Hires Notes attached to Candidates or Applications migrate to Bullhorn Note records linked via BULLHORN entity associations. Note body, author (resolved to Bullhorn User by email), and creation timestamp are preserved. Bullhorn Note uses a body field and a commentCount field; we map the original author as a custom field if the Bullhorn Note author attribution behavior differs from the source.

100Hires email conversations (Message objects tied to Candidates or Applications) migrate to Bullhorn Note records with a message-type indicator. Email subject, body, sender, and recipient are preserved. External email threads that originated in Gmail or LinkedIn and were imported into 100Hires via Chrome extension may require thread-context reconciliation; we flag these in the audit report.

100Hires Users (recruiters and team members) map to Bullhorn User records by email address. Role and permission assignments in 100Hires do not map directly to Bullhorn role-based access control because Bullhorn permissions are structured around Bullhorn-specific permission sets. We document the 100Hires role assignments for the customer's Bullhorn admin to reconfigure permissions post-migration.

100Hires Attachments (resumes, cover letters, portfolio files) linked to Candidates or Applications migrate to Bullhorn CandidateAttachment records. We download binary files from 100Hires, preserve filenames and parent record associations, and re-upload to Bullhorn with the appropriate entity reference. Large portfolio files are chunked for re-upload if the Bullhorn attachment API enforces size limits.

100Hires Skills taxonomy is exported as a flat list and mapped to Bullhorn Skill records. Bullhorn Skill is a standard object linked to Candidate via CandidateSkill. We deduplicate skill names during export (normalizing case and removing duplicates) before bulk-inserting into Bullhorn. Skills with no exact match are flagged for admin review.

100Hires Departments taxonomy maps to a Bullhorn custom picklist field on Job (or to a Category object if the Bullhorn edition supports it). We export department names as distinct values and populate the destination field during job import. If no equivalent exists, we document the department list for Bullhorn admin to configure as a custom field.

100Hires Locations taxonomy is exported and mapped to Bullhorn Job location fields (city, state, country) or a custom location field. We parse the 100Hires location string and split into structured address components for Bullhorn's address model.

100Hires Email Templates (body content, subject lines, placeholder tokens) migrate as Bullhorn EmailTemplate records. We export templates as raw text with token syntax preserved and document the placeholder format differences between 100Hires and Bullhorn token syntax so the customer's Bullhorn admin can update template tokens post-migration.