Migrate from Smart Hire to Bullhorn ATS & CRM

Smart Hire Candidate records map to Bullhorn Candidate with name, email, phone, address, work history, education, and skills preserved. We parse the main profile CSV and any linked screening session records, then write Candidate records via Bullhorn REST API. The candidate's primary email becomes the dedupe key. Custom properties export as free-text key-value pairs in Smart Hire; we detect type mismatches (dates stored as strings, booleans as yes/no text) during profiling and apply type-coercion before insert.

Smart Hire Job Openings map to Bullhorn JobOrder with title, department, location, employment type, and description. We preserve the original job ID as a custom field for cross-reference. Pipeline stages (Applied, Screening, Interview, Offer, Hired) from Smart Hire map to Bullhorn JobOrder status values, with the stage ordering and naming preserved per job.

Smart Hire Screening Sessions link a candidate to a specific assessment round. Bullhorn has no native screening session object, so we provision a Custom Object via Bullhorn Support ticket if the customer is on Bullhorn ATS or Enterprise tier (ATS Growth does not support Custom Objects). Each screening session becomes a Custom Object instance linked to the Candidate record, capturing session date, assessment type, and status. If the edition does not support Custom Objects, we attach session metadata as custom fields on the Candidate record.

Smart Hire stores assessment scores and competency rankings in internal scale format. Bullhorn does not have a native psychometric store; we map raw scores, percentile ranks, and competency ratings to Bullhorn Custom Object fields. Score normalization requires us to validate score ranges during pre-migration profiling because Smart Hire's scale may not match any standardized benchmark. We preserve the raw numeric value and the scale label as separate fields rather than converting to a non-equivalent Bullhorn scale.

Smart Hire stores candidate-to-job associations as foreign key IDs in the candidate and job export files. When these span multiple CSV files, the association can fragment. We reconstruct the link by matching candidate IDs to application records during the transformation phase, then write Bullhorn JobSubmission records that link the Candidate and JobOrder. A reconciliation step confirms every migrated candidate is attached to at least one job opening before cutover.

Smart Hire resumes and supporting documents export as downloadable files linked to candidate records. We export these as binary assets, map file type and content to Bullhorn's attachment handling, and attach them to the corresponding Candidate record via ContentDocumentLink. If the resume content was parsed into Smart Hire's structured fields (rather than stored as a file), we ensure that parsed data is reflected in the Candidate's description or skills fields.

Smart Hire user accounts with role assignments map to Bullhorn User records. We resolve users by email match against the Bullhorn destination org. Any Smart Hire user without a matching Bullhorn User goes to a reconciliation queue for your admin to provision before record import resumes. Role terminology differs between platforms; Smart Hire's recruiter role maps to Bullhorn's internal recruiter assignment field.

Smart Hire's per-job pipeline stages (Applied, Screening, Interview, Offer, Hired) map to Bullhorn JobOrder status values. We extract the full stage configuration from Smart Hire including stage names, ordering, and any custom stage definitions, then configure matching status values in Bullhorn. If Smart Hire has stages not present in Bullhorn's standard list, we create custom status values.

Smart Hire custom fields on candidate records export as free-text key-value pairs. During profiling we detect type mismatches (dates stored as strings, numeric IDs stored as text) and apply coercion. Custom fields are mapped to Bullhorn Candidate custom fields if the destination supports them, or to Custom Object fields on the Candidate entity. Field names from Smart Hire are preserved as labels with API-safe names generated for Bullhorn.

Smart Hire custom fields on job openings (such as internal requisition codes, department-specific attributes, or compensation bands) map to Bullhorn JobOrder custom fields. We read the full custom property schema during profiling, map each field to an equivalent Bullhorn field or create a custom field, and validate that required fields on Bullhorn JobOrder are populated.

Smart Hire's talent pipeline management stores candidates in pools for future openings. We map talent pool membership to Bullhorn Candidate records with Tag or List membership. If the destination Bullhorn instance has Bullhorn Pro or Enterprise with automation, we map pool membership to a Bullhorn List or Tag that the customer's team can use to filter for future job submissions.

Smart Hire's custom career sites and white-label branding are platform-specific and cannot be exported as structured data. We document the career site URL, page structure, and any embedded Smart Hire job board references so your Bullhorn admin can configure Bullhorn Career Portal or a third-party career site builder post-migration. This is a manual rebuild item outside data migration scope.