Migrate from Sage People to Zoho Recruit

Sage People Candidate records migrate to Zoho Recruit Candidates. The core fields (name, email, phone, current title, current company) map directly. We resolve any custom Sage People Candidate fields by inventorying UD_ and UDF_ prefixed fields during discovery and mapping them to Zoho Recruit custom fields or the Candidate module's Additional Fields section. Candidate status from Sage People (New, In Review, Shortlisted, Interview, Offer, Hired, Rejected) maps to Zoho Recruit Candidate Status values.

Sage People Vacancy records map to Zoho Recruit Job Openings. Job title, job description, employment type (full-time, part-time, contract), and location transfer directly. Required qualifications, desired skills, and compensation bands stored as custom fields in Sage People migrate to Zoho Recruit Job Opening custom fields. Active or closed status maps to the Job Opening Active/Inactive flag.

Sage People Application records link Candidates to Vacancies and carry application-stage history. We migrate the application record with its current stage and the stage-change timestamp history preserved in Zoho Recruit's candidate activity feed. If Sage People stores interview scores or feedback as custom fields on the Application object, we map these to Zoho Recruit Interview Feedback forms.

Sage People Employee records flagged as hiring managers or recruiters map to Zoho Recruit Clients (for external hiring managers) or Zoho Recruit Users (for internal recruiters). We identify recruiter-role employees from Sage People's role-based object model and create corresponding Zoho Recruit user accounts with the matching email address. Hiring managers who are not Zoho Recruit users are created as Client records so they can access the Zoho Recruit Candidate Portal.

Sage People core HR Employee records do not map to Zoho Recruit because Zoho Recruit is an ATS, not an HRIS. Employee data (compensation, benefits, organizational hierarchy, leave balances) requires a separate migration to Zoho People if the customer needs to move core HR data. We flag this as a parallel engagement scope during discovery and do not attempt to map Employee records to Candidate records unless the customer explicitly wants pre-hire employee profiles migrated as candidate records.

Sage People leave and absence records are HRMS data that has no equivalent in Zoho Recruit's ATS model. If the customer is moving both recruitment and core HR to Zoho, we recommend a parallel Zoho People migration for absence data. If only recruitment moves, we do not migrate absence records and document this boundary in the migration scope.

Candidate documents (resumes, cover letters, certifications) stored as Salesforce attachments in Sage People export as binary blobs. We download document metadata and files in a batch queue before the URL expiration window, then upload them to Zoho Recruit's document library and attach them to the corresponding Candidate record. Resume parsing settings in Zoho Recruit (available on Professional and Enterprise) can re-parse uploaded resumes to populate structured candidate fields automatically.

Sage People Performance Management objectives and review records do not map to Zoho Recruit, which does not have a performance review module. If the customer uses Sage People Performance Management and needs to preserve review history, we recommend either a separate migration to Zoho People (which has a performance review module) or exporting review records as a CSV for manual reference. We document the review history schema during discovery for the customer's admin to handle separately.

Sage People Department records map to Zoho Recruit Departments for organizational structure. Cost center codes migrate as Department custom fields if the customer needs to track recruiting spend by department. Department hierarchies (parent-child relationships) are preserved by resolving the parent Department ID during Zoho Recruit import.

Sage People recruitment workflows (candidate approval, offer approval, vacancy publishing approval) are not API-exportable. We document every active workflow during discovery as a configuration inventory with its trigger conditions, approval routing, and action steps. The customer's Zoho Recruit admin rebuilds these as Blueprint workflows or Workflow Rules post-migration. This is the primary automation gap in this migration pair.

Sage People reports built on its Salesforce-backed reporting engine do not migrate to Zoho Recruit. We deliver a written report inventory with each report's filters, groupings, and chart types for the customer's admin to rebuild as Zoho Recruit standard or custom reports. Zoho Recruit's Professional and Enterprise tiers include Advanced Analytics with custom report builders and KPI dashboards that replicate most Sage People recruiting report types.

Sage People custom fields with UD_, UDF_, or IM_ prefixes are inventoried during discovery. We map field data types (text, number, date, picklist, checkbox) to Zoho Recruit field types and create the corresponding custom fields in Zoho Recruit before migration. Picklist values are mapped as explicit value lists. Non-prefixed custom fields are detected by comparing the live Sage People schema against the standard object reference and flagged for explicit review.