Migrate from Worknice to Zoho Recruit

Worknice People records map to Zoho Recruit Candidates. Worknice's role property (Employee, Contractor, Manager) maps to a custom Candidate field candidate_type__c as a picklist. The mandatory Last Name field in Zoho Recruit requires a pre-transform step: any Worknice Person record without a surname is flagged and set to 'not provided' per Zoho's import spec. First name, email, phone, and position title map to standard Candidate fields. We preserve the Worknice Person ID as an external reference in a custom field worknice_person_id__c for audit trail.

Worknice Positions define job titles and hierarchies. Position names migrate as Zoho Recruit Departments or as Job Opening titles depending on context. Active hiring positions become Job Openings linked to a Department; historical positions that are no longer open become reference data in the Department module. The position reporting hierarchy maps to a custom manager lookup field on the Candidate record where Zoho Recruit's native structure does not support org-chart depth.

Worknice leave entitlements (balance by type: annual, sick, personal) have no native equivalent in Zoho Recruit, which does not include a leave management module. We export leave type, current balance, and accrual method as structured fields and create a custom Zoho Recruit module named 'Leave Balances' with a Candidate lookup. We document the original accrual method in a long-text field so the customer's HR team can configure equivalent rules in their chosen HRMS post-migration. This migration does not replace a dedicated leave management system.

Worknice 360 reviews, customizable review forms, reviewer relationships, and completion status have partial mapping to Zoho Recruit's Assessments feature (Professional and Enterprise tiers). Custom form question responses migrate as a custom module 'Performance Reviews' with a Candidate lookup and free-text fields per question. Reviewer names migrate as custom User lookup fields. Review cycle dates migrate as start and end date fields. Customers on Zoho Recruit Standard without the Assessments module receive a custom module design during scoping.

Worknice company-level OKRs and employee goals with parent-child alignment have no direct Zoho Recruit equivalent, as Zoho Recruit is ATS-focused. We export goal titles, descriptions, progress percentages, and alignment hierarchies as structured metadata and create a custom module 'Goals and OKRs' with a Candidate lookup where applicable. The customer should plan to manage goal-setting separately or via Zoho Projects if cross-module visibility is required.

Worknice stores compliance documents, contracts, and onboarding paperwork per Person. We export document blobs and their attachment metadata (filename, file type, upload date, Person ID). Files are re-uploaded to the Zoho Recruit Document Library and linked via Candidate attachment relationships or a custom document module with Candidate lookup. File naming conventions from Worknice are preserved in the Zoho Recruit file name for traceability. We do not migrate Worknice's document version history as a structured record.

Worknice Bundles group templates (documents, onboarding tasks, review forms) assigned to positions or people. Bundle names and associated template types are exported as structured metadata and stored in a custom text field bundle_assignments__c on the relevant Person or Position record. Zoho Recruit does not have a bundle concept; the customer must rebuild onboarding task sequences as Zoho Recruit Workflow Rules or Blueprint process steps post-migration. We flag this in the migration handoff documentation.

Worknice assigns roles at the Person level (Employee, Manager, Contractor, Account owner). Role assignments migrate as a custom picklist field candidate_role__c on the Candidate record with values matching Worknice's role taxonomy. Where a Person has multiple roles (e.g., Employee and Manager), we create separate entries or flag for the customer's HR admin to resolve in Zoho Recruit's user management.

Worknice maps per-person integration connections to external ATS platforms, payroll providers, and timesheet tools via its Connections feature. These person-level integration IDs are specific to Worknice's integration broker and have no counterpart in Zoho Recruit. We exclude integration connections from the migration set and document the list of active connections in the migration inventory so the customer's admin can re-establish each integration in Zoho Recruit post-go-live.

Worknice Essential plan time entries (hours, dates, time category) migrate as Zoho Recruit Tasks linked to the Candidate record where the time entry relates to onboarding or interview activity. General timesheet data that is not tied to a hiring event is flagged as out-of-scope for the ATS migration and documented separately for the customer's HR admin.

Worknice engagement survey responses and continuous feedback records per Person export as structured rows. We create a custom module 'Engagement Feedback' in Zoho Recruit with a Candidate lookup and map response fields. Survey design and question structure require reconstruction in Zoho Recruit's Forms or a dedicated survey integration; we document the original survey question set in the migration inventory.

Worknice staff who have active logins and will use Zoho Recruit as a recruiter or hiring manager are exported as a Zoho Recruit User import. The migration order follows Zoho Recruit's recommended sequence: Users first, then Candidates, then Job Openings, then related records. Users who already have a separate Zoho Recruit account cannot be imported via the migration tool; they must close their existing account first per Zoho Recruit's import documentation.