Migrate from Grove HR to BambooHR

Grove HR Employee records map directly to BambooHR Employee records. Core fields (first name, last name, date of birth, address, contact details, employment status, job title, start date, department) migrate via CSV export to BambooHR REST API. We resolve Grove's nested document references to separate attachment assets and link them to the corresponding BambooHR Employee record after the employee insert completes. Any custom fields defined on Employee in Grove are detected during scoping, and we map them to BambooHR custom fields on the Employee tab. Grove employee IDs are preserved in a custom BambooHR field grove_employee_id__c for audit trail purposes.

Grove HR leave entitlements (annual leave, sick leave, parental leave) export as balance snapshots per employee per leave type. These map to BambooHR Time Off types with balances entered as static values at migration time. Grove's dynamic accrual rules (accrual rate, carry-over limits, Bradford Factor triggers) are not replicated in BambooHR; instead, we capture the current entitlement and used balance as a fixed snapshot and the customer's BambooHR admin configures accrual rules going forward. Any approved leave between extraction and go-live requires a supplemental import or manual adjustment to avoid double-counting.

Grove HR onboarding is driven by automated checklist templates assigned to employees with task assignments and completion states. Templates are defined at the company level and cannot be exported as reusable objects. We export each assigned checklist item as a standalone task record per employee, capturing task name, assignee, due date relative to start date, and completion status. Completed items migrate as completed tasks; incomplete items migrate as open tasks. The customer's BambooHR admin rebuilds reusable onboarding packet templates from the delivered task list inventory.

Grove HR offboarding checklists follow the same template-to-task decomposition as onboarding. We extract each assigned offboarding task per employee with completion status and link it to the termination record. Template structure (task names, order, assignee roles) is preserved as a flat task list in the migration deliverable for the customer's admin to reconstruct as BambooHR offboarding workflows. Grove's termination reason and exit interview data migrate as notes attached to the employee record.

Grove HR recruitment includes a career site builder, CV storage, and a drag-and-drop hiring pipeline. Candidate records, applications, and pipeline stage history are exportable from Grove HR. We map candidates to BambooHR Applicants and map Grove pipeline stages to BambooHR Job stages. Stage names vary by organisation so we capture the customer's specific stage labels during scoping and configure matching values in BambooHR before import. CV files migrate as attachments to the corresponding BambooHR Applicant record.

Grove HR performance review cycles contain structured rating fields and reviewer assignments per employee. We export completed review records with scores, comments, and reviewer metadata. In-progress reviews migrate as draft reviews in BambooHR with a note flagging their incomplete status. Review templates from Grove HR do not export as reusable objects; we deliver a template inventory document describing each review cycle's structure for the customer's BambooHR admin to rebuild.

Goals linked to employees with progress tracking and due dates export from Grove HR with current status, owner, and linked key results. We map goal records to BambooHR Goals, preserving the goal title, description, progress percentage, due date, and owner assignment. Orphaned goals without an active owner employee are flagged in the migration report and held for the customer's admin to reassign or close.

Training modules and employee completion records export from Grove HR with assignment, completion status, and scores per employee. We map these to BambooHR Training records, preserving the course name, completion date, score (if applicable), and status. Training course content does not migrate; enrollment and completion history does. The customer's BambooHR admin rebuilds training course content separately if needed.

Grove HR time attendance data links to payroll calculations with clock-in/out events, timesheets, and overtime flags. Where attendance data feeds into leave entitlement computation, we export raw timesheet records as a reference dataset rather than a live integration. BambooHR does not have a native clock-in/out module, so timesheet records are stored as an attached reference file on the employee record or mapped to a BambooHR custom field if the customer configures one. Overtime flags migrate as a custom field on the employee.

Employee documents (contracts, payslips, offer letters) export from Grove HR as binary file attachments. We export these as separate file assets with a reference back to the owning employee, then attach them to the corresponding BambooHR Employee record using the BambooHR file upload API. We do not parse or transform document contents. The customer should confirm BambooHR's file storage limits for their plan before committing to a full document migration; BambooHR imposes storage limits that vary by tier.