Migrate from SmartRecruiters to Bullhorn ATS & CRM

SmartRecruiters Posting records map to Bullhorn JobOrder. We preserve the refNumber, job title, description, and typeOfEmployment. Location maps to Bullhorn's address fields and city/state/country. The SmartRecruiters experienceLevel maps to a Bullhorn custom field since JobOrder does not have a native experience level field. Department reference is preserved as a text label in a custom field since Bullhorn Jobs do not have a native department link. Any active posting status in SmartRecruiters becomes a Bullhorn Job with status = 'Open'.

SmartRecruiters Candidate records map directly to Bullhorn Candidate. Required fields (firstName, lastName, email) transfer directly. Phone, address, social profiles (LinkedIn URL), and tags migrate to corresponding Bullhorn Candidate fields. We deduplicate by email during import. Candidate history and source attribution migrate to Bullhorn Candidate custom fields.

SmartRecruiters Application records (linking Candidate to Posting) map to Bullhorn JobSubmission. Bullhorn's REST API only creates JobSubmission in New status; we run a two-step import where records land as New then advance to the target pipeline stage via a separate API call using the JobSubmission ID. The SmartRecruiters application date becomes the Bullhorn dateAdded. Screening answers migrate as JobSubmission custom fields.

SmartRecruiters organization-scoped custom fields (discovered via /configuration endpoint) map to Bullhorn Custom Objects. Bullhorn requires Custom Objects to be provisioned via Bullhorn Support ticket before any API import; we coordinate this during scoping. Edition limits apply: Front Office Growth/Enterprise gets 10 Custom Objects with 55 fields each; Bullhorn ATS gets 2; ATS Growth gets none. Field types (text, drop-down, checkbox) map from SmartRecruiters fieldId/valueId structure to Bullhorn edit types. This is the highest-risk mapping step and requires pre-migration field discovery.

SmartRecruiters Department records (with description and label) map to Bullhorn Department entities. Bullhorn Department is a standard entity in the ATS and CRM modules. We preserve the department label and ID so that job postings reference the correct Bullhorn Department. Note that Bullhorn Jobs do not natively reference Department; we use a custom field on JobOrder to maintain the link.

SmartRecruiters User records (recruiters, hiring managers, admins) map to Bullhorn User. We match by email as the dedupe key. Bullhorn requires User provisioning by a Bullhorn Admin or through Bullhorn Support for initial setup. We resolve all User references on Candidate, Job, and Application records before migration. Any SmartRecruiters User without a Bullhorn User counterpart goes to a reconciliation queue.

SmartRecruiters hiring team assignments (userId with role per job) map to Bullhorn JobSubmission assignments and JobOrder owner relationships. The recruiter role migrates to the Bullhorn User assigned as the primary recruiter on the Job. Hiring manager visibility is preserved via Bullhorn User assignment on the JobSubmission. Role labels (interviewer, screener, approver) migrate as JobSubmission custom fields since Bullhorn does not have a native role per assignment.

SmartRecruiters Scorecards (structured evaluation data embedded in candidate/evaluation records) map to Bullhorn Note records attached to the JobSubmission. We extract the evaluation score, recommendation, and interviewer name into a structured note format that preserves the evaluation history. If the destination Bullhorn edition supports Bullhorn Automation for scorecard workflows, we note this for the customer's admin to configure post-migration.

SmartRecruiters Interview records (scheduling, interviewer assignments, outcome notes) map to Bullhorn Event (Appointment) records linked to the Candidate and JobSubmission. Interview dates, times, locations, and dispositions migrate directly. Interviewer names resolve to Bullhorn User IDs where possible; unresolved interviewers are recorded as text in the event description. Outcome status (completed, cancelled, no-show) migrates as an Event custom field.

SmartRecruiters Offer records (compensation, status, candidate linkage) migrate to Bullhorn as Placement records with offer compensation fields in Bullhorn's standard Placement object plus custom fields for offer-specific data (offer date, offer letter reference, start date). Note that Bullhorn Placement is typically created after a candidate is placed; we create the Placement record during migration to preserve offer history even if the offer was not accepted or the placement was not completed. Status (extended, accepted, declined, withdrawn) maps directly.

SmartRecruiters candidate attachments (resumes, cover letters, portfolio files) stored against the candidate profile migrate to Bullhorn Attachments linked to the Candidate record. We use Bullhorn's Attachment API with file type and description preserved. Large attachments may require chunked upload via Bullhorn's REST API. We verify each attachment link after migration by checking the file reference in Bullhorn.

SmartRecruiters Assessment packages ordered via /packages are integration-specific and may not have a direct Bullhorn equivalent. We migrate assessment order records (assessment type, order date, status) as custom fields on the relevant JobSubmission. Active assessment status (pending, completed, failed) migrates as a custom picklist field. If the customer uses a specific assessment partner that also integrates with Bullhorn, we coordinate with that partner during migration scoping.