Migrate from Scout Talent Software to Zoho Recruit

Scout Talent Candidate records map to Zoho Recruit Candidate. We export profile fields, status tags, email, phone, address, current_company, current_title, and source attribution. Zoho Recruit requires Last Name as a mandatory field; any Scout Talent record without a surname is queued with 'not provided' substituted per Zoho's import requirement. Custom candidate properties from Scout Talent map to Zoho Recruit custom fields (created in Setup > Customization > Modules before import; Standard tier or above required). Historical status tags are remapped to Zoho Recruit picklist values. Attached resumes migrate as Candidate Attachments.

Scout Talent Vacancy records map to Zoho Recruit Job Opening. We preserve vacancy title, job description (rich text), status (Published/Unpublished/Closed mapped to Zoho status values), assigned hiring manager (resolved via User mapping), opening date, and closing date. Job location, employment type, and department fields map to equivalent Zoho Recruit fields. Vacancies with custom requisition fields map to Job Opening custom fields.

Each Scout Talent Application links a Candidate to a Vacancy at a point in time. We export application date, current workflow stage, interview event data, and notes attached to the application. Application status from Scout Talent's pipeline stage maps to Zoho Recruit's Candidate Status values. Multiple applications per candidate (re-applications) create separate Candidate Submissions in Zoho Recruit linked to the same candidate record.

Scout Talent's Entity model segments candidates, vacancies, and templates by organisational unit with permission gating. Zoho Recruit does not have an equivalent Entity model. We export the entity hierarchy and entity-to-record associations, then reconstruct access scoping in Zoho Recruit using Roles and Profiles. If entity-scoped visibility was enforced at the candidate level, we add Zoho Recruit custom fields (Entity_Name__c) to preserve the grouping for reporting, and the customer's admin configures sharing rules accordingly.

Scout Talent Talent Pools are long-term candidate pipelines and expression-of-interest records. We export pool names, associated candidate IDs, and tagging data. Each pooled candidate is imported as a Zoho Recruit Candidate with a custom field talent_pool__c carrying the pool name, and status set to Passive or Archived per the customer's preference. Tags from Scout Talent migrate to Zoho Recruit Tags. Multiple talent pool associations per candidate are stored as comma-separated values in the custom field.

Scout Talent screening questions are vacancy-specific with no standard schema, supporting free-text, multiple-choice, numeric rating, or file-upload responses. We export each question's text, answer format, and applicant responses per vacancy. In Zoho Recruit, we create equivalent custom fields on the Candidate module (for free-text and multiple-choice) or use the candidate scorecard feature (for scored numeric responses). Vacancies with 20+ screening questions may require manual custom field pre-creation in Zoho Recruit before automated import can proceed, which we document during scoping.

Scout Talent User records (name, email, role, entity permissions) export with role-based permission sets. We resolve users by email match against the Zoho Recruit destination account. Hiring Manager users (Scout Talent's unlimited no-cost tier) are provisioned in Zoho Recruit as Users with the relevant Zoho Recruit role. If a Scout Talent user has a separate existing Zoho Recruit account, Zoho requires that account to be closed before the user can be imported into the company Recruit account per Zoho's migration documentation.

Interview scheduling records from Scout Talent (date, time, interviewer, outcome notes) export with timezone normalisation to UTC. Scout Talent's interview booking feature carries known timezone corruption reported in G2 reviews; we normalise all datetime values to UTC during extraction and flag records where timezone data is missing or inconsistent, prompting the customer to verify critical event dates post-migration. Interview records map to Zoho Recruit Interview module with interviewer linked via User lookup and candidate via Candidate lookup.

Resume files, cover letters, assessment documents, and offer letters export as binary blobs from Scout Talent and map to Zoho Recruit's attachment model on the corresponding Candidate or Job Opening record. We map each attachment to the related candidate or vacancy using the source record ID preserved during export. File type and original filename are retained for reference.

Status labels (e.g., 'contacted', 'interview booked') and tags from Scout Talent export as simple key-value taxonomy records. The full taxonomy remaps to Zoho Recruit Tags with tag names preserved. Tags applied to candidates migrate as Zoho Recruit candidate Tags. The customer chooses whether to keep the full tag vocabulary or consolidate during scoping.

Email templates from Scout Talent (global and entity-scoped) export with content and association metadata. Zoho Recruit has a separate Email Template module. We export template content and deliver it as a written template inventory document specifying template name, associated vacancy/entity, body content, and merge field equivalents. The customer's admin recreates templates in Zoho Recruit's template editor. Template migration as code is outside scope.

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 Zoho Recruit's Branding or Career Page settings. The careers portal and employer branding configuration does not migrate automatically; we deliver an asset inventory with filenames, intended use, and destination section for the customer's admin to re-upload post-migration.