Migrate from Smart Recruit Online to Zoho Recruit

Smart Recruit Online Candidates map directly to Zoho Recruit Candidates. The primary mapping covers name, email, phone, location, and current status. Custom fields migrate via the fieldId/valueId/valueLabel structure extracted during the pre-migration audit, mapped to Zoho Recruit's equivalent custom field types (picklist, multi-select, text). Last Name is mandatory in Zoho Recruit — any Candidate without a last name receives a value of 'Not Provided' to prevent silent record skips during import. Candidate ID from Smart Recruit Online is preserved in a custom field src_candidate_id__c for audit and cross-reference.

Smart Recruit Online Job records map to Zoho Recruit Job records. The mapping covers title, department, function, location (including remote flag), typeOfEmployment, experienceLevel, and job description. Job reference numbers migrate to the Zoho Recruit Reference Number field. Each Job in Smart Recruit Online may have multiple Postings — these map to a single Job in Zoho Recruit with the posting name and board-specific URLs noted in a custom field for manual reposting.

Smart Recruit Online Application records link a Candidate to a Job with a current pipeline status. In Zoho Recruit, Applications live as records within the Candidates module linked to Jobs via the Job ID lookup. We map the application status history, application creation timestamp, and assigned Hirer to Zoho Recruit's corresponding fields. Status values from Smart Recruit Online are mapped to Zoho Recruit pipeline stages during the field mapping phase, and unmapped statuses are flagged before the migration run.

Smart Recruit Online Hirer records map to Zoho Recruit User accounts. Resolution is by email address — the Hirer's email in Smart Recruit Online must match a Zoho Recruit User's email for the assignment to resolve automatically. We extract all Hirers during scoping, match them against the destination User list, and place any unmatched Hirers in a reconciliation queue for the customer's admin to provision before the migration run proceeds.

Smart Recruit Online's configurable pipeline stages within Jobs map to Zoho Recruit's customizable hiring pipelines. We extract the current stage definitions — stage name, order, and stage-specific automations — during the pre-migration audit. Automations attached to stages are configuration objects and do not migrate as data; they are documented in the workflow inventory deliverable. Stage probability percentages map to Zoho Recruit's stage probability fields.

Smart Recruit Online Postings (linked to Jobs via jobAdId with board-specific distribution URLs) do not migrate as live board listings because distribution is a Smart Recruit Online-controlled action. We preserve the posting content, board name, released date, and URL in a custom field src_posting_board__c on the migrated Job record. The customer receives a job board reposting checklist as part of the migration handoff package for manual republishing in Zoho Recruit.

Smart Recruit Online CustomField objects (fieldId, fieldLabel, valueId, valueLabel) map to Zoho Recruit custom fields created in each module's Layout Editor. Picklist-style custom fields require value-label mapping against Zoho Recruit's picklist values during the migration run. Lookup fields in Smart Recruit Online map to Zoho Recruit Lookup fields pointing to the related module. Custom fields are not available in the Free Edition of Zoho Recruit — we confirm the destination edition includes the required custom field types before migration begins.

Smart Recruit Online workflow rules, approval chains, and stage-triggered actions live in the platform configuration layer and are not transferable as data records. We export the workflow definitions as documentation (trigger, conditions, actions, associated stages) and deliver a written automation inventory for the customer's admin to rebuild using Zoho Recruit's Workflow Rules interface (available from Professional tier). This is explicitly scoped as a configuration audit deliverable, not a data migration.

Candidate email threads accessible via the Smart Recruit Online candidate detail endpoint migrate to the Emails Related List in Zoho Recruit Candidates. Thread integrity depends on the email having been sent through Smart Recruit Online natively — external email imports may not be fully captured. Email attachments migrate as Zoho Recruit attachments linked to the Candidate record.

Resume files and attachments associated with Smart Recruit Online Candidates and Applications can be exported. File URLs in Smart Recruit Online reference Smart Recruit Online-controlled storage and are not portable — we export the files as binary blobs and re-host them as Zoho Recruit attachments linked to the corresponding Candidate record. File metadata (filename, upload date, file size) is preserved.

Department and function are structured fields on Smart Recruit Online Job objects with id and label. We migrate these as reference data, mapping to Zoho Recruit's Department module. If the customer's Zoho Recruit instance has a pre-configured Department list, we match by label; otherwise, we create the Departments during the migration run.

Offer management in Smart Recruit Online is available on higher tiers. We migrate offer records including offer status, details, and associated candidate and job references where exposed via API. Offer templates and approval workflows require manual setup in Zoho Recruit's Offer module post-migration. The Offer module availability depends on the Zoho Recruit edition selected.