Migrate from Talos ATS to Zoho Recruit

Talos ATS owner and recruiter assignments map to Zoho Recruit Users. Zoho Recruit requires Users to be imported first — before Candidates, Clients, and Job Openings — because OwnerId is a required lookup on most records. Import is limited to the first 2,000 user records; any excess requires a second import batch or manual provisioning. We match Talos users by email address against the Zoho Recruit user directory and flag any Talos user without a matching Zoho Recruit account for admin provisioning before the migration batch runs.

Talos ATS Candidates map 1:1 to Zoho Recruit Candidates, preserving contact details, CV/resume, application history, and stage progression timeline. Last Name is a mandatory field in Zoho Recruit — any Talos candidate record without a last name must be flagged and set to a placeholder value ('Not Provided') before import or the record is skipped. We preserve the Talos candidate ID in a custom field talos_candidate_id__c for audit traceability.

Talos ATS Job records (title, description, location, department, status) map to Zoho Recruit Job Openings. Active and closed jobs migrate with their posting URL mapped to the Zoho Recruit job record. Job status (open/closed/hired) maps to Zoho Recruit's status field. We flag any Talos job with a posting URL that may break post-migration if the Talos careers site is decommissioned simultaneously.

Talos ATS Application records link a Candidate to a Job and track stage progression. We migrate the association through Zoho Recruit's candidate-job association step, which occurs after both Candidates and Job Openings are loaded. The application stage history migrates as a linear timeline note attached to the candidate record because Zoho Recruit represents stage progression differently than Talos's explicit Application Stage object.

Talos ATS allows fully customisable stage names and counts per job or pipeline. Zoho Recruit uses a fixed-stage model with configurable labels within limits. We extract the customer's stage label set during the audit phase, consolidate duplicates, and remap to Zoho Recruit's stage structure. If a Talos pipeline exceeds Zoho Recruit's stage count limit, we flag the excess and work with the customer to merge or defer stages. Stage transition automation does not transfer — we document the original Talos stage triggers for manual rebuild in Zoho Recruit Blueprint.

Talos ATS Interview records (date, interviewer, type, outcome notes) map to Zoho Recruit Interview records. Video interview transcription from Talos is a custom Assessment feature and may not carry to Zoho Recruit in structured form — we migrate the outcome notes and scheduling details as structured fields and flag any transcription attachments that require manual re-upload. The import sequence places Interviews after Job Openings and candidate associations are resolved.

Free-text notes from Talos ATS migrate to Zoho Recruit Notes attached to the relevant Candidate, Client, or Job Opening record via ContentDocumentLink. Structured Assessment scoring rubrics require field-level mapping — we identify Talos custom Assessment fields during the audit and create equivalent custom fields in Zoho Recruit if the Professional or Enterprise tier is licensed. Free-form assessments without a structured schema migrate as Notes with the original score appended to the note body.

Talos ATS Offer records (compensation, start date, status) migrate to Zoho Recruit Job Opening offer details. We flag any Talos record where e-Sign status (Docusign integration) is present — these are add-on module records that may not export from the core Talos data package and require a separate data pull from the Docusign integration or manual documentation. Offer acceptance workflow state migrates as a custom status field.

Talos ATS custom fields on Jobs and Candidates are discovered during the audit phase. Zoho Recruit allows custom field creation during the import workflow via the 'Create New Field' button in field mapping. We pre-create Zoho Recruit custom fields matching Talos field types before migration to avoid import-time creation bottlenecks. Custom modules from Talos cannot be imported into Zoho Recruit — we flag these and recommend rebuilding the module structure in Zoho Recruit as a custom module (Professional tier and above) post-migration.

If the Talos ATS instance includes Client records (organisations as hiring clients separate from Candidate companies), they map to Zoho Recruit Clients in the staffing agency workflow. The import sequence places Clients after Candidates and before Job Openings. Client contact persons map to Zoho Recruit Contacts linked to the Client record.

Talos ATS sourcing campaigns or marketing campaign records map to Zoho Recruit Campaigns. Zoho Recruit's import sequence requires Campaigns to be loaded after Users and before Candidates, so that candidate source attribution can reference the campaign record during Candidate import. We map Talos campaign source tags to Zoho Recruit Campaign member status values.

Talos ATS saved reports and dashboard configurations are platform-specific and do not export cleanly. We deliver a written report inventory documenting every active Talos report's filters, groupings, and metrics. Zoho Recruit's report builder recreates these using the migrated raw data. The customer or a Zoho Recruit partner rebuilds the reports post-migration; this is out of standard migration scope.