Migrate from Paycom to Zoho Recruit

Paycom employee records with a new-hire status and eecode map to Zoho Recruit Candidate records. The four-character eecode becomes an external ID field (External Candidate ID) in Zoho Recruit for deduplication. First Name and Last Name are mapped directly; if Last Name is empty in Paycom, we insert 'Not Provided' as required by Zoho Recruit's import validation. Email, phone, address, and employment status fields map to their Zoho Recruit equivalents. Employee hire date and job title map to Candidate creation date and current position fields.

Existing Paycom employee records can map to Zoho Recruit Candidates if the customer's use case is internal mobility or redeployment tracking. For companies that want to keep a full employee directory separate from recruiting candidates, we create a Zoho Recruit custom module (Employee Directory) with the same field structure as the Candidate module, linked via the eecode external ID. Custom module availability requires Zoho Recruit Standard tier or above; Free tier does not support custom modules.

Paycom's Enhanced Background Checks store check status, completion date, and flags per candidate. We map these to Zoho Recruit Assessments (if the Enterprise plan is in use, which supports assessment workflows) or to a group of custom fields on the Candidate record (background_check_status, background_check_date, background_check_flags). The pre-hire background check order and result workflow is documented for rebuild in Zoho Recruit's Workflow Rules.

Paycom's get_new_hire_custom_fields endpoint exposes client-specific custom fields on new hire profiles, which can be type text, select, or date. We map each to a Zoho Recruit custom field of the equivalent type (Text, Picklist, or Date). Field limits apply: Zoho Recruit Standard allows 50 custom fields per module; Enterprise allows 300. If the Paycom custom field count exceeds the plan tier limit, we prioritize fields used in active hiring workflows and document the remainder for customer admin to enable post-migration.

If Paycom's hiring module includes active job postings, we map these to Zoho Recruit Job Opening records. Job title, job description, department, location, and employment type transfer directly. Paycom's requisition approval workflow is documented for rebuild in Zoho Recruit's Blueprint (Enterprise) or Workflow Rules (Standard/Professional). Job Opening limits apply per plan: Standard allows 10 active jobs/recruiter; Enterprise allows 20 active jobs/recruiter.

Paycom hiring module candidate application status and stage data maps to Zoho Recruit's candidate-job application relationship. Each application links a Candidate to a Job Opening with a stage value (Applied, Screening, Interview, Offer, Hired, Rejected). We map Paycom's stage values to Zoho Recruit's pipeline stages, with custom stage values created if the Paycom workflow has more stages than Zoho Recruit's default pipeline.

If Paycom stores interview scheduling data (interviewer name, date, time, interview type), we map these to Zoho Recruit Interview records linked to the Candidate and Job Opening. Interview feedback form responses from Paycom map to Zoho Recruit Interview Feedback Forms, which require Enterprise tier or the Interview Feedback Form add-on on Professional.

Hiring-related notes from Paycom employee and candidate records migrate as Zoho Recruit Note records linked to the Candidate. We preserve the note body, author (mapped via email to the Zoho Recruit User), and creation date. Non-hiring notes (payroll comments, benefits notes) are not migrated because they fall outside Zoho Recruit's scope.

Hiring-related tasks from Paycom (onboarding checklist items, pre-hire compliance tasks) migrate to Zoho Recruit Task records linked to the Candidate or Job Opening. Task status, priority, and due date transfer directly. Completed vs. open status is preserved. Automated task generation (e.g., reminders sent from Paycom's onboarding workflow) is documented for rebuild in Zoho Recruit Workflow Rules.

Timekeeping records are employee-owned in Paycom with clock-in/out timestamps, total hours, and overtime flags. Zoho Recruit does not have a timekeeping module, and this data has no equivalent in an ATS. We do not migrate timekeeping records. If the customer needs time and attendance tracking alongside Zoho Recruit, we recommend Zoho Cliq, Zoho Projects, or a dedicated time-tracking integration. The customer decides scope during discovery.

PTO accrual rules and balances are computed inside Paycom's rules engine and exposed as balance snapshots via the API. Zoho Recruit does not have an accrual engine. We do not migrate PTO balances. If the customer needs PTO tracking in the new system, Zoho Recruit's custom module can store a one-time balance snapshot as a static field, but ongoing accrual computation requires a separate HR system.

Payroll runs, gross/net pay amounts, tax withholdings, benefit deduction codes, and garnishment orders are HCM-specific objects with no equivalent in Zoho Recruit's ATS schema. We do not migrate this data. Garnishment calculation rules are opaque in Paycom (computed internally based on federal and state guidelines) and cannot be re-created externally; any deduction amounts would differ in a new payroll system. We document payroll-adjacent records that exist in Paycom for the customer's HR and payroll team to handle separately.