Migrate from WebHR to Crelate

WebHR Candidates from the ATS module map to Crelate Contacts of the candidate type. We extract the candidate name, email, phone, resume URL, application stage, screening data, and source attribution. The WebHR application pipeline stage names (Screening, Technical Interview, Culture Fit) are customer-configured, so we resolve the actual stage values during discovery and map them to the equivalent Crelate pipeline stage or Activity status. Any candidate-specific custom fields in WebHR map to Crelate custom fields on Contact.

If WebHR contains client or company contact records in its Organization module, we extract them as Crelate Contacts of the client type. Name, company affiliation, email, phone, and address fields map directly. We flag any records with ambiguous type classification (candidate vs. client) for the customer's admin to verify during reconciliation.

WebHR Company records from the Organization module map to Crelate Companies. The company name, domain/website, address, industry, and size fields migrate directly. For multi-entity WebHR deployments, each company is extracted as a separate Crelate Company. The Company record is created in Crelate before any linked Contacts are imported so that the Company-Contact relationship is satisfied at insert time.

WebHR job requisitions and open positions in the Recruitment module map to Crelate Jobs. We extract job title, description, location, employment type, department, salary range, and job status. Active jobs migrate as open Crelate Jobs; filled or closed WebHR positions migrate as closed Jobs with historical placement data linked via Activities.

WebHR's custom pipeline stage names vary per account configuration, with no stable canonical schema. During discovery we extract the customer's actual pipeline stages and status values, then configure the corresponding Crelate pipeline stages and job workflow steps. We apply a migration field map that routes each WebHR stage name to the equivalent Crelate stage identifier before inserting candidate records.

WebHR engagement records (call logs, email threads, meeting records, task completions) on candidate records migrate to Crelate Activities linked to the corresponding Contact. We preserve the engagement type, subject, body content, timestamp, and owner attribution. Activity ordering is maintained by setting the Crelate Activity date to the original WebHR timestamp. Unprocessed or pending WebHR engagements are flagged for manual review before migration.

WebHR's Files module stores binary blobs (resumes, contracts, certifications, identification documents) linked to candidate and employee records. We enumerate all file metadata from WebHR, download the binary blobs, and upload them as Crelate Attachments linked to the corresponding Contact, Company, or Job via ContentDocumentLink. Original file names, MIME types, and upload timestamps are preserved. We verify blob integrity via checksum before upload.

WebHR Leave and PTO records have no equivalent object in Crelate's recruiting CRM. Crelate does not manage time-off, absence tracking, or accrual balances. We advise the customer's admin to retain WebHR read-only access for historical leave records or export them as a CSV for the destination HRMS. This boundary is documented in the migration scope before work begins.

WebHR payroll data (payslips, year-to-date earnings, deductions) is available only if the customer's subscription includes the Payroll add-on at $2/employee/month. Crelate does not process payroll or store payroll history. We scope payroll data completeness during discovery and, where the module is active, extract the records as a structured export for the customer's admin to file in WebHR read-only mode or migrate to a dedicated payroll platform.

WebHR Performance module records (ratings, goals, feedback text, custom review templates) do not have a Crelate equivalent. Crelate is a recruiting and CRM platform, not an HRMS. We extract the review records as a structured export and advise the customer's admin to retain WebHR read-only access for performance history or move it to a dedicated HRMS post-migration.

WebHR Benefits module records (enrollment type, coverage level, dependent details, beneficiary information) have no Crelate equivalent. We extract a full benefits enrollment export as a CSV and flag this data for the customer's admin to migrate to a dedicated benefits administration platform. This boundary is confirmed during discovery scoping.

WebHR custom forms and customer-configured Performance Review templates with non-standard rating scales and field names are exported as structured data. The form response records and field values are extracted during discovery and provided as a written field map and data export. We do not rebuild custom forms in Crelate as part of the standard migration scope; this is documented as a post-migration admin task.