Migrate from SeamlessHR to Zoho Recruit

SeamlessHR's SeamlessHiring module stores candidate profiles as part of the recruitment workflow. We export candidate records including name, email, phone, application date, source, and any custom fields stored against the candidate profile. Zoho Recruit's Candidate object accepts these fields via CSV import with Last Name as a mandatory requirement — any SeamlessHR record without a Last Name value is flagged and populated with 'not provided' during the transform phase to prevent import rejection.

SeamlessHR Requisition records map to Zoho Recruit Job Opening. The requisition title becomes the Job Opening title, department assignment maps to Zoho Recruit's Department field, and the job description migrates as the Description field. Workflow stage names from SeamlessHR are mapped to Zoho Recruit's candidate stage pipeline. Custom fields on requisitions require pre-creation in Zoho Recruit at the Custom Field level before the import run; we retrieve the SeamlessHR custom field definition list during schema extraction and create matching fields in Zoho Recruit first.

SeamlessHR applications (candidate-to-requisition associations) map to the join between Zoho Recruit's Candidate record and Job Opening record. We preserve the application date, current stage, and stage history as a comment thread attached to the Candidate record in Zoho Recruit. Stage timestamps are preserved as Activity notes with a dated prefix.

Active SeamlessHR employee records do not map directly to Zoho Recruit's Candidate object because Zoho Recruit is an ATS for talent acquisition rather than an HRIS for current employees. We treat this as a configuration decision during scoping: the customer chooses whether to import current employees as Candidates (for organizations that recruit internally), as Contacts in Zoho Recruit's optional CRM module, or to exclude HRIS records and migrate only the recruitment module. Employee compensation, payroll, and benefits fields have no destination equivalent and are flagged as out-of-scope.

SeamlessHR's organizational hierarchy (reporting tree and department assignments) exports as a distinct object. We map department names and parent-child relationships to Zoho Recruit's Department module and hierarchy. Job requisitions reference the correct department during import so that the hiring manager assignment in Zoho Recruit reflects the SeamlessHR org structure.

SeamlessHR leave balances, entitlement policies, and request history have no equivalent in Zoho Recruit's ATS scope. We flag leave management as out-of-scope for this migration. If the customer requires leave tracking post-migration, Zoho People (a separate Zoho HRMS product) handles time-off management and can be migrated in a parallel engagement. We do not migrate pending leave requests unless specifically scoped; if requested, pending requests are exported as of the migration date and flagged as historical records.

Historical payslips and payroll runs in SeamlessHR are tied to employee records but live in the payroll module. Zoho Recruit does not have a payroll module. Compensation history must migrate separately to Zoho People or remain in SeamlessHR for audit purposes. We flag payroll as out-of-scope and deliver a written record of the payroll record count for the customer's HR team to handle in a separate migration.

SeamlessHR Core tier and above includes performance and potential management with review cycles, ratings, and goal data. Zoho Recruit has no performance management module. We flag performance data as out-of-scope and deliver the review history as a written inventory (record count, review period dates, rating distribution) for the customer to handle in a separate HRMS migration if needed.

SeamlessHR stores terminated employees on a separate export path from active employees. Exited employee records (exit dates, final compensation, attached documents) have no destination in Zoho Recruit as an ATS. We extract the exited employee record count and flag this as an out-of-scope item that the customer can handle in a separate Zoho People migration if the HRMS layer is also being moved.

SeamlessHR approval chains defining requisition sign-off routes and hiring manager escalation paths are configuration objects that do not migrate. We deliver a written inventory of every configured approval workflow including the approval chain, conditions, and delegation rules for the customer's admin to rebuild in Zoho Recruit's Assignment Rules and Workflow Alerts if needed.

SeamlessHR custom fields on requisitions require separate schema extraction before data export because no standardized import template exists. We retrieve the field definition list via SeamlessHR API first, construct the field mapping table, create matching custom fields in Zoho Recruit under Setup > Data Administration, then run the data import. Any custom field that exists in SeamlessHR but not pre-created in Zoho Recruit is skipped and listed in the post-migration gap report.

Candidate documents (CVs, cover letters, identification copies) attached to SeamlessHR profiles are exported as binary blobs and mapped to Zoho Recruit's attachment infrastructure. We extract document metadata (filename, file type, upload date, attached to which candidate) and upload the files during the candidate import phase. Files exceeding 25 MB are flagged for manual upload. Document versioning is not preserved if SeamlessHR stores version history as a separate attachment record.