Migrate from Harri to Recruit CRM & ATS

Harri Workers (active employees) map directly to Recruit CRM Contacts. Standard fields—first name, last name, email, phone, hire date, job title, employment status—map 1:1 to the Contact object. Harri's worker_id becomes a custom field harri_worker_id__c on Contact for audit and reconciliation. Harri Location assignment migrates as a custom lookup field or Organization association depending on how the customer configures their Recruit CRM organization hierarchy.

Harri Locations (individual restaurant or hotel properties) represent the top of Harri's hierarchy: each Location has a manager, address, position catalog, and assigned Workers. Recruit CRM has no native multi-property hierarchy; Locations must be merged into Recruit CRM Organizations, with the property address and manager stored as custom fields on the Organization record. Multi-location operators with 20+ Locations will have multiple Location records resolving to a smaller number of Organization records in Recruit CRM.

Harri Positions (job listings within a Location) map to Recruit CRM Jobs. Harri position title, FT/PT/seasonal classification, pay rate, and department migrate to the corresponding Recruit CRM Job fields. Job status (active/paused/closed) maps from Harri position status. Positions without an active application pipeline still migrate as historical job records if the customer requests placement history preserved.

Harri Applications track candidate submissions for Positions: application date, source, pipeline stage, and interview scores. These map to Recruit CRM Candidates with the job association resolved at migration time. Pipeline stage names are Harri-customer-specific; we preserve the original stage label as a custom field candidate_stage__c rather than forcing it into Recruit CRM's default pipeline stages, which the customer's admin configures post-migration.

Harri stores applicants as Workers with an applicant-specific status. Unhired applicants (pipeline candidates not yet converted to employees) migrate as Recruit CRM Candidates with a custom field harri_applicant_status__c preserving the original Harri applicant stage. We deduplicate on email address during import to avoid creating duplicate Candidate records where a candidate applied multiple times.

Harri Shifts are time-block records assigned to Workers at a Location with start/end times, shift type, and coverage requirements. Recruit CRM has no native scheduling object. We migrate the most recent shift assignment as custom fields on the Contact record (most_recent_shift_date__c, shift_type__c) rather than a full shift history, because Recruit CRM's data model does not support recurring shift records. Customers needing full shift history retain it in a reporting export from Harri.

Harri stores structured onboarding task checklists tied to new-hire Workers: task name, completion status, due date, and custom fields. Recruit CRM has no native onboarding task object. We migrate onboarding task data as a serialized JSON custom field onboarding_tasks__c on the Contact record, or as a multi-select picklist of completed task names if the checklist is short (under 20 tasks). Complex onboarding flows require manual rebuild in Recruit CRM.

Harri tracks compliance data specific to hospitality regulations: certification expiry dates, mandatory training completion, tip-credit acknowledgements, and regulatory acknowledgements. Recruit CRM has no native compliance object. We migrate the most recent compliance record fields (certification_type__c, certification_expiry__c, training_complete__c) as custom fields on the Contact record. Historical compliance events migrate as a separate compliance export file the customer's admin ingests manually, because Recruit CRM cannot model the jurisdiction-specific regulatory fields that Harri handles natively.

Harri stores employee documents: contracts, ID scans, policy acknowledgements. Document exports from Harri are file-based. We migrate documents as attachments to the corresponding Contact record in Recruit CRM, preserving the original filename, upload timestamp, and file type. PDF and image formats migrate without transformation; documents over 25 MB are flagged for the customer admin to handle manually due to Recruit CRM attachment size limits.

Harri stores pay rate on the Position record (hourly rate, salary, FT/PT classification). Recruit CRM Jobs have no native pay-rate field. We migrate pay rate as a custom field pay_rate__c on the Job record, preserving the currency and rate type. The customer's admin maps this field into any Recruit CRM reporting or client-facing job order as needed post-migration.