Migrate from In-recruiting to Bullhorn ATS & CRM

In-recruiting Candidate records map to Bullhorn Candidate. The In-recruiting candidateID becomes Bullhorn's candidateID; firstName, lastName, email, phone, and address fields map directly. We flag any In-recruiting custom fields on Candidate (for example, availability windows, source channel, or salary expectations) that need to map to Bullhorn Candidate custom fields. Bullhorn's Candidate entity supports custom fields and Custom Object associations per record.

In-recruiting Job records map to Bullhorn JobOrder. The job title, description, address, employmentType, and payRate fields map directly. In-recruiting's jobStatus (Active/Paused/Closed) maps to Bullhorn's JobOrder status. JobOwner (the assigned recruiter) maps to Bullhorn's JobOrder ownerId via User lookup by email.

In-recruiting Application records (the join entity between Candidate and Job) map to Bullhorn JobSubmission. The applicationDate and currentStage map to JobSubmission dateSubmitted and the assigned opportunityStage. We preserve the full application history (stage transitions with timestamps) as Bullhorn JobSubmission status-change records or as Note attachments on the JobSubmission if the stage history is not representable through standard status values.

In-recruiting's custom pipeline stages (for example, 'Phone Screen', 'Technical Interview', 'Offer', 'Rejected') map to Bullhorn opportunityStage values on the corresponding JobSubmission. Bullhorn predefines standard stage values; custom stage names require Bullhorn Support or an admin with stage-configuration access to add values to the opportunityStage picklist before migration. We validate the picklist during scoping and configure any missing values as part of the destination schema setup.

In-recruiting Interview records map to Bullhorn Appointment. The interviewDate, interviewer (linked User), interviewType, and outcome map to Bullhorn Appointment's startDateTime, endDateTime, userID (interviewer), type, and outcome fields. Candidate and JobOrder associations map to Bullhorn's candidateID and jobOrderID on the Appointment. Interview scorecards or feedback notes migrate as Note attachments to the Appointment.

In-recruiting Client records map to Bullhorn ClientCorporation. The company name, address, industry, website, and billingContact fields map directly. In-recruiting client records that include both organizational and contact-level data require a split: the company-level fields go to ClientCorporation and any primary contact fields go to a corresponding ClientContact record linked to the ClientCorporation.

In-recruiting contact records associated with a Client map to Bullhorn ClientContact. The contact name, email, phone, title, and department map directly. ClientContact is linked to ClientCorporation via the clientCorporationID foreign key, which we resolve at migration time after ClientCorporation records are created.

In-recruiting Placement records (candidates successfully placed in jobs) map to Bullhorn Placement. The candidateID, jobOrderID, startDate, endDate, payRate, billRate, and placementStatus map to Bullhorn Placement fields. In-recruiting's placement history preserves as Bullhorn Placement records with their original start dates, enabling reporting on historical placement data in Bullhorn.

In-recruiting User records (recruiters, admins, hiring managers) map to Bullhorn User. We resolve by email match across both systems. Any In-recruiting User without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. OwnerId references on JobOrder, JobSubmission, and Placement require a valid Bullhorn User at migration time.

In-recruiting Notes attached to Candidates, Jobs, Applications, or Clients map to Bullhorn Note. The note text, author, and creation date migrate. Bullhorn Note is linked via ContentDocumentLink to the parent entity (Candidate, JobOrder, JobSubmission, ClientCorporation, ClientContact, or Placement). Rich-text formatting in In-recruiting Notes converts to plain text or HTML depending on Bullhorn's Note body field support.

In-recruiting engagement records (calls, emails, tasks logged against Candidates or Applications) map to Bullhorn Task. The activity type, date, duration, outcome, and description map to Bullhorn Task fields. Call activities migrate as Task with taskSubtype=Call and duration preserved. Email activities migrate as Task with type=Email and the body preserved. We resolve the target entity (candidateID, jobSubmissionID) at migration time via lookup.

In-recruiting custom fields that do not map to standard Bullhorn fields migrate to Bullhorn Custom Objects or custom fields on the standard entity. Bullhorn Front Office Growth and Enterprise editions support up to 10 Custom Objects with 55 fields each; ATS Growth supports 2; standard ATS Growth entry has none. We design the Custom Object schema during scoping, submit the Custom Object Setup Sheet to Bullhorn Support before migration, and map In-recruiting field values into the configured Custom Object fields during data load.

In-recruiting tags or labels applied to Candidates, Jobs, or Applications migrate to Bullhorn custom multi-select picklist fields on the relevant entity. We identify the full tag vocabulary during scoping and configure Bullhorn multi-select picklist values to match before migration. Tags used for candidate segmentation migrate to Bullhorn Topics with TopicAssignment records if the customer uses Bullhorn's topic taxonomy.