Migrate from PeopleForce to Zoho Recruit

PeopleForce Employees contain both current staff and historical candidate records from PeopleRecruit. We split these during extraction: active employees who were hired through PeopleRecruit are mapped to Zoho Recruit Candidate records with current employment status stored in a custom field; employee records that represent current staff (with onboarding completed) are held for a separate Zoho People migration or documented for manual entry in Zoho Recruit. The split rule uses the PeopleForce hire_date, employment_status, and onboarding_stage fields to route each record correctly.

PeopleForce Vacancies and Positions map directly to Zoho Recruit Job Opening. We preserve the job title, department, employment type, and any vacancy description from PeopleForce as fields on the Job Opening. Publish status (Draft, Open, On Hold, Closed) maps to Zoho Recruit's Opening Status field. Active Vacancies with candidate pipelines migrate with their pipeline intact; closed vacancies migrate as historical records with a Closed status.

PeopleForce candidate records from PeopleRecruit map to Zoho Recruit Candidate. The candidate name, email, phone, source, and current application stage migrate directly. Custom candidate fields (skills assessments, interview ratings, sourced-from attributes) map to Zoho Recruit custom candidate fields created during schema setup. Source attribution from PeopleForce (LinkedIn, referral, job board) migrates to Zoho Recruit's Candidate Source field.

PeopleForce application records with pipeline stages map to Zoho Recruit's candidate stage history. Each stage transition (Applied, Screening, Interview, Offer, Hired, Rejected) migrates with its timestamp and assigning user. We preserve the stage history as Zoho Recruit Interview records with feedback, scorecards, and disposition notes where available. Stage names are mapped via a translation table during scoping to align PeopleForce stage labels with Zoho Recruit's standard pipeline stages.

PeopleForce profile photos, bio text, and skills stored on Employee and Candidate records map to Zoho Recruit Candidate profile fields. Profile photos migrate as attachments to the Candidate record. Skills migrate as multi-select picklist fields in Zoho Recruit. Bio text migrates to a long-text area on the Candidate profile. This mapping applies only to candidates who are also employees in PeopleForce; standalone candidate profiles without an employee record migrate as-is without an employee counterpart.

PeopleForce employee documents (employment contracts, ID copies, certifications) stored per employee record migrate as Zoho Recruit Attachments on the corresponding Candidate or Contact. We extract document metadata (filename, upload date, document type) from PeopleForce API and preserve the binary content where accessible. Document templates (reusable contract templates, offer letter templates) do not migrate; we document their existence and recommend Zoho Creator or DocuSign integration for template reconstruction.

Leave management is a PeopleForce HRMS feature that has no equivalent in Zoho Recruit's ATS model. We do not migrate Leave Policies, Leave Requests, or Leave Balances because Zoho Recruit does not have a Leave module. We document all active leave policies, accrual rules, and pending requests in a written inventory so the customer's admin can configure equivalent leave management in Zoho People or a separate leave platform post-migration.

Performance review cycles, review forms, submitted feedback, and scores stored in PeopleForce are HRMS-specific and have no equivalent receiving object in Zoho Recruit's ATS schema. We do not migrate Performance Reviews. We deliver a written inventory of all review cycles, configured forms, and scoring rubrics so the customer's admin can evaluate Zoho People or an alternative performance management tool for post-migration rebuild.

Recognition records in PeopleForce (Kudos given between employees with timestamps and messages) have no equivalent in Zoho Recruit's ATS schema. We do not migrate Kudos. We document the count of recognition records and note that if the customer moves to Zoho People, recognition can be rebuilt as part of a Zoho People engagement. This is informational only.

PeopleForce onboarding and offboarding task checklists (automated task templates generated at hire or departure) are HRMS-specific workflow constructs. Zoho Recruit's ATS model does not include an onboarding or offboarding module. We do not migrate checklist templates or task history. We document the checklist structure for each active onboarding and offboarding flow so the customer's admin can rebuild in Zoho People if that platform is adopted, or in Zoho Recruit's Blueprint automation for candidate-stage task triggers.

PeopleForce custom fields on Employee and Candidate objects are inventoried during discovery and mapped to Zoho Recruit custom fields of equivalent data type. Text fields map to Zoho Recruit single-line text; multi-select fields map to Zoho Recruit multi-select picklists; date fields map to Zoho Recruit date fields. We create the Zoho Recruit custom field schema before any data loads and apply type validation to ensure migrated values are compatible. Fields that have no Zoho Recruit equivalent (e.g., PeopleForce-specific dropdown values) are mapped to a text field with a lookup table applied during transform.

PeopleForce workflow rules built on the attribute-triggered automation engine (triggers tied to employee profile fields, hire dates, department changes, or onboarding stages) do not migrate as automation code. Zoho Recruit's Blueprint automation is a stage-based pipeline tool, not an attribute-triggered workflow engine, so a direct translation is not possible. We deliver a written workflow inventory document listing every active PeopleForce workflow with its trigger conditions, actions, and recommended Zoho Recruit Blueprint or Zoho Flow equivalent for the customer's admin to rebuild post-migration.