Migrate from HROne to BambooHR

HROne Employee records map to BambooHR Employee via standard fields (firstName, lastName, workEmail, jobTitle, department, location, employmentHistoryStatus, hireDate, terminationDate, supervisor). The HROne per-user billing model can inflate headcount—some organizations have more user accounts than active employees—so we audit the HROne user list separately from the employee list and exclude inactive or shared accounts. BambooHR uses HTTP Basic Auth with an API key that inherits the permissions of the generating user account; we require a dedicated service account with scoped permissions rather than an admin's personal key during migration.

HROne stores salary structures, pay components, and compensation histories as separate associated records joined on employee ID. BambooHR stores payRate as a single flat field on the Employee record. We collapse HROne's multi-component compensation (base salary, allowances, deductions, variable pay) into a single effective payRate value for the most recent active compensation record, and preserve the full compensation history in a structured migration artifact for the customer's admin to reconcile against BambooHR's separate Payroll add-on module if applicable.

HROne's Clock-in/out logs, shift assignments, and overtime records map to BambooHR's Time Tracking feature if the customer has enabled it. HROne stores attendance timestamps in local timezone of the employee's office or biometric device, and multi-state or multi-country organizations export mixed-timezone data in a single extract. We detect mixed-timezone exports during profiling, normalize all timestamps to UTC before transformation, and map them to the BambooHR time-tracking schema. BambooHR does not support biometric device integration natively; organizations relying on biometric hardware must evaluate BambooHR-compatible time-clock hardware or a third-party attendance integration post-migration.

HROne leave entitlements, accrual policies, and current balances per employee map to BambooHR Time Off types. HROne plan-specific leave type configurations (earned leave, sick leave, casual leave, comp-off) require explicit mapping to BambooHR Time Off categories, and carry-forward rules require manual reconfiguration in BambooHR's accrual policy settings because BambooHR does not import accrual logic from HROne. We deliver a leave-type mapping table and flag each carry-forward discrepancy for admin review before the migration date.

HROne stores employee documents (offer letters, contracts, ID proofs) as DocumentTemplate records or file attachments. We extract file binaries and associated metadata (documentType, language, upload date) and map them to BambooHR's employee Files section. BambooHR does not have a native document type taxonomy, so we create a folder structure per employee using the document type as the folder name and store the original filename and HROne record ID in the file description for audit traceability.

HROne departments, cost centers, and reporting hierarchy export and map to BambooHR's department and division structure. Manager relationships (supervisor fields) map directly to BambooHR's supervisor field on the Employee record. HROne's multi-entity and multi-country organization structures (available on Enterprise tier) require flattening into BambooHR's single-org model unless the customer has multiple BambooHR accounts per entity, which adds to configuration scope.

HROne organizations frequently add custom fields to the Employee object and other modules for region-specific or policy-specific data. These custom fields are not consistently exposed via HROne's public API and may only appear in UI exports and reports. We add a manual custom-field discovery step to every HROne migration: we request a sample employee export from HROne's UI alongside the API export, compare field counts, and flag any discrepancy for field-level audit. Custom fields then map to BambooHR custom fields using the numeric field IDs returned by GET /v1/meta/fields, which are account-specific and cannot be hardcoded across migrations.

HROne's recruitment module (available on Professional and Enterprise tiers) with job postings, candidate pipelines, and applicant data maps to BambooHR's ATS feature. Interview scores and custom recruiter fields in HROne require explicit mapping to BambooHR's custom applicant fields. BambooHR ATS supports 5 job openings on Core and 25 on Pro; organizations with more than 25 active openings at migration time must upgrade plans or archive inactive postings before migration.

HROne's performance module with goals, appraisal cycles, and review ratings per employee maps to BambooHR's Performance Management feature (Pro plan and above). If the destination BambooHR account is on the Core plan, performance appraisal data cannot be loaded and we flag it as a gap requiring either a plan upgrade or an alternative performance tracking solution post-migration. Appraisal dates, ratings, and reviewer assignments migrate as structured records in the migration artifact regardless of destination plan.

HROne Workflows and approval chains are not migrated as automation code because the execution models differ. We deliver a written inventory of every active HROne Workflow with its trigger conditions, action sequence, and assigned approvers, and map each to a recommended BambooHR Workflow equivalent or approval chain configuration. The customer's admin rebuilds these in BambooHR's Workflow builder post-migration. BambooHR's Workflow coverage differs from HROne's; not every HROne automation pattern has a direct BambooHR equivalent.