Migrate from EPAY HCM to Zoho Recruit

EPAY's recruiting module Job Openings map directly to Zoho Recruit Job Openings. We preserve job title, job description, department assignment, location, employment type (full-time, part-time, contract), and hiring team. The EPAY job status (open, filled, cancelled) maps to Zoho Recruit's status field. If EPAY uses custom job classification fields, we create matching custom fields in Zoho Recruit during the schema setup phase. Note that EPAY job costing and labor allocation fields have no Zoho Recruit equivalent; these are flagged as unmapped and held in a reconciliation report for the customer's admin.

EPAY applicants map to Zoho Recruit Candidates. We preserve candidate name, email address, phone number, current employer, current job title, resume/CV attachment, source (Indeed, LinkedIn, referral, direct), and any rating or score from EPAY. The Last Name field is mandatory in Zoho Recruit; we flag any EPAY records missing a last name and set them to 'not provided' per Zoho's import requirements. If EPAY stores candidate skills as a multi-select field, we map to Zoho Recruit's Skills field or create a custom Skills picklist during setup.

EPAY application records (the association between a Candidate and a Job Opening) map to Zoho Recruit's candidate-job association within the Job Opening module. We preserve application date, current stage in the hiring pipeline (applied, screening, interview, offer, hired, rejected), and any custom stage values EPAY uses. EPAY offer letters and offer details are exported as attachments and linked to the candidate record in Zoho Recruit. Note that EPAY's onboarding module records (I-9, direct deposit, first-day tasks) have no Zoho Recruit equivalent; these remain in EPAY or migrate to a dedicated onboarding platform.

EPAY stores interview scheduling details and interviewer feedback within the recruiting module. We migrate interviewer name, interview date and time, interview type (phone, video, onsite), and free-text feedback notes to Zoho Recruit's Interview module. Zoho Recruit's interview scorecard fields are created as custom fields during setup to match EPAY's feedback structure if the customer uses structured scorecards. Rating values are mapped to Zoho Recruit's rating scale.

EPAY may store client or customer employer records for staffing and agency use cases. These map to Zoho Recruit's Client module. We preserve client company name, primary contact, address, industry classification, and any client-specific notes. If the customer uses EPAY's staffing billing module, invoice and placement records are flagged as unmapped because Zoho Recruit's Client module is for candidate-client association and does not handle billing or contract management.

EPAY's recruiting module stores candidate communication history — emails sent, calls logged, notes added. We migrate these as Zoho Recruit Tasks with the appropriate TaskSubtype (Call, Email) where available, and as Notes attached to the candidate record for general activity. The original activity timestamp is preserved in the Activity Date field. Bulk activity imports use Zoho Recruit's API or CSV import with date parsing to maintain chronological ordering. High-volume activity logs (over 50,000 records) may require chunked import with API rate-limit handling.

EPAY Employee records (personal info, employment history, job titles, departments, locations, hire dates, termination dates) have no equivalent in Zoho Recruit, which is an ATS and not an HRMS. We flag all Employee records as unmapped and hold them in a separate data export for the customer's admin to handle in their chosen HR platform. If the customer needs a combined ATS + HR platform, we recommend Zoho People as a companion product within the Zoho ecosystem; the Employee-to-Zoho People migration is a separate engagement scope.

EPAY payroll processing history, pay rates, salary histories, pay frequency, bonus records, and deduction codes have no Zoho Recruit equivalent. Zoho Recruit does not process payroll. We export payroll data as a CSV for the customer's records and recommend retaining EPAY access for payroll lookback purposes or migrating payroll to a dedicated platform (ADP, Paychex, Gusto, or Zoho Payroll if the customer standardizes on the Zoho ecosystem). Garnishment orders and active deduction codes are particularly sensitive and require manual verification in whatever payroll system is selected.

EPAY benefit plan assignments, coverage tiers, enrollment dates, and dependent information cannot migrate to Zoho Recruit. We export benefit enrollment records as supporting documentation in CSV format for the customer's admin to reference when setting up the new HR platform. Benefits carriers typically require employees to re-enroll directly in the carrier's system or the new HR platform's carrier integration regardless of data export quality.

EPAY time and attendance logs, accrual balances, scheduling rules, and overtime records have no Zoho Recruit equivalent. Zoho Recruit is an ATS and does not track time or manage schedules. We export time and attendance data as CSV for the customer's records. If the customer uses EPAY's job costing and labor allocation features, cost center and project code assignments are exported as a separate report for the customer's accounting or project management system.

EPAY performance review cycles, 360-degree feedback, journaling entries, review scores, course completions, and training certificates have no Zoho Recruit equivalent. We export these records as CSV for the customer's reference and recommend Zoho People or a dedicated performance management platform as the destination for this data.

EPAY ACA eligibility tracking, coverage offers, and compliance records have no Zoho Recruit equivalent. We export ACA measurement data as a CSV report for the customer's records and recommend the customer's chosen HR platform or a compliance consultant handle ACA tracking going forward.