Migrate your Scout Talent Software data

Candidates are the core record in :Recruit. We export profile fields, application history, status tags, screening responses, and attached documents. Custom candidate properties and screening question answers require field-level mapping against the destination schema.

Vacancies are job listings linked to pipelines, stages, and assigned users. We preserve the vacancy title, description, status, assigned hiring manager, and opening date. Pipeline stage definitions and vacancy-to-entity assignments must be manually mapped at the destination.

Applications link a Candidate to a Vacancy at a specific point in time. We export application date, stage in the workflow, interview event data, and notes. Where interview booking records exist, we flag timezone discrepancies noted in G2 reviews and normalise to UTC before import.

Entities are Scout Talent's organisational segmentation layer — user-created categories that gate access to candidates, templates, and vacancies. We export the entity hierarchy and map entity assignments to equivalent team, department, or org-unit structures at the destination ATS.

Scout Talent supports long-term talent pipelines and expression-of-interest records. We export pool names, associated candidates, and tagging data. These land as archived or passive candidates in the destination, preserving source pool membership as a custom tag.

Custom screening questions are attached to vacancies and capture structured applicant responses. We export question text, answer format, and scored responses. These map to custom application fields or scorecards at the destination.

User records with name, email, role, and entity permissions are exported. Role-based permission sets are mapped to equivalent access levels in the target platform. User accounts that no longer exist are flagged for deactivation.

Email templates, form templates, and offer letter templates exist at both global and entity-scoped levels. We export template content and association metadata. Template re-creation at the destination requires content formatting review.

Interview scheduling records, including date, time, interviewer, and outcome notes, are exported. We handle timezone normalisation from UTC storage. Outlook calendar integration issues reported in G2 reviews mean we treat booking-source data as unreliable and re-import from event records only.

Resume files, cover letters, assessment documents, and offer letters are exported as binary blobs. We map each attachment to the corresponding candidate or application record at the destination and preserve original filenames and MIME types.

Scout Talent stores branded careers portal content, job ad imagery, and email template assets. We export these as packaged file sets and flag which assets require re-upload to the destination's branding settings.

Status labels (e.g., 'contacted', 'interview booked') and tags are simple key-value taxonomy records. We export the full taxonomy and remap status names to match the destination's stage language. Tag count per candidate is preserved as metadata.