Migrate from Folks HR to Zoho Recruit

Folks HR Candidates with application status, resume uploads, interview scores, and hiring stage map directly to Zoho Recruit Candidate records. Application status values from Folks HR are mapped to Zoho Recruit Candidate status picklist (Active, Interview, Offer, Hired, Rejected). The full status transition history migrates as a custom multi-line text field or note attachment for audit. Resume files (stored as document attachments in Folks HR) are downloaded individually per the Folks HR API (no bulk download endpoint) and uploaded to Zoho Recruit's Candidate attachment model. We sequence file retrieval across multiple sessions to stay within the 60 req/min rate limit on the source.

Folks HR does not expose a formal Job Opening or requisition object; active job postings exist as part of the recruitment module but lack the structured requisition workflow (approval routing, hiring team assignment, interview schedule) that Zoho Recruit models explicitly. We extract active postings from Folks HR and create corresponding Zoho Recruit Job Opening records with title, department, location, employment type, and description. Job Opening status (Open, On Hold, Closed, Cancelled) is set based on the Folks HR posting active/inactive flag. The hiring manager assignment maps from the Folks HR recruiter owner to Zoho Recruit's Hiring Manager field.

Folks HR tracks which Candidates apply to which postings but the association structure is implicit in the application history. We reconstruct the Candidate-to-Job Opening linkage in Zoho Recruit by creating Job Application records that link each migrated Candidate to the corresponding Job Opening. Application date, current stage, and last activity date are preserved. This step is essential for staffing agencies where the same Candidate may apply to multiple Job Openings across clients.

Folks HR stores interview scores and reviewer feedback per Candidate. Zoho Recruit's Interview module captures interviewer, date, type, and feedback; score values migrate to custom fields on the Interview record. We create Zoho Recruit custom fields (if not already present) to capture each Folks HR rating dimension and map the values preserving the reviewer assignment. If Folks HR uses a 360-degree feedback model, we create multiple Interview records per Candidate per round.

Folks HR Departments map to Zoho Recruit Department values if Zoho People is co-deployed. If the migration scope is Zoho Recruit standalone without Zoho People integration, Departments are stored as a custom picklist field on the Job Opening and optionally on Candidate for segmentation. We configure the Department field during the Zoho Recruit schema setup phase before any candidate import.

Folks HR User accounts with role-based permissions (admin, manager, employee) are exported and matched to Zoho Recruit Users by email address. Recruiter and Hiring Manager roles from Folks HR map to Zoho Recruit's recruiter profile assignment. Any Folks HR user without a matching Zoho Recruit User is flagged in a reconciliation queue for the customer's admin to provision before candidate import resumes, because OwnerId references on Candidates and Job Openings must be satisfied at insert time.

Folks HR Employee records (current employees who are not candidates) do not map into Zoho Recruit's ATS object model. If the destination includes Zoho People, Employees migrate separately through the Zoho People migration module. We flag this as a parallel migration scope and note that the Folks HR employee export should be scoped separately from the recruitment export to avoid candidate record duplication when a former candidate becomes a hired Employee.

Folks HR custom fields defined on the Candidate object migrate as Zoho Recruit Candidate custom fields. Field type mapping is required during the configuration phase: Folks HR text fields map to Zoho Recruit single-line or multi-line text; dropdown fields map to picklist; date fields map to date. We extract the full custom field schema from Folks HR during scoping, pre-create the equivalent fields in Zoho Recruit, and document any field type changes for the customer to approve before the migration run.

Folks HR Leave Requests and accrual balances have no equivalent object in Zoho Recruit's ATS model. The leave balance calculation logic is server-side in Folks HR and not fully exposed via API, so we can only export current balance snapshots and request history. If the customer is also deploying Zoho People, leave data is a separate migration scope. If Zoho Recruit standalone, we document the gap and recommend the customer's HR admin manually configure leave types in Zoho People or accept the absence of leave tracking in the ATS.

Folks HR time tracking data (employee time entries by date, hours, and cost code) has no ATS equivalent in Zoho Recruit. This data is out of scope for a Folks HR to Zoho Recruit migration. If the customer's organization requires time tracking post-migration, we recommend evaluating Zoho People as a complementary HRMS layer or documenting the gap in the migration handoff checklist for the customer's HR leadership to address separately.

Folks HR performance review cycles, 360-degree feedback ratings, and review form history do not map into Zoho Recruit's ATS object model. Zoho Recruit is scoped to the talent acquisition lifecycle; performance management sits in Zoho People. We flag this as out-of-scope and recommend a separate Zoho People migration engagement if performance review history must be preserved. Review history is not lost—it remains accessible in Folks HR export files—but is not migrated into Zoho Recruit.

Folks HR expense reports with line items, receipts, amounts, and approval status are an HRMS feature with no ATS equivalent in Zoho Recruit. Receipts in Folks HR require individual-file download (no bulk export), compounding the 60 req/min rate limit challenge if a customer requests expense migration. We recommend routing expense report migration to a separate scope targeting Zoho Expense or Zoho Books if the customer uses the Zoho finance suite. If this is a requirement, we scope it independently during discovery.

Folks HR document attachments for Candidates—resumes, cover letters, offer letters, portfolio files—are stored individually per record and retrievable only by explicit file ID via API. For migrations involving hundreds of candidate documents, we iterate through the file list and download each file in sequence with throttling to respect the 60 req/min limit. We then upload each file to the corresponding Zoho Recruit Candidate record as a Candidate Attachment. Document filenames are preserved to maintain traceability. We recommend customers prioritize high-value document types (resumes and offer letters) first if document migration must be phased due to volume.