Migrate from Talos ATS to Bullhorn ATS & CRM

Talos Candidate records map directly to Bullhorn Candidate. The Talos candidate record holds contact details, CV (as document), application history, and stage progression. We map the Talos firstName and lastName to Bullhorn Candidate name fields, email to the Candidate email field, and phone to the phone field. The Talos CV document migrates as a ContentDocumentLink attached to the Candidate record. All candidate custom fields discovered in the audit phase map to Bullhorn custom fields on the Candidate entity, subject to the per-entity custom field limit (2 custom objects with 55 fields each on Bullhorn ATS tier; 10 with 55 fields each on Growth/Enterprise). Talos candidate status flags (active, dormant, blacklisted) map to Bullhorn Candidate isDeleted and status fields with a custom status_reason__c field for blacklist attribution.

Talos Job records map to Bullhorn Job Order (JobPosting). The Talos job title, description, location, department, and status migrate as Bullhorn JobOrder.title, description, address, category, and status. Talos postingUrl maps to Bullhorn externalReference. Active and closed jobs migrate; the Bullhorn job status field reflects the Talos status (Open, Placed, Closed). If Talos jobs use custom internal job IDs, these map to a custom field job_customid__c on the Bullhorn Job Order for cross-reference.

Talos Application records link a Candidate to a Job and track stage progression. The mapping depends on the destination Bullhorn data model chosen during scoping. Under ATS v1, each Talos application generates multiple per-stage Submission records (one per pipeline stage) plus Job Reporting junction records; we map the Talos stage name to the corresponding Bullhorn Submission stage. Under ATS v2, a single Application V2 record is created per Candidate-Job pair with stage controlled by a picklist, and stage transitions generate Application History records. We determine the appropriate model based on the customer's Bullhorn edition and existing configuration, and document the stage mapping matrix before migration begins. Stage rules and automation triggers tied to Talos stage transitions do not transfer.

Talos allows fully custom stage names and arbitrary stage counts per job or pipeline. Bullhorn ATS v1 represents each stage as a separate Custom Object, while ATS v2 uses a Stage picklist on the Application V2 record. We extract the customer's Talos stage labels and consolidate or remap them based on the Bullhorn edition: Bullhorn ATS (2 custom objects) may require stage count reduction; Bullhorn Growth/Enterprise (10 custom objects) provides more flexibility. Bullhorn's standard stages (Application, Submittal, Interview, Offer, Placement) are used as the default label set, with Talos custom labels mapped as aliases. Stage probability percentages are set on Bullhorn Stage records during configuration.

Talos Interview records (date, interviewer, type, outcome notes) map to Bullhorn SendOut records for the submission-to-interview transition and to Event records for calendar and attendee tracking. The Talos interview type maps to Bullhorn SendOut type (Phone Screen, Video Interview, On-site, Technical). Interview outcome notes migrate as free-text on the SendOut record or as a Note attached to the Candidate. Talos video interview transcription content does not carry to Bullhorn as a native field; we flag this for the customer's admin to assess whether the transcription content should be stored as a Note or discarded.

Free-text notes attached to Talos Candidates and Applications migrate as Bullhorn Note records linked via ContentDocumentLink to the parent record (Candidate, Job Order, or Submission). Note timestamps and owner attribution migrate. Notes created by the Tali AI agent that contain auto-generated tagging or commentary are included as-is without transformation; we flag these during the audit phase so the customer is aware that AI-generated notes may not reflect the same context in Bullhorn.

Structured scoring rubrics and Assessment data from Talos require field-level mapping to Bullhorn. On Bullhorn ATS (2 custom objects), Assessment records may require consolidation into a single Custom Object with a section-header layout; on Bullhorn Growth/Enterprise (10 custom objects), each Assessment type can map to its own Custom Object. We discover Assessment field types during the data audit and create the corresponding Bullhorn Custom Object schema before migration. Assessment scores that use a Talos-specific rubric scale are preserved as numeric or text fields with a custom field rubric_scale__c documenting the original scale.

Talos Users assigned as owners on Candidate, Job, and Application records map to Bullhorn User records by email match. We extract all distinct Talos user references during the audit and validate against the Bullhorn destination User table before migration. Inactive or departed Talos users are flagged for reassignment; the customer's Bullhorn admin provisions any missing Users. OwnerId references on Bullhorn records (Candidate, Job Order, Submission) require a resolved User before insert.

Talos ATS stores client contacts within its multi-brand pipeline structure. When migrating to Bullhorn, these split into two records: Client Corporation (the employing organisation) and Contact (the individual within that organisation). We extract Talos client name and address data, create Bullhorn ClientCorporation records, then create Bullhorn Contact records linked via the clientCorporationId lookup. Multi-brand Talos deployments may have client records per franchise; we aggregate these into a single Client Corporation hierarchy in Bullhorn if the customer's Bullhorn configuration supports it.

Talos Offer records (compensation, start date, status) map to Bullhorn Placement. The Talos offer status (pending, accepted, declined, withdrawn) maps to Bullhorn Placement status values. Compensation details migrate to Placement payRate, billRate, and overtimeRate fields. Offer acceptance workflow state from Talos (including any e-Sign Docusign status) is flagged as a separate data pull since e-Sign records are stored in the Docusign integration, not in Talos core. We recommend a separate Docusign export and re-link signed offer documents to Bullhorn Placement records post-migration.

Talos custom fields on Jobs and Candidates are discovered during the data audit phase. Bullhorn custom fields on Candidate, JobOrder, and Submission entities are available up to the per-entity limit. If Talos custom fields exceed the Bullhorn field limit, we recommend creating a Custom Object with a lookup to the parent record. Multi-select and checkbox Talos field types map to Bullhorn Multi-Select Picklist and Checkbox field types respectively. Date fields, numeric fields, and free-text fields map directly with type preservation.

Talos multi-brand franchise reporting dashboards and saved report configurations are platform-specific and do not export cleanly. We do not migrate reporting configurations. We deliver a written inventory of every Talos report and dashboard with its filters, metrics, and visualisation type, plus the raw migrated data in a format compatible with Bullhorn Report Builder. The customer's Bullhorn admin or a reporting consultant rebuilds the reports post-migration using the migrated data.