Migrate your Grove HR data

Employee is the central record in Grove HR. It stores contact details, job role, start date, employment status, and links to documents (contracts, payslips). We export the full employee profile including custom properties as a flat record and remap any manager/owner references to the destination.

Grove tracks leave entitlements per employee with balances updated by approved requests. We extract leave type configurations (annual, sick, parental) and historical request records, preserving approval status and balances at cutover date.

Onboarding is driven by automated checklists with task assignments and completion states. Offboarding has its own checklist variant. We map checklist items to a destination task structure; any incomplete items are flagged for manual completion after migration.

Grove includes a career site builder, CV storage, and a drag-and-drop hiring pipeline. Candidate records, applications, and pipeline stage history are exportable. Stage names vary by organisation so we map them to standard deal stages in the destination.

Performance review cycles contain structured rating fields and reviewer assignments per employee. We export completed review records with scores, comments, and reviewer metadata. Draft or in-progress cycles are flagged separately.

Goals are linked to employees with progress tracking and due dates. We export goal records including current status, owner, and any linked key results. Orphaned goals without an active owner are noted.

Time attendance data links to payroll calculations. Clock-in/out events, timesheets, and overtime flags are exportable. Where attendance data is used to compute salary, we export raw timesheet records for recalculation in the destination payroll.

Employee documents are stored as binary attachments linked to each employee record. We export these as-is as separate file assets with a reference back to the owning employee. Customers should confirm document retention requirements for payslips in the destination system.

Training modules and employee completion records are stored per employee. We export training assignment, completion status, and scores. Training course content is out of scope but enrollment records transfer.

Grove stores company-level settings, departments, and locations. We map departments to the destination org chart structure. Custom company properties are extracted as key-value pairs and mapped to equivalent destination fields.

Custom fields can be defined on employee and other objects. We detect all custom field definitions during scoping and export values alongside standard fields. Destination mapping depends on whether the target system supports equivalent custom field names and types.