Migrate from WebHR to Recruit CRM & ATS

WebHR employee records map to Recruit CRM Candidates as contact records. The employee's first name, last name, email, phone, job title, department, and hire date migrate to the Candidate object fields. The WebHR employee ID is preserved as a custom field webhr_employee_id__c for audit and cross-reference. Active employment status from WebHR (current employee) maps to a Candidate status value; terminated employees migrate with their termination date retained.

WebHR exposes the parent organization record via GET /v3 CompaniesList. This maps to Recruit CRM's Organization field on the Candidate record. For multi-entity WebHR deployments, each company extracted from CompaniesList becomes a separate Organization value in Recruit CRM, preserving the hierarchical structure. The WebHR company name, address, and industry fields map to the corresponding Candidate organization fields.

WebHR ATS candidates are the primary migration payload for this pair. Each WebHR candidate record — including name, email, phone, resume/CV, source, screening notes, and application status — maps to a Recruit CRM Candidate record. The candidate's application pipeline stage from WebHR maps to the corresponding Recruit CRM pipeline stage; custom stage names require discovery-phase extraction before mapping because they are customer-defined rather than canonical.

WebHR job postings (created in the Recruitment module) map to Recruit CRM Job records. Fields include job title, job type (permanent/contract/intern), description, required qualifications, experience level, number of positions, and opening/closing dates. WebHR job post status (open/closed/draft) maps to Recruit CRM job status. Job postings linked to candidates via the application relationship preserve the linkage through Recruit CRM's candidate-job association.

Each WebHR candidate applying to a job opening generates an application record. This maps to Recruit CRM Application records linking the Candidate and Job. The application stage in WebHR (e.g., Screening, Technical Interview, Offer) maps to the Recruit CRM application stage field, and the stage transition timestamps migrate to the Application object for pipeline analytics. Custom stage names require per-account discovery.

WebHR leave records (approved, pending, denied) include leave type, start/end dates, status, and balance consumed. These do not map to a native Recruit CRM object because Recruit CRM is an ATS/recruitment CRM, not an HRMS. We migrate leave history as note attachments on the Candidate record with a typed note category, preserving the leave type, dates, and status for HR audit purposes. Leave balance data migrates as a formatted text note or custom field if the customer configures one in Recruit CRM.

WebHR performance review records — including review period, rating, goals, and feedback text — migrate as typed notes on the Candidate record. Custom review templates and non-standard rating scales are customer-defined and must be extracted during discovery; we build a per-account field map before migration. The structured rating score migrates to a numeric custom field if Recruit CRM has one configured, otherwise it appears in the review note body.

WebHR files module stores employee documents (contracts, IDs, certifications, CVs) as binary blobs. We enumerate all file metadata via the WebHR API and download each blob for re-upload to Recruit CRM as a Candidate attachment. The original filename, MIME type, upload date, and file content migrate. Resume and CV files associated with recruitment candidates map to Recruit CRM's resume attachment field on the Candidate record, preserving parseability for candidate parsing features.

WebHR payroll is a paid add-on at $2/employee/month. Historical payslips, year-to-date earnings, and deduction records are not part of a standard ATS data model and Recruit CRM does not have payroll objects. We scope payroll data availability during discovery by checking whether the customer's WebHR subscription includes the payroll module. If payroll is active, we extract payslip records as PDF attachments on the Candidate (or as a separate archive) and advise the customer to maintain payroll records in a dedicated payroll system post-migration.

Clock-in/clock-out timestamps and approved timesheet records are HRMS-specific data with no equivalent in Recruit CRM's ATS/recruitment model. We extract approved timesheet records as a CSV report during migration for the customer's HR admin to archive, and flag any unprocessed or pending entries requiring manual resolution. Recruit CRM is not designed to store time-and-attendance data; it is not migrated as live records.

WebHR benefit enrollment records — benefit type, coverage level, enrollment dates, and dependent/beneficiary details — migrate as typed notes on the Candidate record. Benefit type maps to a custom field if Recruit CRM has one; otherwise the enrollment detail appears in the note body. This data is retained for HR audit continuity rather than for active recruiting use in Recruit CRM.