Migrate from Paycor to Zoho Recruit

Paycor Persons records filtered by applicant status map to Zoho Recruit Candidates. The Paycor Person record contains name, address, contact fields, and custom fields that map to Zoho Recruit's Candidate module. Zoho Recruit requires Last Name as a mandatory field on every Candidate import; Paycor Persons without a last name require a placeholder value of 'not provided' or similar before import. We extract standard and custom fields from Paycor's Persons endpoint, map them to Zoho Recruit's Candidate field schema, and flag any required picklist values that must be pre-created in Zoho Recruit before the import runs.

Paycor Employees (active workforce records with compensation, job history, and employment status) do not map to any Zoho Recruit module. Zoho Recruit is an ATS focused on the candidate lifecycle through offer acceptance. Post-hire employee records require Zoho People or another HR platform. We flag this scope gap during scoping and recommend either accepting manual entry of new hires into Zoho People post-migration or planning a separate Zoho People implementation if the customer's HR team manages the employee record lifecycle there.

Paycor Job Titles are position descriptors that attach to Employees. When migrating active job postings, we map the Paycor Job Title to the Job Opening Title in Zoho Recruit and preserve the Job Title as a custom field in the Job Opening if the customer's hiring process references Paycor's classification codes. Job Titles used in payroll rule filtering require documentation for the customer's admin to rebuild as Zoho Recruit workflow conditions.

Paycor Departments per Legal Entity map to Zoho Recruit's Department module, which Zoho Recruit uses to assign hiring managers and route approval workflows. We export Paycor's department codes and names, normalize the hierarchy (parent-child relationships flatten to flat records in Zoho Recruit), and import them as Zoho Recruit Departments before the Job Opening import so that the Department lookup is available at record creation.

Paycor Work Locations (geographic locations tied to Legal Entities for tax jurisdiction and compliance) map to Zoho Recruit's Job Opening Location field and related Address fields. We export the Work Location name and address components and map them to the corresponding Zoho Recruit fields. Multi-state or multi-country location hierarchies in Paycor that affect tax withholding rules do not map to Zoho Recruit, which does not handle payroll tax jurisdiction logic.

Paycor Legal Entities represent distinct business entities or subsidiaries and serve as the organizational hierarchy root for all subordinate objects (departments, work locations, time off plans). Zoho Recruit does not have a Legal Entity or multi-org concept; a single Zoho Recruit account represents one organization. For multi-subsidiary Paycor customers, we recommend either a single Zoho Recruit instance with a custom field identifying the subsidiary, or separate Zoho Recruit accounts per subsidiary (which adds user licensing cost). We document this architectural constraint during scoping.

Paycor Pay Groups (compensation grouping rules) and Labor Categories (job classification for costing) are payroll-specific constructs that affect GL journal entries and benefits eligibility. Zoho Recruit does not manage payroll, compensation, or benefits. We extract Pay Group and Labor Category codes and document them as a reference field for the customer's HR admin to cross-reference, but these do not import into Zoho Recruit's candidate or job modules.

Paycor Time Off Plans (accrual rules, carryover limits, plan types) and current PTO balances per Employee are HR and payroll operational data. Zoho Recruit does not manage time-off accruals, balance tracking, or scheduling. We do not migrate PTO data. Organizations needing PTO management post-Zoho Recruit should evaluate Zoho People as a separate implementation, which includes time-off tracking and integrates with Zoho Recruit for the candidate-to-employee conversion.

Historical payroll registers, pay stubs, tax filings, garnishment orders, and benefit deduction codes are the core operational records of Paycor and have no equivalent in Zoho Recruit. We do not migrate payroll data. Garnishment orders require continuous compliance management in a payroll platform; the customer's admin must maintain these in Paycor or transfer them to the payroll platform of choice if moving away from Paycor entirely.

Paycor HR documents (I-9s, W-4s, personnel policies) are stored separately from Employee records and are candidate or employee documents rather than recruiting-stage records. We can export these as attachments from Paycor and link them to the corresponding Zoho Recruit Candidate record via the Attachment module if the documents were collected during the recruitment phase. Post-hire documents (I-9 completion after hire) are better managed in Zoho People, which is a separate implementation scope.

Paycor users who will be recruiters, hiring managers, or administrators in Zoho Recruit require User provisioning in the Zoho Recruit account before candidate import begins. Zoho Recruit requires at least two users in the account before the CSV migration wizard runs; if only one user exists, a second user must be created manually. Users with pre-existing separate Zoho Recruit accounts cannot be imported into the organization's Zoho Recruit account; they must close their separate account first. We extract Paycor user email addresses and roles, validate against these Zoho Recruit requirements, and provision the user list in Zoho Recruit before the data migration phase.

Paycor stores candidate interaction history (interview schedules, recruiter notes, screening tasks) as part of the Persons record or linked through the recruiting workflow. We map interview records to Zoho Recruit Interviews, notes to Zoho Recruit Notes, and tasks and calls to the respective Zoho Recruit modules. Zoho Recruit's interview scheduling, feedback forms, and candidate rating features are standard functionality on Standard and above tiers. We validate that the Paycor engagement data exports in a format that maps cleanly to Zoho Recruit's module structure before migration.