Migrate from PeopleStrong to Zoho Recruit

PeopleStrong candidate records — including resume data, stage history, source attribution, and recruiter assignments — map to Zoho Recruit Candidates. We extract full candidate profiles via PeopleStrong's recruitment API, map source fields to Zoho Recruit's Source dropdown, and preserve candidate status as a custom field if the organization's stages differ from Zoho's default pipeline stages. Active candidate records without a last name in PeopleStrong require a 'not provided' placeholder because Zoho Recruit enforces Last Name as mandatory on Candidate import.

PeopleStrong job applications map to Zoho Recruit Job Applications, preserving the candidate-to-job-opening relationship and application submission date. Application stage history in PeopleStrong migrates as activity log entries or comments on the Zoho Recruit application record, since Zoho Recruit's native stage history differs in structure from PeopleStrong's timeline model.

PeopleStrong job requisitions map to Zoho Recruit Job Openings. We map job title, department, location, employment type, and job description fields directly. Salary range and budget information stored in PeopleStrong custom fields on the requisition map to Zoho Recruit custom fields if the customer's Enterprise plan supports them, or become structured notes for the recruiter to re-enter. Approval status on requisitions does not migrate; we note it in the handoff inventory.

PeopleStrong interview scorecards and evaluator ratings map to Zoho Recruit Interview records with Assessment ratings on the associated candidate. Interview feedback forms in PeopleStrong map to Zoho Recruit's Interview Feedback feature. If PeopleStrong stores interviewer assignments as separate user records, we resolve them by email match against Zoho Recruit user accounts during migration.

PeopleStrong offer letter records map to Zoho Recruit Offers. The offer status (accepted, rejected, pending) migrates as a custom picklist field or stage flag. Offer letter PDF attachments migrate as document attachments on the Zoho Recruit Candidate record via file-level API retrieval after the primary record import phase.

PeopleStrong organizational units — departments, cost centers, and locations — migrate as Zoho Recruit Departments before candidate and job opening import so that the Department lookup is satisfied at insert time. We preserve the full PeopleStrong location hierarchy as parent-child Department records. If PeopleStrong stores cost centers separately, those migrate as custom fields on the Department or as a separate custom lookup.

PeopleStrong user accounts with recruiter roles map to Zoho Recruit Users. We resolve by email match. Any PeopleStrong user without a matching Zoho Recruit user account enters a reconciliation queue; the customer's Zoho admin provisions the account before record import resumes. Active versus inactive status in PeopleStrong maps to Zoho Recruit user active flag. Note that PeopleStrong employees who are not system users do not get Zoho Recruit accounts in this migration scope.

Candidate resumes, cover letters, and portfolio files stored as attachments in PeopleStrong are retrieved via separate file-level API calls after the primary candidate record import. We batch file retrieval in groups of 50 to avoid timeout errors on candidates with multiple attachments. Attachments are uploaded to Zoho Recruit's Document Library and linked to the corresponding Candidate record via the CandidateID reference.

PeopleStrong organizations frequently add custom fields to candidate records — for example, background check status, internal candidate codes, or referral source details. These custom fields have inconsistent API exposure in PeopleStrong. We perform a schema discovery step during scoping to enumerate all active custom fields and their data types, then create matching custom fields in Zoho Recruit (up to 50 per module on Standard, 300 on Enterprise) before building the field mapping. Any custom fields exceeding Zoho Recruit's per-module limit become structured notes or a separate CSV sheet for manual review.

Payroll records — pay runs, salary components, deductions, and payslip metadata — do not map into Zoho Recruit's ATS data model. We extract payroll data as a structured CSV export with employee ID, pay period, gross salary, deductions, and net pay fields, and deliver it as a separate Zoho People import package with field mapping documentation. The customer's Zoho People administrator executes the HRMS import as a parallel workstream. We note that PeopleStrong payroll requires careful date-range scoping to avoid partial pay periods.

Attendance timestamps, regularization requests, leave balances, and leave request history stored in PeopleStrong do not map to Zoho Recruit objects. We export attendance and leave data as structured CSV files (employee ID, leave type, accrual, used, balance, request dates, approval status) and deliver a written Zoho People import guide with field mapping. Zoho People has a separate attendance module that the customer's HR admin configures after migration.

Performance review cycles, ratings, goals, and review templates in PeopleStrong's Performance Management module fall outside Zoho Recruit's schema. We deliver a written inventory of all review cycles with reviewer, reviewee, rating, and comments, formatted as a structured document for the customer's HR admin to re-enter manually or import into a separate Zoho People performance module if that is activated. Review template structures (configurable forms) do not migrate and require rebuild in the destination.