Migrate from Talent finder to Bullhorn ATS & CRM

Talent Finder Job records (title, department, location, description, status) map directly to Bullhorn JobOrder. We extract the field schema from the Talent Finder CSV export during discovery, align each column to the corresponding Bullhorn JobOrder field (title, department, city, state, description, status), and flag any Talent Finder taxonomy field that has no Bullhorn equivalent. JobOrder is loaded first because it is a required parent for any Application records.

Talent Finder Candidate records are split at migration time based on source attribution. Candidates sourced directly via Talent Finder's job board or application forms map to Bullhorn Candidate. Candidates sourced by agency recruiters or imported from external channels map to Bullhorn ClientContact (a separate entity). We use email address as the dedupe key across both destination entities and flag duplicates before insert. Name, phone, email, skills, work history, and source attribution migrate as typed fields.

Talent Finder Application records link a Candidate to a Job and track stage progression. These map to Bullhorn JobSubmission, which is the standard Bullhorn entity for tracking a candidate's journey through a job order. We preserve the full stage history including timestamps so that the destination reflects the original hiring pipeline state. The JobSubmission points to the migrated JobOrder and Candidate or ClientContact by ID.

Talent Finder User accounts with recruiter, hiring manager, or admin roles map to Bullhorn User. Role names from Talent Finder are mapped to Bullhorn's role equivalents (BullhornUser, Standard). We resolve owners by email match during migration and hold any User without a matching Bullhorn account in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.

Talent Finder configurable pipeline stages are mapped to Bullhorn JobOrder Record Types with corresponding Sales Processes that whitelist the applicable StageName values. We capture the stage name, display order, and probability percentage from Talent Finder and configure matching values in Bullhorn. Any Talent Finder stage without a direct Bullhorn equivalent is flagged during scoping and the customer chooses a fallback stage during review.

Talent Finder structured interview scorecard data (evaluations tied to a candidate and interviewer) is extracted as field values from the export and mapped to Bullhorn Candidate custom fields or a Bullhorn Custom Object if one is provisioned. Scorecard questions become field labels; rating values populate the corresponding fields. This requires Bullhorn Support ticket setup if the destination is Bullhorn ATS or ATS Growth edition due to their limited Custom Object availability.

Resume files and uploaded documents from Talent Finder are extracted from the CSV export (if stored as base64) or sourced from the file export directory, renamed to follow candidate-referenced conventions (CandidateID_resume.pdf), and loaded to Bullhorn as attachments on the Candidate record. Bullhorn's built-in resume parser runs on upload; we document the original parsed output for reconciliation since Bullhorn's parser reformats content and the original file serves as the authoritative record.

Talent Finder outreach emails, notes, and event timestamps migrate as Bullhorn Note records linked to the Candidate or ClientContact, and as Task records for time-stamped activity entries. HTML is stripped from email bodies to ensure clean display in Bullhorn. Communication type (email, call, meeting, note) is stored in a custom field on the Note or Task. Activity ordering is preserved by setting the timestamp to the original Talent Finder created date.

Talent Finder custom properties on Candidates require explicit field mapping. We extract the schema from the CSV export during discovery, display it for customer review, and map each field individually to Bullhorn Candidate standard fields or a CustomObject. Bullhorn edition tier determines whether CustomObject is available: ATS Growth = 0, Bullhorn ATS = 2, Front Office Growth/Enterprise = 10. Custom Object provisioning requires a Bullhorn Support ticket with the completed Custom Object Setup Spreadsheet.

Talent Finder custom properties on Applications map to Bullhorn JobSubmission custom fields or a CustomObject. Same edition-gating applies as for Candidate custom fields. We coordinate with Bullhorn Support for CustomObject creation before migration begins, and we configure the custom field schema in the Bullhorn instance via the Setup sheet before any Application data loads.

Talent Finder companies referenced in job postings or candidate work history map to Bullhorn ClientCorporation. Company name, address, industry, and contact information from Talent Finder populate the corresponding ClientCorporation fields. ClientCorporation is loaded before JobOrder if the job references a specific client, and before ClientContact if the contact belongs to a specific company.

Candidate records contain PII subject to GDPR and regional privacy laws. We flag every candidate record during migration scoping and strip or hash PII fields (national ID numbers, salary history, personal addresses) on request before loading into Bullhorn. The customer chooses the PII handling policy during discovery. This produces a clean record set that is audit-ready and compliant with the destination jurisdiction's data requirements.