Migrate from Breathe to Zoho Recruit

Breathe Employee records map to Zoho Recruit Candidates in the first instance, with the option to convert to Contact (Corporate HR mode) once hired. We preserve name fields, contact details (email, phone), address, job title, department, employment start date, employment status, and salary band in typed Zoho Recruit fields. The Employee ID from Breathe is stored as a custom field for audit traceability. Custom fields on the Employee record (Professional tier and above) map to Zoho Recruit custom fields with type matching (text, picklist, date, number). Department structure from Breathe maps to Zoho Recruit's Departments module.

Breathe custom fields on the Employee record migrate to Zoho Recruit custom fields on the Candidate or Contact module. We extract field names and data types from the People Data Export, provision equivalent custom fields in Zoho Recruit via Setup > Customization > Modules before import, and map values during the CSV load. Multi-select picklist values from Breathe map to Zoho Recruit multi-select picklists; date fields map to date fields; numeric fields map to numeric fields. Note that custom fields are unavailable on Zoho Recruit's Free Edition; we recommend Standard tier ($25/recruiter/month) as the minimum for organisations with active custom field requirements.

Breathe's native Absence module (annual leave, sick leave, other leave types) has no direct Zoho Recruit equivalent. We handle this by creating a custom Absence History section on the Candidate or Contact record using custom fields for balance totals per leave type, and attaching structured Note records per absence entry with dates, type, and approval status. Leave entitlement settings migrate as typed custom fields. Balance carry-forward requires manual verification against the source export at the point of migration; we compute expected balances from entitlement settings and approval records rather than relying on pre-calculated fields alone.

Breathe sickness entries are a distinct record type linked to employees. We migrate sickness history as structured Note records attached to the Candidate or Contact, with key fields (sick dates, Fit Note reference where present, return-to-work date) captured in custom fields on the Note or as separate custom fields on the parent record. Fit Note attachments (PDFs) must be downloaded manually from Breathe's UI and re-uploaded to Zoho Recruit's Document Library post-import.

Breathe's performance review module (Professional tier and above) stores review cycles, ratings, and reviewer comments. We extract historical review records and map them to Zoho Recruit Notes attached to the Candidate or Contact, preserving review date, overall rating, and reviewer name. Custom rating scales from Breathe map to Zoho Recruit picklist values, with a mapping table documented during scoping. Review template definitions are configuration artefacts that do not migrate; we document the template structure for the customer's admin to rebuild in Zoho Recruit.

Breathe onboarding records track new-hire setup tasks, pending documents, and workflow step completion. We extract the task list and completion status as Zoho Recruit Tasks attached to the Candidate or Contact record, with task names and due dates preserved. Onboarding workflow definitions are configuration artefacts; we deliver a written inventory of active onboarding tasks and their completion status for the customer's admin to rebuild in Zoho Recruit's workflow rules or as a Task template.

Breathe's Remuneration Report (salary, additional payments, benefits, auto-enrolment) migrates to Zoho Recruit custom fields on the Candidate or Contact record. Salary fields map to currency fields, benefit flags map to checkbox fields, and auto-enrolment status maps to a picklist. We extract payroll data from Reports > Payroll exports and load it as structured rows during the main Employee migration phase. Note that Zoho Recruit does not have a native payroll module; payroll data is stored as reference fields rather than in a dedicated payroll object.

Breathe Company-level documents (policies, handbooks, templates) are stored in a separate section from Employee documents and cannot be bulk-exported via API. We flag this as a manual step requiring the customer to download documents from Breathe's Company > Company documents section before the migration date. Downloaded files are uploaded to Zoho Recruit's Document Library under the appropriate module post-import. We provide a guided checklist of document sections to visit.

Breathe Employee documents (contracts, certifications, ID documents) are stored per employee in the Profile > More > Documents section with no bulk export endpoint. We flag this as a manual archiving step at the scoping stage, provide a checklist of the UI sections to visit, and coordinate with the customer to complete downloads before migration. Individual files are attached to the corresponding Candidate or Contact record in Zoho Recruit post-import. This step is a common source of delay; we advise beginning document archiving four to six weeks before the planned migration date.

Breathe's organisational structure (departments and reporting lines) maps to Zoho Recruit's Departments module in Corporate HR mode. We extract the department hierarchy from the People Data Export and create matching Department records in Zoho Recruit before Employee migration begins, ensuring that the department lookup on each Candidate or Contact record can be resolved at insert time.

Breathe users who administer HR records map to Zoho Recruit User accounts. We resolve owners by email match. Any Breathe user without a matching Zoho Recruit User account is held in a reconciliation queue for the customer's admin to provision before Candidate and Contact import resumes. Inactive users are mapped to inactive Zoho Recruit User records to preserve assignment history.

Breathe Learn completion records (GDPR awareness, health and safety compliance training) are not supported by a direct Zoho Recruit equivalent. Zoho Recruit has no native learning management module. We document the completion status of each employee at migration time as a structured data deliverable (CSV), and the customer configures compliance tracking in Zoho Recruit custom fields or integrates a dedicated L&D platform post-migration. We do not migrate training content or course definitions as these are not data records.