Migrate from Talexio to Bullhorn ATS & CRM

Talexio People profiles function as unified employee and candidate records. We migrate the core profile fields (name, email, phone, address, LinkedIn, skills) directly to Bullhorn Candidate. Employment history within the Talexio profile maps to the Candidate's workHistory custom text area or a WorkHistory CustomObject depending on field length. Talexio profile photos migrate as ContentDocument records linked via ContentDocumentLink to the Candidate.

If the Talexio deployment includes client-facing contacts (external hiring managers stored in Talexio rather than a separate CRM), we map these to Bullhorn Contact. Contact records are differentiated from Candidate records at migration time by a flag set during discovery. Talexio does not have a separate Contact object; the distinction is enforced through Talexio's record type or a custom profile attribute that we enumerate during scoping.

Talexio Employment Positions capture role changes, salary adjustments, and effective dates against a single People profile. Each Position entry maps to a Bullhorn Placement record, preserving job title, start date, end date, salary, and employment type. Active Positions map to open Placements; historical Positions map to closed Placements with a placementStatus of Lost or Left. We preserve the Talexio position hierarchy as Bullhorn Placement custom fields for audit.

Talexio recruitment job postings and pipeline stages map to Bullhorn JobOrder. The Talexio job title, description, department, and employment type migrate directly. Talexio pipeline stages (Applied, Screening, Interview, Offer, Hired) map to Bullhorn JobOrder status values and JobSubmission pipeline stages. JobOrder is created before any JobSubmission records so that the JobOrderID lookup is satisfied at submission insert time.

Talexio applications (a candidate applying to a Talexio job posting) map to Bullhorn JobSubmission records linking a Candidate to a JobOrder. If a Talexio candidate applied to multiple Talexio jobs, each application becomes a separate JobSubmission under the same Candidate. The Talexio application date, source, and stage status map to Bullhorn JobSubmission dateAdded, source, and status.

Talexio candidates who have not yet been placed but are in active sourcing (in-talent-pool candidates not attached to a specific job) map to Bullhorn Lead records. Lead captures the candidate name, contact details, skills, and source. The Talexio profile rating or score maps to a Bullhorn Lead custom field leadScore__c. When a Lead is later attached to a JobOrder, it converts to a JobSubmission.

Talexio Onboarding Assistant packages and step completion status map to Bullhorn Placement onboarding fields and attached Note records. Completed steps are recorded as Note entries with timestamps. Step names and completion dates migrate; the step configuration itself (the onboarding workflow template) does not migrate as code. We deliver a written onboarding workflow inventory for the Bullhorn admin to rebuild using Bullhorn's workflow tools or Bullhorn Automation Studio.

Talexio leave records (approved leave with type, balance used, and effective dates) have no native Bullhorn equivalent because Bullhorn is a staffing ATS rather than an HRMS. We create a Bullhorn Leave CustomObject with fields for leaveType, startDate, endDate, daysTaken, balanceRemaining, and approvalStatus. Each Leave record links to the Candidate via a CandidateID lookup. Leave entitlements (the employee's annual leave balance) migrate as a separate CustomObject record per employee.

Talexio clocking records (employee reference, date, clock-in/out timestamps, and work hours) map to a Bullhorn TimeLog CustomObject. We create the CustomObject schema in Bullhorn with fields for employeeReference, clockingDate, clockIn, clockOut, totalHours, and workType. Physical device clockings that were exported via USB before software sync are identified during the data audit (per Talexio's device clocking gotcha) and included in the export set before API extraction.

Talexio departments and cost centres map to Bullhorn ClientCorporation records used as internal organisation units or, if the deployment includes client companies, as ClientCorporation objects with their own corporate records. We export Talexio departments as reference data during scoping, recreate them in Bullhorn before any candidate or placement import, and use department references on Placement records as custom lookup fields or text fields depending on Bullhorn edition.

Talexio documents attached to People profiles and recruitment records migrate as Bullhorn ContentDocument records linked via ContentDocumentLink to the parent record (Candidate, JobOrder, or Placement). We enumerate all document types during data audit, export the binary files from Talexio via the reporting database or UI export, and upload them to Bullhorn with the correct ContentDocumentLink relationship. CVs and resumes attached to Talexio candidates parse into Bullhorn Candidate fields and also attach as ContentDocument records.

Talexio custom fields created on People profiles, Positions, and recruitment records map to Bullhorn custom fields on the corresponding destination object. Bullhorn supports custom fields on Candidate, ClientCorporation, JobOrder, JobSubmission, Placement, and Lead via its entity custom field API. We enumerate all custom fields during discovery (Talexio requires a support ticket to obtain the flattened schema), create the Bullhorn custom field definitions before migration, and map each field with type conversion (Talexio text to Bullhorn String, Talexio date to Bullhorn Date, Talexio dropdown to Bullhorn Picklist).