Migrate from Darwinbox to Zoho Recruit

Darwinbox Employee records map to Zoho Recruit Candidates. The Darwinbox employee ID becomes a custom field darwinbox_employee_id__c on the Candidate record to preserve the source reference. Name, email, phone, and current employment status map directly. Current job title and department pull from the Darwinbox employee record and map to Zoho Recruit's Candidate fields. Employees who originated from a Darwinbox recruitment requisition will have a darwinbox_requisition_id__c custom field linking back to the Job Opening.

Darwinbox candidate profiles generated during the Darwinbox recruitment workflow map directly to Zoho Recruit Candidates. The Darwinbox applicant-stage history (applied, screened, interview, offer, hired) maps to Zoho Recruit's Candidate Status picklist values, with each stage recorded as an Interview or Activity record. Candidate source, rating, and notes migrate as Zoho Recruit Candidate custom fields.

Darwinbox job postings and requisitions map to Zoho Recruit Job Openings. The Darwinbox job title, department, location, employment type, and job description map to the corresponding Zoho Recruit fields. Active versus closed status on the Darwinbox requisition determines the Job Opening status in Zoho Recruit. Position count from Darwinbox maps to Zoho Recruit's Number of Positions field.

Darwinbox organisational units and department structure map to Zoho Recruit Departments. We preserve the Darwinbox hierarchy by mapping the parent department reference to Zoho Recruit's Department hierarchy where supported. Cost centre assignments and location data from Darwinbox store as custom fields on the Department record. If the organisation uses Darwinbox's multi-location setup, each location becomes a separate Zoho Recruit Department or a custom Location field.

Zoho Recruit does not have a native leave management module. Leave entitlements, accrual balances, and leave history from Darwinbox must be handled as a parallel system decision: either stored as custom fields on the Candidate or Employee record in Zoho Recruit (limited by the 50-300 custom field cap per module), or managed in a separate Zoho People instance integrated via Zoho Flow. We document the Darwinbox leave types and balances in a structured CSV and provide a Zoho People onboarding checklist as part of the out-of-scope handoff.

Zoho Recruit has no attendance or time-tracking module. Attendance punch data from Darwinbox (timestamps, shift references, in/out status codes) has no native Zoho Recruit equivalent. If the customer requires attendance tracking post-migration, we recommend a separate Zoho People instance for time and attendance or an integration via Zoho Flow. We export the Darwinbox attendance data as a structured CSV with employee ID and punch timestamp for the customer's HR admin to configure in their chosen tool.

Darwinbox stores effective-dated compensation rows per employee (salary components, deductions, tax codes). Zoho Recruit has no native payroll or compensation module. Current salary and notice period details can be stored as custom fields on the Candidate record if required for recruitment decision-making, but historical compensation rows cannot be meaningfully represented in Zoho Recruit's schema. We extract the most recent compensation snapshot and flag the full payroll history as out-of-scope for manual handling.

Darwinbox performance review cycles, ratings, goals, and manager feedback have no equivalent in Zoho Recruit's ATS model. Review records and ratings cannot be stored as custom fields because a single review cycle generates multiple rows per employee with complex date dependencies. We export performance data as a structured CSV and flag it as out-of-scope for the customer's HR admin to handle in a dedicated performance management tool.

Darwinbox engagement events (peer awards, reward points, recognition timestamps) map to Zoho Recruit Activity records and Notes attached to the Candidate. Recognition type, point value, and awarding manager migrate as custom fields on the Activity record. The engagement timestamp preserves as the Activity date. This mapping captures the existence of engagement records but does not replicate any gamification or rewards-redemption functionality.

Darwinbox tenant-specific custom fields must be introspected during the discovery phase since they are not documented in the public API reference. Each Darwinbox custom field is mapped to a Zoho Recruit custom field on the corresponding module (Candidate, Job Opening, or Department). Zoho Recruit's custom field limits (50 per module on Standard, 300 on Enterprise) apply. Fields exceeding the cap are flagged in the mapping document for the customer's admin to resolve before migration day.

Darwinbox user accounts with roles (admin, manager, employee) map to Zoho Recruit User profiles. The mapping preserves the user's name, email, and functional role as a Zoho Recruit recruiter profile. Active versus inactive status is resolved against the Darwinbox user status. Only users with recruiter or admin function in Darwinbox map to Zoho Recruit Users; employees with no recruitment responsibility are not provisioned as Zoho Recruit Users.

Darwinbox document blobs (contracts, IDs, certifications) are stored in a document management module that is not accessible via the Darwinbox public REST API. Zoho Recruit supports file attachments per record but cannot ingest the Darwinbox blob storage directly. We flag document migration as an out-of-scope step requiring manual handling. Customers must either export documents from Darwinbox manually or coordinate a vendor-assisted export, then upload them to the relevant Zoho Recruit Candidate record post-migration.