Migrate from WebHR to BambooHR

WebHR Employee records map 1:1 to BambooHR Employee. The WebHR employee profile (name, contact, job title, department, hire date, employment status, supervisor) maps to BambooHR's standard Employee fields. Custom fields on the WebHR employee record map to BambooHR custom fields of equivalent type (text, number, date, dropdown). Department and location map to BambooHR's organizational hierarchy fields. Employment status transitions (active, terminated, on leave) preserve the effective date of the most recent status change.

WebHR's CompaniesList endpoint exposes the parent organization record. For single-entity deployments, the WebHR company maps to a BambooHR Company record used as the employer entity for benefits and onboarding context. Multi-entity WebHR deployments map each company as a separate BambooHR Company, with the migration scope clarified during discovery since BambooHR's multi-company support is scoped to the customer's plan tier.

WebHR leave records (approved, pending, denied) migrate to BambooHR Time Off as individual entries with type, start date, end date, status, and hours/days consumed. We compute the balance forward from the leave history and set the current balance on the BambooHR Time Off page. The leave type mapping is direct where WebHR types match BambooHR defaults (PTO, Sick, Bereavement); custom WebHR leave types map to BambooHR custom Time Off types created during schema setup before migration begins.

WebHR ATS candidates migrate to BambooHR Applicants. The application stage name from WebHR (which varies by customer configuration: Screening, Technical Interview, Culture Fit, etc.) maps to a BambooHR stage name defined during schema setup. Application attachments, screening notes, and score data transfer as BambooHR Applicant custom fields. Job opening links are preserved as BambooHR Job Opening references where the corresponding opening exists in BambooHR.

WebHR's customer-configured pipeline stages (no stable canonical schema) require field-level discovery before migration. We extract the actual stage names and order from the source account during scoping, create matching stages in BambooHR's Job Opening configuration, and build a stage-by-stage map that handles any missing or renamed stages with a default fallback. This adds one to two days to scoping for accounts with complex or non-standard pipeline configurations.

WebHR Performance module records link reviews to employees with ratings, goals, and feedback text. Custom review templates and non-standard rating scales require field-level mapping: we extract the actual template fields during discovery, map each to a BambooHR review field or custom field, and apply the mapping during migration. Ratings are normalized to the destination scale where source and destination rating systems differ. Goal records migrate as separate Performance Goal entries linked to the same employee.

WebHR payroll data is only accessible via API if the customer's subscription includes the Payroll add-on at $2/employee/month. Historical payslips, year-to-date earnings, and deduction records migrate to BambooHR Payroll where the customer also activates BambooHR Payroll on the destination. We scope the payroll module status before migration and advise on whether a temporary WebHR payroll upgrade for the migration window is warranted, or whether payroll is entered manually post-migration. YTD totals and deduction histories are written as BambooHR Payroll records with effective dates preserved.

Clock-in/clock-out timestamps and approved timesheet records from WebHR's Time & Attendance module migrate to BambooHR Time Tracking entries. We migrate approved timesheet records with hours worked, overtime, and the relevant pay period dates. Unprocessed or pending entries are flagged in the reconciliation report and left for manual resolution post-migration. Attendance policy settings (grace periods, rounding rules) do not migrate as configuration; they are documented in the handoff inventory for the customer's HR admin to reconfigure in BambooHR.

WebHR Files module stores employee documents (contracts, IDs, certifications) as binary blobs. We enumerate all file metadata via the API, download the blobs, and re-upload them to BambooHR as Files attached to the corresponding Employee record. File names, MIME types, upload dates, and uploaded-by metadata are preserved. Documents exceeding typical attachment size limits are flagged for chunked transfer or alternative delivery.

Benefit enrollment records from WebHR's Benefits module (available on the Benefits add-on at $1/employee/month) migrate to BambooHR Benefits. We map the benefit type, coverage level (employee only, employee plus spouse, family), enrollment effective date, and any waiting period. Dependent and beneficiary details map as BambooHR dependent records attached to the benefit enrollment. Benefit carrier details and plan names are preserved in free-text fields where BambooHR's native benefit carrier lookup does not include the specific plan.

Signed document records from WebHR's eSignature module migrate as BambooHR document status entries. The record captures the document name, signatory, signing date, and signature status (signed, pending, voided). The actual signed PDF does not re-sign; we attach the downloaded blob to the BambooHR employee file and document the original signatory and signing date as metadata. Audit trail entries migrate as notes on the document record.