Migrate from TalentNest to Bullhorn ATS & CRM

TalentNest Jobs map 1:1 to Bullhorn JobOrder records. Each TalentNest Job's title, description, location, and status transfer directly. Bullhorn's employmentType field on JobOrder captures the hire type (Direct Hire, Contract, etc.). For TalentNest jobs with multiple workflow variants (e.g., same role hired as W2 vs 1099), Bullhorn's Tracks feature (Enterprise) lets you configure Track I, Track II, etc. with different field visibility. We map TalentNest stage definitions to a written JobOrder configuration document so your Bullhorn admin recreates the stage sequence in Bullhorn's workflow builder.

TalentNest Candidate profiles (contact details, resume, demographics, notes) map directly to Bullhorn Candidate records. The candidate's name, email, phone, and address fields migrate as typed fields. Resume files migrate as Bullhorn Candidate attachments linked via ContentDocumentLink. We resolve the TalentNest candidate email as the dedupe key to prevent duplicate Candidate creation if the candidate applied to multiple jobs.

TalentNest Application junction records (linking a Candidate to a Job with status, rating, and stage history) map to Bullhorn JobSubmission. The application status maps to Bullhorn's application status field, and the stage transition history migrates as a sequence of status-change records with timestamps. We source submission timestamps from TalentNest's audit trail to avoid the application-date-reset issue.

TalentNest stores proprietary screening scores as job-specific custom fields on Applications with no standardized schema across jobs. We export all screening fields as key-value pairs and map them into Bullhorn Custom Objects (up to 10 for Front Office Growth/Enterprise, 2 for Bullhorn ATS). Bullhorn Support must create the Custom Object definitions; we provide a field specification spreadsheet with field names, types, and Bullhorn-equivalent edit types (text, drop-down, numeric). Assessment scores that exceed the 55-field Custom Object limit are split across two Custom Objects.

TalentNest stage-based workflow automation (email triggers, SMS triggers, stage conditions) does not migrate as functional code. Bullhorn's workflow automation lives in Bullhorn Automation (Herefish) or is rebuilt by the admin in Bullhorn's workflow builder. We export the full stage definition including trigger actions, email template bodies, and automation rules as a structured configuration document. Your Bullhorn admin uses this to recreate stages in Bullhorn's JobOrder setup.

TalentNest User accounts with roles and access permissions map to Bullhorn User records. We resolve by email match. Any TalentNest User without a matching Bullhorn User goes to a reconciliation queue for your Bullhorn admin to provision before record import resumes. Hiring manager assignment on Jobs migrates as the Bullhorn User on the JobOrder record.

Recruiter notes attached to candidate profiles in TalentNest migrate to Bullhorn Note records linked via ContentDocumentLink to the Candidate record. Author, timestamp, and full note body are preserved. Bullhorn Note supports up to millions of characters per note, which accommodates even lengthy assessment notes from TalentNest.

Referral source data on TalentNest Applications (available on Business and Enterprise tiers) migrates to a Bullhorn custom field on Candidate. If your TalentNest account was on Starter or Growth, referral data is absent (null) and we surface this as a tier-gap note. We flag any candidates who were referred so your Bullhorn admin can configure a referral source tracking workflow post-migration.

TalentNest's Talent CRM (Growth and above) stores candidate profiles outside of active job applications. We export all CRM candidate records and map them as Candidate records in Bullhorn. Candidates with no active application in TalentNest land in Bullhorn as Candidate records without a JobSubmission; we flag these as CRM-pool records so your Bullhorn admin can configure them as a talent pool or source list.

TalentNest email and SMS templates tied to workflow stages export as template body and metadata records. Since template IDs are proprietary to TalentNest, they cannot be re-imported into Bullhorn. We deliver a template inventory document listing every TalentNest template with its body, trigger conditions, and stage association so your Bullhorn admin creates equivalent Bullhorn email templates and SMS templates in Bullhorn Automation or Bullhorn's native template builder.

TalentNest's 30+ board distribution configuration per Job is exported as a distribution list property. Bullhorn's native job distribution covers Indeed, LinkedIn, and major aggregators but does not natively replicate all 30+ TalentNest boards. We provide a job-board distribution log mapping each TalentNest board to its Bullhorn-equivalent or third-party integration (if available), and your Bullhorn admin configures distribution per JobOrder post-migration.

TalentNest pre-screen and demographic custom fields on Applications export with field types, labels, and answer options. We map each to a Bullhorn custom field on JobSubmission or Candidate, using the appropriate Bullhorn field type (text, drop-down, numeric, checkbox). Bullhorn field character limits vary (some capped at 100 characters, others at millions); we analyze your TalentNest data to ensure no truncation occurs during import.