Migrate from Sage HRMS to Zoho Recruit

Sage HRMS ATS candidate profiles (name, email, phone, resume file reference, application status, and source) map directly to Zoho Recruit Candidates. The Sage HRMS candidate record stores the candidate's application against a job requisition; we extract the candidate profile as the primary record and link it to the matching Zoho Recruit Job Opening by req ID during import. Sage HRMS exports candidate data as a flat CSV; we transform it to Zoho Recruit's Candidate module structure with First Name and Last Name as separate fields (Zoho Recruit requires Last Name).

Sage HRMS stores active job requisitions with title, department, position, employment type, and status. These map to Zoho Recruit Job Openings with Job Title, Department (mapped to Zoho Recruit's industry/department tag taxonomy), and Status. We preserve the Sage HRMS requisition number as a custom field in Zoho Recruit for cross-reference during the transition period.

Sage HRMS links each candidate profile to one or more job requisitions via application records that carry status (applied, screened, interviewed, offered, hired, rejected). We map these to Zoho Recruit's candidate Job Opening association (status) and create corresponding Interview records in Zoho Recruit for any Sage HRMS application status indicating an interview took place. Historical application status values that have no Zoho Recruit equivalent are preserved as candidate tags.

Sage HRMS organizational departments serve as cost centers for payroll allocation. Zoho Recruit does not have a native payroll cost-center model; instead, it uses Clients (external organizations) and tags for internal categorization. We map Sage HRMS Departments to Zoho Recruit Client records when the department represents an external employer, or to a department tag taxonomy we configure in Zoho Recruit's tag settings. If the customer uses Zoho People for HRMS, we map to Zoho People Departments instead and note the integration path.

Sage HRMS positions define job title, grade level, and pay range. Zoho Recruit Job Openings carry a position title and skill requirements but do not store pay grade or compensation bands natively. We map the position title to the Job Opening Title field and preserve the Sage HRMS pay range as a custom field on the Job Opening record. Grade level maps to a custom picklist field.

When a Sage HRMS candidate is marked as hired, the ATS module creates or links an Employee record. We export hired candidates with their offer details and map them to Zoho Recruit Candidate records with Hired status. If the customer also uses Zoho People, we note the candidate-to-employee conversion workflow via Zoho Recruit's native Zoho People integration rather than duplicating the employee record.

Sage HRMS stores candidate resumes and supporting documents as file attachments. We export these as a file bundle keyed by candidate ID, restructure them to Zoho Recruit's attachment format, and upload them to the corresponding Candidate record via the Zoho Recruit API or file upload endpoint. Large resume bundles (over 500 documents) are batched to avoid exceeding API credit limits on the destination tier.

Sage HRMS Pay Groups define pay frequency (weekly, biweekly, monthly), deduction priorities, and tax jurisdiction. Zoho Recruit does not have a native payroll model. We preserve Pay Group data as a custom field on the Job Opening or Client record so that the recruiting team has visibility into the compensation structure associated with each role. This is informational only; payroll processing remains in Sage HRMS or migrates to a separate payroll system.

Sage HRMS stores federal and state tax agency accounts, filing frequencies, and EINs for payroll tax compliance. Zoho Recruit is ATS-only and does not process payroll. We export the tax agency configuration as a reference document delivered alongside the migration and map the relevant tax jurisdiction to a custom field on Job Openings where pay-related tax context is relevant for candidate offers.

Sage HRMS organizations add custom fields to ATS module records (candidates, requisitions, applications). We inventory every custom field definition and data type, then create equivalent custom fields in Zoho Recruit using the Custom Field builder in Setup > Fields. Field types are mapped: Sage text becomes Zoho single-line text, Sage date becomes Zoho date, Sage picklist becomes Zoho picklist, and Sage numeric becomes Zoho number. ESS custom fields tied to core HRMS tables are out of scope for Zoho Recruit migration.

Sage HRMS user accounts and role-based permissions control access to ATS windows and reports. We extract user records (name, email, role) from Sage HRMS and map them to Zoho Recruit user accounts. The customer's Zoho Recruit admin provisions matching users before migration; we reconcile by email and flag any Sage HRMS users without a corresponding Zoho Recruit account for manual provisioning. Permissions do not migrate because Zoho Recruit has its own role and profile model.

Sage HRMS Employee Self Service configurations (ESS field visibility rules tied to custom database columns) have no equivalent in Zoho Recruit's ATS model. ESS is an HRMS feature for employees to view pay and request time off, not a recruitment feature. We document ESS field configurations in the migration handoff as out of scope. If the customer uses Zoho People for the HRMS layer post-migration, ESS configuration would be scoped under a separate Zoho People engagement.