Migrate from Scout Talent Software to Bullhorn ATS & CRM

Scout Talent Candidates map to Bullhorn Lead and Contact records based on hiring stage. Candidates with no associated Application or Talent Pool membership map to Bullhorn Lead. Candidates with an active Application, a Talent Pool membership, or a documented hiring stage of interview or beyond map to Bullhorn Contact. We preserve the Scout Talent candidate ID and any status tag as custom fields on both Lead and Contact for cross-reference and reconciliation.

Scout Talent Vacancies map to Bullhorn JobOrder as the primary job listing record. Bullhorn JobOrder carries the vacancy title, description, status, assigned hiring manager (mapped to Bullhorn User), and opening date. Vacancy pipeline stages map to Bullhorn Opportunity pipeline stages (a separate object linked to JobOrder via a custom field). We preserve the vacancy ID and stage name across both records so that the customer's admin can reconstruct the original pipeline view in Bullhorn.

Scout Talent Application records (Candidate applied to Vacancy) map directly to Bullhorn Application. The mapping includes application date, current stage, interview event references, and notes. Application-to-Candidate and Application-to-Vacancy lookups resolve by email match (Candidate) and job title match (Vacancy) during import. Interview booking records attached to applications are normalised from Scout Talent's known UTC-offset corruption before insert.

Scout Talent Entities are organisational segmentation layers that gate visibility to candidates, vacancies, and templates. Bullhorn has no native Entity equivalent; access is controlled via Team membership and User roles. We export the full entity hierarchy during scoping, then map entity assignments to Bullhorn Teams (created per Scout Talent Entity) and User Role permissions. Records hidden behind entity permissions in Scout Talent are only discoverable if the admin provides a cross-entity export; we flag this as a pre-migration access requirement.

Scout Talent Talent Pools are long-term candidate pipelines used for future roles. These map to Bullhorn Candidate records with a custom field pool_name__c carrying the original pool name and a status of passive or archived. We export the pool membership list and tagging data alongside the candidate record so that the customer's Bullhorn admin can recreate pools as Bullhorn Lists or through a tagging taxonomy.

Scout Talent vacancy-specific screening questions have no standard schema and include free-text, multiple-choice, numeric rating, and file-upload formats. We export each question with its answer format and all responses as structured key-value pairs. Bullhorn JobSubmission supports custom fields for additional applicant data. Vacancies with more than 15 screening questions require manual custom field pre-creation at Bullhorn before automated import can proceed; we provide the pre-creation field spec as part of the migration deliverable.

Scout Talent user records (name, email, role, entity permissions) map to Bullhorn User records. Role-based permission sets from Scout Talent map to Bullhorn role hierarchies and team assignments. Users without an active Bullhorn licence at migration time are imported as inactive Users with a custom field original_scout_id__c for reconciliation.

Scout Talent interview scheduling records include date, time, interviewer, and outcome notes. G2 reviews report that Scout Talent's Outlook calendar sync produces timezone corruption and offset errors on interview timestamps. We normalise all datetime values to UTC during extraction and flag records where the original timezone field is missing or flagged inconsistent, prompting the customer to verify critical interview dates post-migration. Bullhorn Event records carry StartDateTime, EndDateTime, and Location.

Email templates, form templates, and offer letter templates exist at both global and entity-scoped levels in Scout Talent. Bullhorn supports email templates and form templates within its CRM. We export template content and association metadata as structured files. Template re-creation is outside the automated migration scope; we deliver a template inventory document specifying the template name, type, content summary, and recommended Bullhorn replacement location (Bullhorn Email Tools, Salesforce Content, or a connected template tool).

Resume files, cover letters, assessment documents, and offer letters export as binary blobs and attach to the corresponding Candidate or Application record. We map each attachment to a Bullhorn ContentDocument record linked via ContentDocumentLink to the parent Candidate, Contact, Lead, or JobSubmission. File type and original filename are preserved in ContentVersion metadata.

Scout Talent status labels (contacted, interview booked, rejected, etc.) and tags are simple key-value taxonomy records. We export the full taxonomy and remap status names to Bullhorn's stage language. Tags that are used for candidate segmentation are mapped to custom multi-select picklist fields on the Candidate or Contact record. The customer selects the tag-to-picklist strategy during scoping.

Scout Talent stores branded careers portal content, job ad imagery, and email template assets. We export these as packaged file sets. Bullhorn's branding assets live in its CRM content management layer and the Bullhorn Careers Portal configuration. We flag which assets require re-upload, provide a file inventory with original location metadata, and deliver a re-upload guide specifying the target location in Bullhorn's portal settings. This is not an automated migration step.