Migrate from WebHR to Zoho Recruit

WebHR's Recruitment Candidate records map to Zoho Recruit's Candidate module. The mapping includes first name, last name (required in Zoho Recruit; we substitute 'Not Provided' for blank values), email, phone, current company, current job title, application date, and source. If WebHR's Recruitment module was not active (a paid add-on at $0.50/employee/month), candidate records do not exist in the source API despite the customer's expectation. We verify module activation before scoping commits to candidate data completeness.

WebHR pipeline stages (Screening, Technical Interview, Culture Fit, Offer) are customer-defined with no canonical schema. We extract the actual stage names and order during the discovery phase, then configure Zoho Recruit's Job Opening stages to match. Each stage in Zoho Recruit is tied to a Job Opening record rather than a global pipeline; we create stage values per active Job Opening during migration.

WebHR job posting records map to Zoho Recruit Job Opening. We extract job title, job description (rich text), department, location, employment type, required experience, and posting date. Active and closed job status migrates to Zoho Recruit's Open/Closed state. The Zoho Recruit Standard tier allows 10 active jobs per recruiter; Enterprise allows 20 per recruiter; we flag any customer exceeding these limits before migration so the customer can upgrade or archive stale postings.

WebHR's Companies/Organization records map to Zoho Recruit's Client module. We extract company name, website, address, industry, and size. The Client module in Zoho Recruit supports contact-person relationships; we link the primary WebHR employee contact to the Client as a primary contact.

WebHR employee records used as hiring managers, interviewers, and recruiters map to Zoho Recruit User accounts. We resolve by email match against Zoho Recruit's user table. Any WebHR employee without a corresponding Zoho Recruit User is held in a reconciliation queue; the customer's admin provisions the missing User before record import resumes.

WebHR notes attached to candidate records migrate to Zoho Recruit Notes linked to the Candidate. We preserve the note body, author (mapped to Zoho Recruit User), and timestamp. If notes contain file attachments, we enumerate the attachment metadata and upload the blobs to Zoho Recruit's Document Library under the corresponding Candidate.

Leave and PTO records in WebHR do not have a native equivalent in Zoho Recruit's ATS data model. We do not migrate leave balances or leave history because Zoho Recruit is an ATS, not a core HRMS. We flag this as a gap and recommend migrating leave data separately to Zoho People or another HRMS if the customer requires it.

WebHR Performance Review records use custom rating templates with customer-defined scales (1-5, Strength/Development, numerical). Zoho Recruit has no native performance review module. We extract the review records during discovery and deliver them as a structured CSV with the original rating scale preserved. If the customer wants these records in Zoho Recruit, we set up a custom module to receive them; otherwise they are excluded from the ATS migration scope.

WebHR file attachments (resumes, contracts, certifications) stored under the Files module migrate to Zoho Recruit's Document Library. We enumerate file metadata via WebHR API, download blobs, and upload them to Zoho Recruit linked to the corresponding Candidate or Client record. File naming conventions are preserved for traceability.

WebHR organizational department records map to Zoho Recruit's Department module. This supports job opening department assignment in Zoho Recruit. We extract department name and parent department hierarchy for nested department structures.

WebHR's Scheduler module stores shift assignments and rosters. Zoho Recruit has no scheduling module. We do not migrate shift data. If the customer uses WebHR for workforce scheduling, we recommend a separate migration to Zoho Shifts or Zoho People Plus as a standalone engagement.

WebHR custom form field data and employee-level custom field values migrate to Zoho Recruit custom fields created during schema setup. We extract the actual custom field names, types, and values during discovery and create matching Zoho Recruit custom fields (up to 50 per module on Standard, 300 per module on Enterprise) before candidate import. Any fields exceeding the destination edition limit are flagged for field consolidation or Enterprise upgrade.