Migrate from HiBob HRIS to BambooHR

HiBob's People records map to BambooHR Employee profiles. We extract via the People API with system IDs and personal info, job data, employment status, and hire date. BambooHR's Employee object uses a flat field structure versus HiBob's tabbed profile model, so we flatten nested data during the transform. The BambooHR Employee API accepts field names as documented in BambooHR's field reference; custom fields require the customer's admin to provide the internal API field name before we finalize the mapping.

HiBob's Job Catalog API exposes job roles, job families, and job family groups as separate objects; Positions link employees to profiles with budget and opening data. BambooHR stores job title, department, division, employment status, and pay type in a single Job Information table per employee. We map the primary job title and department directly. Multi-job families and budget data from HiBob map to BambooHR custom fields that the customer configures in the destination before migration.

HiBob's org hierarchy derives from the manager relationship stored on the Employee object. BambooHR's Reports To field links directly to another Employee record. We preserve the full reporting chain by resolving manager IDs to BambooHR Employee IDs during migration, maintaining the org structure visible in BambooHR's directory view. If a manager in HiBob has no corresponding BambooHR employee record, we create a placeholder or hold the relationship for the customer's admin to resolve before finalizing.

HiBob's Time Off API provides leave balances and history; the Reports API yields bulk leave snapshots. We extract current balance snapshots per employee per leave type and pending requests separately, flagging any open approvals that require resolution before cutover. BambooHR's Time Off module stores balance entitlements and usage history per employee. We map the leave type names and balances directly where naming conventions match; custom leave types in HiBob map to BambooHR custom leave types that the admin configures before finalizing the import.

HiBob custom list fields return internal string IDs rather than display values; the list metadata endpoint must be called alongside each extraction to resolve IDs to labels. We fetch list definitions before the main data extraction and re-validate metadata before writing to BambooHR. BambooHR custom fields are referenced by their internal API field name, not the display label, so we confirm the exact field names with the customer's BambooHR admin before mapping. Tabular custom fields in HiBob do not map to BambooHR custom fields and are flagged as out of scope.

HiBob stores offer letters, employment contracts, and payslips with metadata exposed via API. BambooHR supports document storage on employee profiles with file attachments. We extract document metadata (file name, type, upload date, associated employee) and binary files via a separate download step, then upload to BambooHR attached to the corresponding employee record. Binary files require authentication to HiBob's document storage API and are downloaded and re-uploaded individually, which extends timeline for accounts with large document volumes.

HiBob PDR cycles, ratings, goals linked to reviews, and review text are accessible via the People API and reporting. BambooHR includes performance review cycles with configurable forms, ratings, and goals. We extract review records with historical ratings and text. Note that BambooHR's performance module does not include HiBob's full engagement survey or 360 feedback scope; survey aggregates and engagement scores are flagged as out of scope. Goals migrate as structured records where the customer has BambooHR Performance enabled.

HiBob's Goals API exposes Goal Types, Goals, and Key Results with progress data and OKR-style linking. BambooHR's Goals module supports goal setting with measurable criteria. We extract goal hierarchies and key result progress as separate goal entries in BambooHR. The OKR-style linking between goals and performance reviews in HiBob does not have a direct BambooHR equivalent; we map the goals but flag the linking as configuration for the customer's admin to re-establish post-migration.

HiBob onboarding workflows are configurable templates with task lists assigned to new hires and managers. BambooHR includes an onboarding module with configurable new-hire checklists. We export active onboarding task configurations and current new-hire onboarding states. The template structure differs between platforms: HiBob's conditional branching and role-based task routing maps to BambooHR's static checklist model. We deliver the task mapping as a written checklist template for the customer's admin to configure in BambooHR, noting which HiBob-specific conditions cannot be replicated without manual rebuild.

HiBob's org chart derives from employee reporting relationships and location/tribe assignments. BambooHR does not have a dedicated org chart object but exposes hierarchical reporting through the directory and the Reports To field. We preserve the reporting line structure and map HiBob locations and divisions to BambooHR's Location and Division fields. Multi-entity structures in HiBob (separate legal entities per country) map to BambooHR's multi-company setup if the customer has that feature, or to Location tags if they operate as a single entity.

HiBob stores compensation bands, salary structures, and compensation review history in the performance and HR modules. BambooHR stores current pay rate and pay type on the Employment tab, with pay change history available via BambooHR Payroll if enabled. We extract salary and compensation band data from HiBob profiles and map current pay to BambooHR's pay fields. Historical compensation review data migrates to BambooHR custom fields if the customer requires retention of that history; the customer's admin configures the destination custom fields before migration.