Migrate your WebHR data

Core employee record in WebHR contains all standard HR fields (name, contact, job title, department, hire date, salary, status). We read these via GET /v3 with module=Organization and map them 1:1 to the destination Employee object. Effective-date changes on compensation are preserved as separate history rows.

WebHR's CompaniesList endpoint exposes the parent organization record. For multi-entity deployments, we extract each company as a separate org unit in the destination system.

Leave records include leave type, start/end dates, status, and balance consumed. We migrate the full leave history including approved, pending, and denied records. Balance forward is calculated and written as an opening balance on the destination system.

Candidates are created via the ATS module and include application stage, screening data, and attachments. The application pipeline stage names vary by customer configuration, so we map them to the destination's equivalent pipeline stages and flag any custom stages that have no clear equivalent.

Performance module stores review records linked to employees with ratings, goals, and feedback text. Custom review templates and rating scales differ across accounts, requiring field-level mapping to the destination's review object schema.

Payroll is a paid add-on module at $2/employee/month. Historical payslips and payroll runs are exported via API where the payroll module is active. Year-to-date earnings and deductions are computed from historical runs and written as opening balances at migration cut-off.

Clock-in/clock-out timestamps and timesheet data are available from the Time & Attendance module. We migrate approved timesheet records and flag any unprocessed or pending entries that require manual review at cut-over.

WebHR's Files module stores employee documents (contracts, IDs, certifications) as binary blobs. We enumerate all file metadata and download the blobs for re-upload to the destination HRMS, preserving original filenames and content types.

Benefit enrollment records are stored under the Benefits module. We extract the benefit type, coverage level, and enrollment dates. Dependent and beneficiary details are mapped as sub-records where the destination schema supports them.

Signed documents from the eSignature module are tracked with status and timestamp. We migrate the record of the signed document and its audit trail, noting the original signatory and signing date.

Custom forms created by the customer in the Forms module contain field data tied to specific employees. We export the form response records and field values, mapping them to the destination's custom field or employee property structure.

Scheduler module stores shift assignments, rosters, and shift swap records. We extract active shift patterns and map them to the destination's scheduling or workforce management object, flagging recurring shift templates that may require translation.