Migrate from UKG Ready to Zoho Recruit

UKG Ready Employee records map to Zoho Recruit Candidates when the organization uses UKG Ready Recruiting. The Employee's name fields map to Zoho Recruit's First Name and Last Name (Last Name is a mandatory field; any Employee without a Last Name in UKG Ready must be populated with 'not provided' or a similar placeholder or the record will be skipped during import). We extract the Employee's primary Cost Center as a custom Candidate field since Zoho Recruit does not have a native Cost Center concept. Active and inactive employment status in UKG Ready maps to Candidate status in Zoho Recruit using the candidate's current assignment record as the status source.

UKG Ready job positions and requisitions created in the Recruiting module map to Zoho Recruit Job Openings. The job title, department (Cost Center), employment type, and job description transfer to the corresponding Zoho Recruit Job Opening fields. Zoho Recruit distinguishes between Staffing Agency mode (with Clients and Contacts as separate modules) and Corporate HR mode (where hiring managers are internal); we confirm the edition during scoping and configure the Job Opening structure accordingly.

UKG Ready applications submitted against a job position map to Zoho Recruit Job Applications, which are the junction records linking Candidates to Job Openings. Application status (applied, screening, interview, offer, hired, rejected) maps to Zoho Recruit's pipeline stage values, and any assessment scores or interview ratings recorded in UKG Ready transfer as custom fields or notes in Zoho Recruit. We validate that the parent Job Opening exists in Zoho Recruit before importing applications to avoid orphan records.

UKG Ready HR Custom Fields on the Employee object map to Zoho Recruit custom Candidate fields. We support up to 10 custom fields as available via the UKG Put HR Custom Fields API. Field type mapping (text, date, picklist) must be validated during scoping because Zoho Recruit field types must match the incoming data format. We pre-create custom fields in Zoho Recruit before the candidate import phase using the Create New Field function in Setup > Data Administration > Data Migration.

UKG Ready Employee Assignments define how employees relate to Cost Centers and locations. We confirm during scoping which Cost Center field holds the primary department, as third-party integrations like Jirav specifically map to the third Cost Center field regardless of its label in UKG Ready. The selected Cost Center transfers as a custom text field on the Candidate record in Zoho Recruit. Multiple Cost Center assignments per employee are concatenated or stored as a multi-select custom field based on the customer's preference.

Interview records from UKG Ready Recruiting map to Zoho Recruit Interviews, with the candidate link resolved through the application mapping. Interview date, time, interviewer (mapped to Zoho Recruit User by email match), location or meeting link, and interview type transfer as Interview fields. Zoho Recruit's Staffing Agency edition includes client-facing interview scheduling; the Corporate HR edition handles internal interviews. We confirm the Zoho Recruit edition before designing the interview mapping.

Former employees in UKG Ready with previous application history map to archived or inactive Candidate records in Zoho Recruit depending on whether the recruiting history is relevant to future hiring. We flag inactive employee records during scoping and apply a status filter unless the customer requests full historical candidate transfer. Active recruiting pipeline candidates (current applicants, offers, recent hires) take migration priority; historical records beyond a defined lookback window are handled in a secondary migration batch.

UKG Ready Base Compensation records and Pay Statements do not migrate to Zoho Recruit because Zoho Recruit is an ATS without payroll or compensation management capabilities. We extract current compensation as a read-only custom field on the Candidate record if the customer requires it for offer-stage salary context, but all payroll, accrual, and pay statement data remains in UKG Ready. This is explicitly called out in the scoping document as outside ATS scope.

UKG Ready Time Entries and Time & Attendance records do not migrate to Zoho Recruit. Time tracking is outside Zoho Recruit's ATS scope. If the customer requires time and attendance tracking in the future, we recommend evaluating Zoho Books, Zoho People, or a dedicated time tracking tool as a separate integration. Time Entry data is flagged as out-of-scope during initial scoping.

UKG Ready Benefits Plan enrollment data does not migrate to Zoho Recruit. Benefit enrollment, carrier connections, and plan design are HR administration functions outside an ATS. We do not transfer benefits data. If the customer requires a benefits enrollment link within the candidate experience, Zoho Recruit's candidate portal supports custom forms that can be configured post-migration as a separate engagement.

UKG Ready Accrual Balances (PTO, leave, and other accrual types) do not migrate to Zoho Recruit. Accrual management is an HRMS function, not an ATS function. Organizations migrating from UKG Ready to Zoho Recruit for recruiting purposes typically retain UKG Ready (or migrate to a competing HCM) for payroll and HR administration. We scope accrual data as out-of-scope and document it in the migration scope agreement.

UKG Ready HR Action Request workflows, Performance Review workflows, Benefits workflows, and Time Approval workflows do not migrate to Zoho Recruit Workflow Rules. UKG workflow logic does not transfer 1:1 because Zoho Recruit Workflow Rules use a different condition-action model (conditions, instant actions, scheduled actions, custom functions). We deliver a written inventory of every active UKG Ready workflow with its trigger, conditions, actions, and a recommended Zoho Recruit Workflow Rule equivalent. The customer's admin rebuilds these in Zoho Recruit post-migration.