Migrate your Harri data

Workers are the primary employee record in Harri, containing standard fields (name, contact, employment status, hire date, job title, department). We map these 1:1 to the destination HRMS Employee object. Custom worker properties are captured via field-level mapping during export.

Positions define job listings within a Location, including title, pay rate, FT/PT/seasonal classification, and department. We preserve position titles, classifications, and any custom fields during migration. Positions may have assigned Shifts and Workers.

Harri organizes operations by Location (restaurant or hotel property). Each Location has an address, manager assignment, and associated Positions and Workers. We map Locations to the destination's equivalent org or site entity, preserving location-level configuration.

Shifts are time-block records assigned to Workers at a Location, including start/end times, shift type, and coverage requirements. Complex recurring shift patterns may require chunked export and re-scheduling in the destination system. We flag open/unfilled shifts as a separate migration lane.

Applications track candidate submissions for Positions, including application date, source, stage in the hiring pipeline, and interview scores. Pipeline stage names vary by customer configuration, so we apply value-mapping during the transform step.

Harri stores structured onboarding task checklists tied to new-hire Workers. Task completion status, due dates, and custom task fields are migrated as custom Employee properties or notes in the destination system.

Harri tracks compliance data including certification expiry dates, mandatory training completion, and regulatory acknowledgements. Compliance record types vary by jurisdiction and customer setup; we flag these as custom fields requiring schema review before mapping.

Harri stores employee documents (contracts, ID scans, policies). Document exports are file-based; we migrate them as attachments to the corresponding Worker record, preserving filenames and upload timestamps.

Harri's employee engagement survey responses and pulse data are tied to the Harri engagement module and are not independently exported via a public API. We do not migrate engagement survey results; we flag this as a scope exclusion during discovery.

Harri handles payroll via integration with third-party providers rather than natively. Pay rates, earnings, and deductions live in the integrated payroll system. We migrate the pay rate from the Position or Worker record but recommend pulling historical payroll data from the payroll provider directly.