Migrate from SmartRecruiters to Zoho Recruit

SmartRecruiters Job Posting maps directly to Zoho Recruit Job Opening. The posting UUID from SmartRecruiters becomes the external ID field in Zoho Recruit for deduplication. We map title, location city/state/country, department (from the SmartRecruiters Department object), employment type (full-time, part-time, contract mapped to Zoho picklist values), and experience level. The SmartRecruiters posting date maps to Zoho Recruit's creation timestamp, and the status field (OPEN, CLOSED, DRAFT, CANCELLED) maps to Zoho's Job Opening status picklist. Job description and requirements migrate as the Description field.

SmartRecruiters Candidate maps 1:1 to Zoho Recruit Candidate. We concatenate firstName and lastName into the Full Name field, with email as the primary deduplication key. Zoho Recruit requires Last Name as a mandatory field; for candidates without a last name in SmartRecruiters we substitute 'Not Provided' per Zoho's documented import requirement. Phone, mobile, address, and social profile URLs migrate to standard Zoho fields. SmartRecruiters tags migrate as Zoho Recruit tags using the multi-record tag endpoint. Candidate history, source attribution, and consent decisions migrate to custom fields or notes.

SmartRecruiters Application records linking Candidate to Job Posting map to the Zoho Recruit Candidates subform under the Job Openings section. We resolve the SmartRecruiters Candidate UUID and Job Posting UUID to the corresponding Zoho Candidate ID and Job Opening ID before import. SmartRecruiters pipeline stage maps to a Zoho Recruit status picklist; we pre-create all SmartRecruiters stages as picklist values in Zoho before this mapping runs. Any screening answers from SmartRecruiters migrate as custom fields on the Zoho Candidate record. Note: SmartRecruiters Application API only accepts New status on insert; we handle the stage assignment in Zoho directly without a two-step workaround.

SmartRecruiters Users (recruiters, hiring managers, admins) map to Zoho Recruit Users by email match. Zoho Recruit enforces a hard constraint: a person cannot be imported as a User if they already hold a separate Zoho Recruit account under any organization. We run a pre-migration check against the destination Zoho Recruit org for every SmartRecruiters Owner; any collision requires the account to be closed before import proceeds. Active SmartRecruiters users map to active Zoho Users with role preserved; any user without a destination match goes to a reconciliation queue for the customer's admin to provision.

SmartRecruiters Department records map to Zoho Recruit Departments if the organization uses Zoho People. If Zoho People is not in scope, department data migrates as a custom picklist field on Job Opening and Candidate so that reporting by department remains available. We preserve the department hierarchy (parent and child department relationships) as a custom related-field structure in Zoho.

SmartRecruiters assigns hiring team members (recruiters, hiring managers, sourcers, coordinators) per job via user ID and role. We map these assignments to Zoho Recruit's assignee and collaborator fields on Job Opening records. The SmartRecruiters role labels (hiring_manager, recruiter, sourcer) map to Zoho's User field assignments with role notes preserved in a custom field. If a SmartRecruiters Hiring Team member has no Zoho User account, their assignment is logged in the inventory document for the customer's admin to provision before cutover.

SmartRecruiters Interview records (scheduling data, interviewer assignments, outcome notes) map to Zoho Recruit Interview records. We map interview date and time, interviewer name (resolved to Zoho User by email), interview type, and overall disposition. SmartRecruiters scorecard evaluation data migrates to Zoho Recruit Assessment records linked to the Interview; the schema difference (structured scorecard fields in SmartRecruiters vs freeform assessment criteria in Zoho) means we map the evaluator scores as Assessment criteria records and preserve evaluator comments as assessment notes. Interview status (SCHEDULED, COMPLETED, CANCELLED) maps to Zoho Interview status.

SmartRecruiters Offer records (compensation details, start date, offer status, candidate linkage) migrate as custom fields on the Zoho Recruit Candidate record or as a custom Offer module if the customer has Zoho Creator add-ons. Compensation structure (base salary, bonus, equity) migrates to currency custom fields; offer status (EXTENDED, ACCEPTED, DECLINED, WITHDRAWN) migrates to a picklist. The candidate linkage resolves via email match to the migrated Zoho Candidate record.

SmartRecruiters attachments (resumes, cover letters, portfolio files) stored against candidate profiles migrate as Zoho Recruit Candidate Attachments. We use Zoho Recruit's bulk file attachment endpoint to upload each file and associate it with the target Candidate record via ID resolution. Resume parsing results from SmartRecruiters migrate to Zoho Recruit's resume parser custom fields if the customer enables that feature in Zoho. File naming conventions from SmartRecruiters are preserved so that candidates' document history is auditable at the destination.

SmartRecruiters custom fields are organization-scoped and have no standard set; every organization defines its own fieldLabel and valueLabel pairs surfaced only at runtime. We run a mandatory pre-migration discovery pass using the SmartRecruiters /configuration endpoint to enumerate every active custom field, its data type (string, picklist, number, date, boolean), and permitted value list. We then pre-create equivalent custom fields in Zoho Recruit via Setup > Fields > Custom > Create New Field, matching data type and picklist values before any data import begins. Skipping this step leads to silent value loss when unmapped SmartRecruiters custom fields are dropped at Zoho import time. SmartRecruiters custom fields using multi-select or tag structures map to Zoho multi-select picklists or tags respectively.

SmartRecruiters Interview Scorecards (structured evaluation data per interviewer) do not map to a standalone Zoho Recruit object; we translate them into Zoho Recruit Assessment records linked to the corresponding Interview. Each SmartRecruiters scorecard criterion maps to an Assessment criterion in Zoho, with the evaluator's numeric score mapped to the criterion score field and free-text comments preserved in the notes. The overall recommendation (move forward, hold, reject) maps to a custom picklist field. This transformation is documented in the mapping spec for customer sign-off before production migration.

SmartRecruiters stores candidate consent decisions (email consent, data retention consent, GDPR flags) against the Candidate record. Zoho Recruit does not have a standard consent management module, so we migrate consent data to a set of custom fields on the Candidate record (consent_email__c, consent_data_retention__c, consent_gdpr__c) as boolean or date fields, or to candidate notes if the customer prefers an audit-log approach. This is a configuration decision made during scoping.