Migrate from Harri to BambooHR

Harri Workers (employees and applicants) map directly to BambooHR Employee records. Standard fields including firstName, lastName, dateOfBirth, hireDate, employmentStatus, and jobTitle migrate 1:1. Harri custom Worker properties map to BambooHR custom Employee fields. We extract Workers by Location during scoping and chunk large exports by Location to avoid timeout during extraction. Any Harri Worker without a matching BambooHR Employee email is held in a reconciliation queue for the customer's admin to resolve.

Harri Positions define job titles within a Location, including title, pay rate, FT/PT/seasonal classification, and department. The Position title maps to BambooHR's jobTitle standard field. Pay rate and classification migrate as custom Employee fields (e.g., payRate__c, employmentType__c) since BambooHR stores compensation in custom fields or in the optional BambooHR Payroll add-on rather than as standard fields.

Harri Locations represent individual restaurant or hotel properties with addresses, manager assignments, and associated Positions and Workers. BambooHR does not have a native multi-location hierarchy. We map Locations to a custom Location__c text field or to the department structure depending on whether the customer wants per-property reporting. Multi-location enterprises with dozens or hundreds of Locations receive a Location mapping table as part of the migration package.

Harri Shifts are time-block records assigned to Workers at a Location, including start/end times, shift type, and coverage requirements. BambooHR does not have a native shift scheduling object. We migrate active shift data as a custom ShiftHistory object with fields for shiftDate, startTime, endTime, shiftType, and Location lookup. Recurring shift patterns require interpretation; we document the pattern cadence separately for the customer's admin to configure in BambooHR's time-off or scheduling module.

Harri Applications track candidate submissions for Positions, including application date, source, stage in the hiring pipeline, and interview scores. If the customer licenses BambooHR Hiring, applications migrate as BambooHR Applicants. Pipeline stage names vary by customer configuration in Harri; we map each named stage to a corresponding BambooHR Hiring stage or to a custom applicantStatus__c field if BambooHR Hiring is not in use. Applications without an offer acceptance map as Applicants; those with an accepted offer migrate as Employee records with a hire date set from the Application.

Harri stores structured onboarding task checklists tied to new-hire Workers, including task name, completion status, due date, and custom task fields. If the customer licenses BambooHR's onboarding module, tasks migrate as onboarding steps. Otherwise, task completion status and due dates migrate as custom Employee properties (e.g., onboardingTaskComplete__c, onboardingTaskDueDate__c) or as notes attached to the Employee record.

Harri tracks compliance data including certification expiry dates, mandatory training completion, and regulatory acknowledgements tied to hospitality-specific requirements. Compliance record types vary by jurisdiction and customer setup. We map each compliance record type to a corresponding BambooHR custom Employee field in the Certification or Custom tab, preserving the expiry date, completion status, and certification name. Mandatory training records migrate as custom fields or notes on the Employee record.

Harri stores employee documents including contracts, ID scans, and policy acknowledgements as file attachments. We migrate documents as files attached to the corresponding BambooHR Employee record via BambooHR's file upload API, preserving original filenames and upload timestamps. Document metadata (document type, expiry date) migrates as a BambooHR custom field if the document type field is required.

Harri's employee engagement and pulse survey module stores response data tied to its internal engagement engine. There is no documented export mechanism for engagement survey responses. We exclude engagement survey data from migration scope and flag it upfront in the discovery document. Customers who need historical engagement data must export it manually from Harri's UI before termination; it will not be included in the standard data export.

Harri handles payroll via integration with third-party providers rather than natively. Historical earnings, deductions, pay stubs, and tax withholdings are stored in the payroll system, not in Harri. We do not migrate payroll data from Harri directly. We instruct customers to export historical payroll from their payroll provider separately and import it into BambooHR Payroll (or their chosen payroll system) independently. Harri's Position pay rate migrates as a custom Employee field to serve as a reference, but this is not payroll history.