Migrate from Talexio to Zoho Recruit

Talexio People profiles with an active recruitment status (applicant, candidate, in-pipeline) map to Zoho Recruit Candidates. The mapping uses Talexio's first_name, last_name, email_address, phone_number, and current_position fields, preserving the original candidate source (internal referral, job board, careers page) as a Zoho Recruit Candidate Source value. Note that Talexio's People profiles include both current employees and job applicants; only records flagged as recruitment candidates migrate to Candidates. Active employee profiles require a decision during scoping about whether they are imported as Candidates for future roles or omitted.

Talexio's ATS candidate records, application history, and pipeline stage assignments map to Zoho Recruit Candidates with associated Job Applications. Talexio pipeline stage names (applied, screening, interview, offer, hired, rejected) map to Zoho Recruit's Job Application status values, which are configurable per job opening. Talexio's candidate rating or score, if stored as a custom field, migrates as a Zoho Recruit custom Candidate field.

Talexio job postings map to Zoho Recruit Job Openings. We extract job title, department, location, employment type (full-time, part-time, contract), job description, and any custom fields. The Zoho Recruit Job Opening is the parent record for Candidate Applications; we create all Job Openings before migrating any Candidates to ensure the application-to-job relationship is satisfied at insert time.

Talexio organisational structure (departments and cost centres) exported as reference data maps to Zoho Recruit Departments. This is a configuration step—we pre-create the department hierarchy in Zoho Recruit before any candidate or job data is imported so that Job Openings can reference the correct department. Departments are a Zoho Recruit configuration object, not a migratable record with a separate history.

Talexio documents attached to candidate profiles (CVs, cover letters, portfolios) are exported from Talexio's reporting database and attached to the corresponding Zoho Recruit Candidate record via the Zoho Recruit Attachments API or CSV import with file references. The document filename and content type are preserved. Large document volumes (over 5 GB of attachments) may require chunked attachment migration separately from the CSV data import.

Talexio interview records (scheduled interviews, interviewer assignments, evaluation scores) map to Zoho Recruit Interviews. Interview dates, times, and interviewer names transfer to Zoho Recruit's Interview scheduling module. Evaluation ratings and interviewer feedback stored as Talexio custom fields migrate to Zoho Recruit custom Interview Assessment fields.

Talexio may hold client company records if the platform is used for staffing-agency-style recruitment. These map to Zoho Recruit Client and Contact records. The client name, primary contact, email, phone, and address fields migrate directly. Zoho Recruit's client portal feature (available from Professional tier) requires configuration post-migration if the customer plans to use it.

Talexio custom fields created on candidate profiles require enumeration during discovery. Each custom field is mapped to a Zoho Recruit custom field of matching type (text, picklist, number, date, checkbox, lookup). Zoho Recruit Standard edition allows up to 50 custom fields per module; Professional allows 300. If the customer's Talexio custom field count exceeds the destination tier limit, we flag this during scoping and the customer either upgrades the Zoho Recruit tier or consolidates fields.

Talexio Employment Positions (title, salary, effective dates, reporting line) have no direct Zoho Recruit equivalent because Zoho Recruit is an ATS without an HR core. We can preserve the most recent position title and employer as a Zoho Recruit Candidate custom text field for reference, but employment history and salary details do not map cleanly. This is documented in the handoff report and left to the customer's HR team to complete in Zoho People or their chosen HRMS post-migration.

Talexio leave entitlement and balance records (annual leave taken, sick leave, accrual history) do not migrate to Zoho Recruit. Zoho Recruit has no leave management module. We document the existence of these records and the leave year-end balances in a written handoff spreadsheet for the customer's HR team to enter into Zoho People or a standalone leave management tool. Leave data is not deleted from Talexio before contract expiry; the customer retains access until the subscription end date.

Talexio time and attendance clocking records (clock-in/out timestamps, overtime, timesheet approvals) have no Zoho Recruit equivalent. We do not migrate time clocking data to Zoho Recruit. Historical time logs can be exported from Talexio as a CSV and retained by the customer for payroll auditing purposes, but they are excluded from the Zoho Recruit migration scope. Time tracking should be configured in Zoho People or a dedicated time-tracking application post-migration.

Talexio onboarding package records (document sign-off status, onboarding step completion, new hire checklists) have no Zoho Recruit equivalent. Zoho Recruit's Employee Conversion feature marks a Candidate as hired and can trigger a Zoho People onboarding workflow, but Talexio's onboarding package data does not transfer. We deliver a written summary of the onboarding completion status per employee for the customer's HR team to enter manually into Zoho People or reconstruct as a Zoho Recruit custom module if the customer chooses to build one.