Migrate from TalentRecruit to Bullhorn ATS & CRM

TalentRecruit job records map to Bullhorn JobOrder. The source job title, description, department, location, hiring manager assignment, and opening count migrate directly. TalentRecruit's configurable stage sequence for each job type maps to Bullhorn Record Types and Sales Processes that we configure before migration, preserving the customer's stage-count and approval-chain structure. JobOrder status (Open, Closed, On Hold) migrates directly.

TalentRecruit candidate profiles (contact information, work history, education, skills, resume files, and tags) map to Bullhorn Candidate records. Resume file attachments migrate as ContentDocument records linked via ContentDocumentLink to the Candidate. Candidate tags from TalentRecruit's flat label arrays migrate to Bullhorn's native tag system or to a custom multi-select picklist field depending on the tag cardinality.

TalentRecruit application records linking a candidate to a job map to Bullhorn JobSubmission. Current stage, stage-transition timestamps, and source channel migrate. The stage name maps to the corresponding Bullhorn JobSubmission status within the configured Sales Process. If TalentRecruit tracks a custom rejection reason or disposition, we map it to a custom field on JobSubmission.

Interview records from TalentRecruit include scheduled datetime, interviewer panel, calendar-integration references, and scorecards with free-text feedback. Scorecard templates vary per tenant and do not map to a native Bullhorn entity, so we flatten them into Note records attached to the JobSubmission with structured key-value pairs in the Note body, plus a Task record representing the interview activity on the Candidate timeline. The customer chooses between Note-flattening and a Bullhorn Custom Object for scorecards during scoping.

TalentRecruit posting records track which job boards and career pages a requisition was published to, with posting date and status per channel. We export the posting manifest as a structured list. Bullhorn does not have a native JobPosting entity for multi-channel status tracking, so we create a lightweight Bullhorn Custom Object or map the posting manifest to Note records on the JobOrder, with one Note per channel for visibility.

Assessment scores and test results stored as linked records against a TalentRecruit application migrate to a Bullhorn Custom Object (if the customer is on Front Office Growth or Enterprise) or to a structured Note attached to the JobSubmission. Assessment type, score value, completion timestamp, and vendor name transfer. Proprietary third-party assessment vendor formats are not transformed; the raw score and metadata are preserved for the customer's admin to re-enter in the vendor portal if needed.

TalentRecruit offer records include salary, benefits summary, start date, and approval status. Bullhorn does not have a native Offer entity separate from Placement, so we map offer fields to Bullhorn Placement (billing rate, pay rate, start date, end date, and status) plus a Note carrying the full offer terms for audit trail. Signed offer letter PDFs migrate as ContentDocument attached to the Placement.

TalentRecruit onboarding documents, task checklists, and task-completion status linked to the hired application migrate to Bullhorn. The checklist structure and completion state transfer to a Bullhorn Custom Object or to Note records on the Placement. Onboarding completion state resets at the destination; the original completion timestamps and checklist status are preserved in the migrated data for the customer's admin to re-enter in Bullhorn's onboarding module or a third-party onboarding tool.

TalentRecruit user accounts, role assignments, and team membership are exported and mapped to Bullhorn User records. Roles from TalentRecruit map to Bullhorn permission groups and team structures. Users must be re-provisioned in Bullhorn by the customer's admin; we export the permission taxonomy as a reference spreadsheet. The Bullhorn migration user must have Modify All Data and API permissions; we coordinate this with the customer's Bullhorn admin before production migration begins.

TalentRecruit candidate and application tags stored as flat label arrays migrate to Bullhorn native tags or to a custom multi-select picklist field on Candidate, depending on the tag volume and whether the customer wants tag-based filtering in Bullhorn's standard search. The full tag vocabulary is preserved. Bullhorn's tag system is entity-level; if tags need to be scoped per entity (Candidate versus JobSubmission), we recommend a custom multi-select picklist approach.

TalentRecruit client records map to Bullhorn ClientCorporation. Company name, address, industry, website, and primary contact information migrate directly. ClientCorporation is the top-level organizational entity in Bullhorn; it must be created before any Candidate or JobSubmission that references it.

Free-text notes attached to TalentRecruit candidates, jobs, or applications migrate to Bullhorn Note records linked via ContentDocumentLink to the parent record. Note creation timestamps, author information, and rich-text body (including embedded images as separate ContentDocument records) are preserved. Bullhorn Note is the standard entity for unstructured commentary on any Bullhorn entity.