Migrate from Paylocity to Zoho Recruit

Paylocity candidate records map to Zoho Recruit Candidate. We split Paylocity's full-name field or reconcile separate first-name and last-name fields into Zoho Recruit's required Last Name field. Paylocity records without a last name are flagged and defaulted to 'Not Provided' per Zoho Recruit's import specification. Candidate status, source channel, and skill tags map to Zoho Recruit's Candidate Status, Source, and Tags fields. Email address and phone number migrate as Contact Info fields.

Paylocity job postings map directly to Zoho Recruit Job Opening. Job title, job description (rich text), department assignment, employment type (full-time, part-time, contract), and location migrate to Zoho Recruit's corresponding Job Opening fields. Paylocity's job status (open, paused, filled, closed) maps to Zoho Recruit's status picklist. Active job openings are imported first to establish lookup references for Candidate association.

Paylocity scheduled interviews map to Zoho Recruit Interview records. Interview date, time, duration, interviewer name, interview type (phone screen, video, onsite), and location or meeting link migrate. Interview scorecards and interviewer feedback notes from Paylocity map to Zoho Recruit's Assessment or Notes modules. We preserve the candidate-to-interview relationship via Zoho Recruit's candidate lookup on Interview records.

Paylocity assessment results and screening scores map to Zoho Recruit Assessment records. Assessment type, score, result (pass/fail/incomplete), and assessment date migrate. Where Paylocity stores third-party assessment provider results as attachments, we import them as Zoho Recruit attachments linked to the Candidate record.

Paylocity's employment data — hire date, department, job title, manager name, employment status — has no native Zoho Recruit object equivalent. We map these to Zoho Recruit Candidate custom fields created during migration scoping. The customer specifies which biographical fields are relevant for recruiting context (e.g., current employer, years of experience, department preference). Paylocity's composite Employee ID plus Company ID is preserved in a custom field for reference.

Paylocity allows custom fields in its recruiting module that may not exist in the HR module and vice versa. We query both module-specific Paylocity endpoints during discovery, collect the union of all candidate-related custom fields, and create equivalent Zoho Recruit custom fields. Field type casting is applied: Paylocity dropdown options map to Zoho Recruit Picklist values; multi-select options map to Multi-select Picklist. Custom fields are created before any Candidate import so that the schema is ready for data insertion.

Organizations using Paylocity's staffing agency module will have Client records representing external companies. These map to Zoho Recruit Client records in the Staffing Agency Edition. Client name, contact information, industry, and address data migrate directly. If the customer's Zoho Recruit account is on the Corporate HR edition (not Staffing Agency), Client records are imported as Organizations in the Candidates module or stored as custom module records.

Candidate notes and communication history from Paylocity's recruiting module migrate to Zoho Recruit Notes linked to the Candidate record. Communication logs (email threads, call summaries) are imported as Note records with the original timestamp preserved. Rich text formatting is maintained where Paylocity supports it; plain text is used for compatibility where Paylocity uses non-standard formatting.

Documents attached to Paylocity candidate records — resumes, certifications, offer letters — migrate as Zoho Recruit Candidate Attachments. File type, original filename, and attachment category are preserved in Zoho Recruit's attachment metadata. We import binary file blobs via Zoho Recruit's attachment API, maintaining the association to the correct Candidate record via candidate ID lookup.

Paylocity payroll records, pay runs, tax withholding elections, and compensation history have no schema equivalent in Zoho Recruit, which is an ATS and not an HRMS. These records are flagged as out of scope in the migration manifest. If the customer needs current salary or rate information for recruiting purposes, we extract the most recent compensation data point from Paylocity and map it to a Candidate custom field (e.g., Current Salary or Expected Salary). Benefits enrollments and deduction records are similarly out of scope.

Paylocity time-off accrual balances, carryover caps, and leave entitlement records have no ATS equivalent in Zoho Recruit and are out of migration scope. We document the existence of these records in the migration manifest with a note that they require a separate HRMS-level migration if needed. GetApp reviews document known Paylocity accrual calculation errors; we recommend the customer verify accrual accuracy in Paylocity before migration cutover for any records that will be needed post-migration.

Paylocity recruiting module users map to Zoho Recruit Users by email address match. We extract all distinct Paylocity users referenced on candidate, job opening, and interview records and match against Zoho Recruit's User table. Any Paylocity user without a matching Zoho Recruit User is held in the reconciliation queue for the customer's admin to provision. Zoho Recruit's user licensing model (Standard, Professional, Enterprise per-user tiers) determines which users require paid licenses, which we note in the scope document.