Migrate from Sesame HR to Zoho Recruit

Sesame HR stores candidates and their associated vacancies within one recruitment module. We split these into Zoho Recruit's two-object model: Job Opening records carry the vacancy details (department, job title, opening date, headcount), and Candidate records carry applicant information. Each Sesame HR candidate links to the corresponding vacancy, which becomes a Zoho Recruit Job Opening. If the customer has more than 5 open vacancies on Sesame HR Starter, we flag any vacancies not visible via API for manual extraction or plan upgrade before migration begins.

Sesame HR employees who were hired through the platform map to Zoho Recruit Candidate records with a Hired status. Employee fields (name, email, department, job title, hire date) map to Zoho Recruit's Candidate object fields. Active employment context from Sesame HR (department name, job title, manager) is stored in custom fields on the Candidate record since Zoho Recruit's standard Candidate object does not include a full employment history section.

Sesame HR department and job-title assignments on employees map to Zoho Recruit's Department lookup and Job Opening job-title fields. We extract the full department hierarchy during discovery and rebuild it as Zoho Recruit Departments. Job titles migrate as custom picklist values on the Job Opening object. Circular manager-subordinate references in the org chart are flagged during extraction and resolved before import.

Sesame HR exposes the org chart as a hierarchical structure. We extract it as a flat list of manager-subordinate relationships and rebuild the hierarchy in Zoho Recruit's Department object. Each department gets a Parent Department reference that maps to the Sesame HR manager field. We flag any employee whose manager record is inactive or missing in the source for reconciliation before import.

Sesame HR clock-in/clock-out records, overtime flags, and break deductions have no native equivalent in Zoho Recruit's ATS data model. We export time-entry data as a structured CSV organized by pay period and employee, preserving clock-in time, clock-out time, duration, overtime flags, and break deductions. The export schema is documented for the customer's payroll team to ingest into their downstream payroll system.

Leave balances and request history from Sesame HR (leave type, request date, status, approver, approved dates) are exported as dated records with a customer-approved leave-type mapping table. Zoho Recruit does not have a time-off management module by default; if the customer uses Zoho People alongside Zoho Recruit, we flag the integration path. Otherwise, absence records are delivered as a structured CSV reference document.

Shift assignments (employee, start time, end time, role, location) are exported as a structured schedule dataset. Zoho Recruit's ATS does not manage shift scheduling; this data is provided as a reference export for the customer's scheduling team to configure in their chosen time-and-attendance tool post-migration.

Sesame HR custom fields on Candidate and Employee records are read during discovery. We map picklist and multi-select values using a customer-approved value-mapping table. Custom fields are created in Zoho Recruit as custom fields on the relevant module (Candidate or Job Opening) with matching data types. The Enterprise tier allows 300 custom fields per module versus 50 on Professional; we confirm the target tier during scoping.

Employee documents from Sesame HR (contracts, ID copies, certificates) are extracted as binary files and attached to the corresponding Candidate record in Zoho Recruit via the Attachment API. File names and document types are preserved. We confirm the maximum attachment size supported by the customer's Zoho Recruit edition before import.

Sesame HR employee tags are extracted and mapped to a Zoho Recruit multi-select picklist field on the Candidate object. We deduplicate tags during transformation and apply the customer-approved value-mapping table for any tags that represent categorical data (department, role type, skill cluster). The customer selects the target field name during scoping.

Sesame HR contract reports, personal data history, and employment data history are exported as reference documents. These do not map to live Zoho Recruit objects because Zoho Recruit is an ATS, not an HRIS. We package them as named PDF and CSV exports attached to the migration delivery summary for the customer's records.

Sesame HR payroll input data (hours worked, overtime, deductions, accruals) is exported as a structured CSV with schema documentation. Zoho Recruit does not process payroll. The customer is responsible for ingesting this export into their downstream payroll system post-migration. We flag any payroll data fields that require customer-approved value mapping before export.