Migrate from Simplicant to Zoho Recruit

Simplicant User accounts (hiring managers, recruiters, interviewers) map to Zoho Recruit Users. We match by email address as the primary key. Active Simplicant Users with a Zoho account invite already sent are held in a reconciliation queue. Zoho requires at least two Users in the account before CSV import runs — we flag this during scoping if the source has fewer than two active users.

Simplicant Candidate records (contact details, application history, source attribution, stage history) map to Zoho Recruit Candidates. Zoho mandates a Last Name value on every Candidate import row; any Simplicant record without a last name is flagged in staging and assigned 'not provided' as a placeholder. Email address serves as the dedupe key. Application dates migrate as custom date fields since Zoho's standard Created Date reflects the import timestamp.

Simplicant Jobs (title, description, department, location, pipeline stage assignment) map to Zoho Recruit Job Openings. We map job status from Simplicant's stage to Zoho's Job Opening status field. The destination Zoho plan tier determines active job limits: Standard allows 10 per recruiter, Enterprise allows 20 per recruiter. Jobs above the plan ceiling are imported as Closed or archived and flagged for the admin to activate post-migration.

Simplicant Department records (organizational metadata on jobs and requisitions) map to Zoho Recruit Departments. Department names and IDs migrate as-is to maintain consistency when job metadata is rebuilt in Zoho. If the destination Zoho org already has Department records, we match by name and ID to avoid duplication.

Simplicant Location data attached to Jobs (defining where roles are based) migrates to Zoho Recruit Locations. Geographic metadata preserves to avoid re-entry. We map city, state, country fields to Zoho's corresponding address components.

Simplicant Interview Packets bundle structured evaluation forms for hiring teams. Form field names and scoring conventions vary by organization. We map the form schema and capture completed responses to Zoho's Interviews and Interview Feedback modules. The mapping type is configuration because Zoho's feedback form structure differs from Simplicant's configurable packet model; we preserve field labels and score values but note that the form builder interface will need re-creation.

Simplicant Offer records (salary, start date, terms, e-signature status) map to Zoho Recruit Offers. Salary figures and start dates migrate directly. E-signature audit trails are linked records in Simplicant and may not be extractable without API access; we flag any missing e-signature state as a manual verification item for the customer's admin post-migration.

Simplicant Hiring Pipelines define stage sequences per job type. Stage names, count, and automation rules vary between organizations. We map pipeline configurations to Zoho's visual pipeline stage model, creating stage entries in Zoho's Pipeline Settings that match the source stage sequence. Automation rules (auto-advance, rejection triggers) do not migrate; we document them in the automation inventory for the admin to rebuild in Zoho Workflows or Blueprint.

Simplicant structured screening scores and evaluation ratings (stored per candidate per stage) migrate to Zoho Recruit Assessments. Score ranges and weighting logic vary by organization and form; we export raw score data and map it to Zoho's Assessment record with a reference to the associated Candidate. Custom score normalization applies where Simplicant uses a non-standard scale.

Simplicant document management stores resumes, cover letters, and HR files in the cloud. File availability during export depends on whether the Careers Site API or bulk export is enabled on the source plan. We handle attachments separately from the main record import, uploading them to Zoho's Document Library and linking them to the associated Candidate or Job Opening record via ContentDocumentLink.

Simplicant organizations add custom fields to Jobs and Candidate profiles for industry-specific or process-specific data. Custom field definitions and data types are inferred from export results; we flag any fields without a direct Zoho equivalent as candidates for custom field creation in the destination. Custom field count limits by Zoho plan: Standard allows 50 per module, Enterprise allows 300 per module.

Simplicant Onboarding Records transition from offer acceptance into new hire setup tasks. Workflow step completion status and assigned task lists are preserved where available. Active onboarding automation sequences with branching logic may not be extractable without API access; we document the workflow structure in the automation inventory. Historical onboarding records (completed hires) migrate as task history against the Candidate record. Active onboarding workflows require manual reconfiguration in Zoho.