Migrate from Unicorn ATS to Zoho Recruit

Unicorn ATS candidate records (name, contact information, resume files, application date, source channel, and pipeline stage assignment) map directly to Zoho Recruit Candidate records. The Zoho Candidate API name is Candidates. Last Name is a mandatory field in Zoho Recruit; any source record with a blank Last Name receives a placeholder value ('not provided') before import or is flagged in a pre-migration reconciliation report for the customer to correct. Candidate email is the dedupe key for duplicate detection during import.

Unicorn ATS job requisitions (requisition title, department, location, employment type, posting dates, and associated hiring managers) map to Zoho Recruit Job Opening records. The Zoho JobOpening API name is JobOpenings. Job status (open, closed, on hold) maps to Zoho's Opening Status picklist. We preserve the original job posting date and closing date as custom date fields if they fall outside Zoho's standard job opening schema.

Unicorn ATS pipeline stages (custom stage names, order, and automation rules) map to Zoho Recruit Hiring Pipeline stages. Zoho supports multiple pipelines per job opening or per job type. We extract the full stage configuration from Unicorn ATS, document the stage names and probabilities, and create corresponding pipeline stages in Zoho Recruit before any candidate records are imported so that stage assignment on candidate records is valid at insert time.

Unicorn ATS employee records (start date, department, job title, manager assignment, employment status, compensation) may represent either active employees or historical hires who were tracked in the ATS. We map active employees to Zoho Recruit Contact records (if the organization uses Zoho Recruit in staffing mode with a client CRM layer) or to Candidate records (if the record represents a previous hire being stored for reference). The split is defined during scoping based on the customer's intended use of the employee data in Zoho Recruit.

Unicorn ATS interview records (scheduled date and time, interviewer assignments, interview type, scorecards, and outcome notes) map to Zoho Recruit Interview records. Interview records in Zoho Recruit have a master-detail relationship to the related Job Opening and Candidate. We resolve the candidate lookup and job opening lookup before inserting interview records to satisfy the relationship requirements.

Unicorn ATS offer records (compensation details, start date, offer status, and approval workflow history) map to Zoho Recruit Offers. Zoho Recruit's Offers module captures compensation, start date, offer status, and related candidate and job opening links. Approval routing logic is platform-specific; we export offer data as structured records and note that approval workflow rules require manual reconfiguration in Zoho Recruit Blueprint post-migration.

Unicorn ATS custom fields added to Candidates, Jobs, or Employee records require explicit field-level mapping. We export custom field definitions alongside their values, document any validation rules or picklist constraints, and create matching custom fields in Zoho Recruit using the Setup > Fields > Create New Field interface. Zoho supports field types including text, number, date, picklist, multi-select picklist, checkbox, and currency. Custom field type mapping is validated during scoping before migration begins.

Unicorn ATS activity logs and recruiter notes export as flat CSV without candidate record ID linkage. We run a fuzzy-match process on candidate name, email, and application date to reattach activity history to the correct Zoho Recruit Candidate record. Re-attached activities land as Zoho Recruit Activity records linked to the matched Candidate. Records that cannot be matched with high confidence are flagged in a pre-migration report for the customer to review and resolve manually before final import.

Unicorn ATS resume files attached to candidate profiles migrate as Zoho Recruit attachments on the corresponding Candidate record. Zoho Recruit supports attachments up to 20 MB per file via the add_attachment_to_application API endpoint. We extract resume files from the source export, associate them with the correct candidate record using the fuzzy-matched candidate ID, and upload them as candidate attachments during the candidate import phase.

Candidate source channel information (job board, referral, direct, career site) from Unicorn ATS maps to the Zoho Recruit Source picklist on the Candidate record. If the source value in Unicorn ATS does not match an existing Zoho Recruit source option, we create a new source entry in Zoho Recruit Setup > Recruiting > Sources before candidate import to prevent picklist validation errors.

Unicorn ATS recruiter owners map to Zoho Recruit User records by email match. We extract every distinct owner referenced on candidate, job, and engagement records and match by email against the Zoho Recruit destination User table. Any owner without a matching Zoho Recruit User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Note: users who already have a separate Zoho Recruit account cannot be migrated into the company's Recruit account and must close their separate account first per Zoho documentation.

Unicorn ATS records tracking when a candidate is submitted to a job requisition map to Zoho Recruit Submission records. Submissions link the Candidate and Job Opening with submission date, submission status (active, shortlisted, rejected, hired), and client organization. We resolve both the Candidate and Job Opening references before inserting Submission records to satisfy the lookup dependencies.