Migrate from In-recruiting to Zoho Recruit

In-recruiting Candidates map directly to Zoho Recruit Candidates. The candidate's first name, last name, email, phone, current title, current company, location, and source tracking fields migrate as text fields. Last Name is mandatory in Zoho Recruit; we flag any In-recruiting candidate records missing last name and substitute 'Not Provided' during transform. Custom fields on the Candidate module require pre-creation in Zoho Recruit before import; we provision each custom field with the correct type (Text, Picklist, Checkbox, Multi-select) during the schema preparation phase. Multi-select fields from In-recruiting are converted to semicolon-delimited strings per Zoho's import specification.

In-recruiting Job postings map to Zoho Recruit Job Openings. The job title, department, location, employment type (full-time, part-time, contract), description, and requirements migrate as standard Job Opening fields. Job status (Active, On Hold, Closed) maps to Zoho's Job Opening status picklist. We preserve the original In-recruiting job ID as a custom field for reconciliation during cutover. Job board distribution settings (Indeed, LinkedIn, Glassdoor) do not migrate; these require manual reconfiguration in Zoho Recruit's Source Boosters or the respective job board connectors.

In-recruiting Applications map to Zoho Recruit's candidate-to-job association. The application date, current stage, source (referral, job board, career site), and rejection reason (if any) migrate. We resolve the parent Candidate and Job Opening references by matching on email (Candidate) and job title plus location (Job Opening). The In-recruiting stage name maps to a Zoho Recruit custom picklist or the standard candidate status values (New, Screening, Interview, Offer, Hired, Rejected). We preserve the full stage history from In-recruiting as a custom text field or JSON blob for audit.

In-recruiting's configurable pipeline stages (often customized per job or agency-wide) require mapping to Zoho Recruit's candidate status values. We extract the full stage list from In-recruiting during discovery, map each stage to either a Zoho Recruit standard status or a custom picklist value, and document the mapping in the migration spec. Stage probability percentages migrate as a custom number field on the Candidate or Job Application record if In-recruiting stores them.

In-recruiting interview records map to Zoho Recruit Interviews. The interview date, time, duration, interview type (phone, video, onsite), interviewer name, location or meeting link, and feedback score or notes migrate. Interviewer name resolves to a Zoho Recruit User record by email match. If In-recruiting stores interview notes as separate records, these map to the Zoho Interview's notes field or to a linked Note record.

In-recruiting Notes attached to Candidates, Jobs, or Applications map to Zoho Recruit Notes. The note body, created date, created by user, and parent record reference migrate. Notes are linked to the parent Candidate, Job Opening, or Job Application via Zoho's association model. We preserve the original created-by timestamp for audit and sequence notes in the Zoho timeline by that timestamp.

In-recruiting Tasks (follow-up items, to-dos, scheduling actions) map to Zoho Recruit Tasks. Task subject, description, due date, priority, status (Open, Completed), assigned owner, and related record reference migrate. Task type (call, email, meeting follow-up) maps to Zoho's Task category or a custom picklist. Owner resolution is by email match against Zoho Recruit Users.

In-recruiting Users (recruiters, hiring managers, admins) map to Zoho Recruit Users. We resolve by email address as the dedupe key. Note: Zoho Recruit cannot import Users who already have a separate Zoho Recruit account; those accounts must be closed before migration. We audit all In-recruiting users during discovery and flag any that may conflict. The customer's admin provisions any missing Zoho Recruit Users before the user import phase.

If In-recruiting includes a Client or Customer module (staffing agency context), these map to Zoho Recruit Clients. Client name, primary contact name, email, phone, address, and industry migrate. Zoho Recruit's Client module also links to Contacts as related records, so we create the Client record first then link any associated Contact records.

In-recruiting Contacts (hiring manager contacts at client companies) map to Zoho Recruit Contacts. First name, last name, email, phone, title, company, and address fields migrate. Contact is linked to the parent Client record via a lookup. If In-recruiting stores the contact as part of a Client record without a separate Contacts module, we split it into Zoho Client and Contact records during transform.

In-recruiting candidate attachments (resumes in PDF, DOCX, or RTF; cover letters; portfolio files) migrate as Zoho Recruit Resume records or document attachments on the Candidate record. We extract the file from In-recruiting's export or API response, map the file type, and attach it to the corresponding Zoho Candidate. Resume parsing in Zoho Recruit extracts structured fields (skills, experience, education) from the attached file post-import if the customer enables that feature on their plan.

In-recruiting custom fields (Candidate rating, availability date, visa status, salary expectation, screening score, etc.) require pre-creation in Zoho Recruit before any data import. We audit every custom field during discovery, document its type (Text, Number, Date, Checkbox, Picklist, Multi-select, Lookup), and provision the matching Zoho Recruit custom field in the target account during schema preparation. Zoho's Custom Field limits are 50 per module on Standard and 300 per module on Professional and Enterprise; we verify the In-recruiting custom field count fits within the customer's chosen Zoho tier.

In-recruiting tracks candidate source (referral, LinkedIn, Indeed, career site, agency, etc.) on each Application or Candidate record. This migrates to Zoho Recruit's Source picklist. If In-recruiting uses source categories that do not exist in Zoho's default list, we add them as custom Source values during the schema preparation phase. Source data is valuable for recruitment analytics and ROI reporting, so we ensure it migrates completely.

In-recruiting candidate ratings (numeric scores, star ratings, or tier classifications) migrate to a Zoho Recruit custom field of type Number or Picklist depending on the format. If In-recruiting uses a 1-5 star rating, we map to a 1-5 picklist in Zoho. Numeric scores migrate as Number fields. We preserve the original rating scale so that reporting continuity is maintained post-migration.