Migrate from Scout Talent Software to Recruit CRM & ATS

Scout Talent Candidate records map to Recruit CRM Candidates with name, email, phone, address, work experience, education, skills, and source preserved. Custom candidate properties migrate as custom fields on the Recruit CRM Candidate record. We resolve the entity-to-organisation relationship during scoping so that candidates associated with multiple Scout Talent entities are not orphaned at the destination. Active candidate status maps directly; inactive and archived candidates from talent pools migrate with a passive or archived status label for the customer to confirm.

Scout Talent Vacancies map to Recruit CRM Jobs. Vacancy title, description, status (Published, Unpublished, Closed), assigned hiring manager, and opening date migrate directly. The Scout Talent job state (Published for active applications, Unpublished to render the page invalid, Closed for filled or withdrawn roles) maps to Recruit CRM's job status field. We preserve the original vacancy ID as a custom field for audit trails.

Scout Talent Applications link a Candidate to a Vacancy and carry application date, current stage, and associated notes. We map applications to Recruit CRM Applications using the Candidate-to-Candidate and Job-to-Job lookups resolved at migration time. Interview event data attached to applications migrates as Interview records in Recruit CRM linked to the Application. Where Scout Talent stores interview outcome notes, these migrate as notes attached to the Interview.

Scout Talent Entities are permission-gated organisational units that segment candidates, vacancies, and templates by team or business unit. Recruit CRM does not have an equivalent entity model. We export the full entity hierarchy and either map entity assignments to Recruit CRM Teams or use tagging to preserve the organisational context. If the customer uses entities purely for access control rather than reporting, we flag the tagging strategy for confirmation during scoping.

Scout Talent Talent Pools are long-term candidate pipelines for expression-of-interest and future roles. We export pool names, associated candidates, and tagging data. These land as Recruit CRM Candidates with a passive or talent-pool tag and the original pool name preserved as a custom field. The customer assigns these candidates to future roles using Recruit CRM's search and pipeline tools.

Screening questions are vacancy-specific in Scout Talent and support free-text, multiple-choice, numeric rating, and file-upload response formats. There is no standard schema across vacancies. We export each question with its answer format and all applicant responses, then map them to Recruit CRM custom fields on the Application record. Vacancies with more than 15 screening questions may require the customer to create custom fields in Recruit CRM before automated import can proceed; we flag these in the pre-migration field audit.

Scout Talent User records with name, email, role, and entity permissions export directly. Role-based permission sets map to Recruit CRM access levels. Scout Talent offers unlimited Hiring Manager users at no additional cost; Recruit CRM includes team members as standard users with role-based permissions. Users without a matching email in Recruit CRM go to a reconciliation queue for the customer to provision before record import.

Interview scheduling records from Scout Talent, including date, time, interviewer, and outcome notes, migrate to Recruit CRM Interviews linked to the Application. We normalise all datetime values to UTC during extraction to account for Scout Talent's documented timezone corruption in Outlook calendar sync. We flag records where timezone data is missing or inconsistent, prompting the customer to verify critical interview dates post-migration. Interview outcome notes migrate as interview feedback notes in Recruit CRM.

Resume files, cover letters, assessment documents, and offer letters export as binary blobs from Scout Talent. We map each attachment to the corresponding Recruit CRM Candidate or Application record and preserve the original filename and MIME type. The customer re-uploads attachments that cannot be parsed during import, or we use Recruit CRM's document attachment endpoint where the file format is supported.

Status labels such as Contacted, Interview Booked, Shortlisted, and Rejected, along with custom tags used for candidate segmentation, migrate as Tags in Recruit CRM. The full taxonomy of status and tag values exports from Scout Talent and is remapped to match the destination's labelling convention. We preserve a mapping table between the Scout Talent status names and their Recruit CRM equivalents for the customer's reference.

Email templates, form templates, and offer letter templates exist at both global and entity-scoped levels in Scout Talent. We export template content and association metadata as a written inventory with field-by-field mapping. Recruit CRM has its own template builder. We do not recreate templates as code; the inventory document provides the customer with a template-by-template reference list to rebuild in Recruit CRM.

Scout Talent stores branded careers portal content, job ad imagery, and email template assets. We export these as a packaged file set with the original asset metadata. We flag which assets require re-upload to Recruit CRM's branding centre or careers portal builder and provide a filename-to-destination mapping guide. Image assets and branded CSS that cannot be imported programmatically are marked for manual re-upload.