Migrate from Harri to Crelate

Harri Workers (employees and applicants) map to Crelate Contacts. Harri Worker fields including first name, last name, email, phone, employment status, hire date, job title, and department migrate to Crelate Contact standard fields. Harri's employment status values (active, inactive, terminated) map to Crelate's contact status system. If a Harri Worker is currently an active applicant, they migrate as an active Crelate Contact in the recruiting pipeline; if they are an active employee, they migrate as a Crelate Contact without a job application association. Custom Worker properties migrate to Crelate custom fields on the Contact record, which Crelate supports for Text, Number, Date, and Picklist types under Settings | Core Records | Contacts.

Harri Positions define job listings within a Location, including title, pay rate, FT/PT/seasonal classification, and department. Positions map to Crelate Job records, which are a core Crelate object with Name (job title), Description, and custom fields. The pay rate from the Harri Position migrates as a custom field on the Crelate Job. Position classifications (full-time, part-time, seasonal) map to Crelate Job type or a custom picklist field. Each Harri Position is tied to a specific Location, so Location lookup must resolve before Position export to maintain the Location-to-Company relationship in Crelate.

Harri Locations represent individual restaurant or hotel properties, each with an address, manager assignment, and associated Positions and Workers. Locations map to Crelate Company records, which are a core object requiring only Name as a required attribute per Crelate's API. The Location address migrates to Crelate Company address fields. For multi-location operators with dozens or hundreds of Locations, we chunk the export by Location during scoping, validate data completeness per site, and import in batches to avoid API timeout. Harri Location managers map to Crelate Company primary contact or a custom manager field.

Harri Applications track candidate submissions for Positions, including application date, source, hiring pipeline stage, and interview scores. Applications map to Crelate Application records, which are linked to a Contact (candidate) and a Job (position). Harri pipeline stage names vary by customer configuration, so we establish a stage mapping table during scoping that aligns Harri stages to Crelate Application statuses. Interview scores and custom application fields migrate as custom fields on the Crelate Application record.

Harri Shifts are time-block records assigned to Workers at a Location with start/end times, shift type, and coverage requirements. Crelate has no native shift or scheduling module. We do not migrate Shifts as records. Instead, we extract the shift data as a structured CSV export during discovery, deliver it to the customer, and recommend they import it into their standalone scheduling tool (Deputy, 7shifts, or Homebase) post-migration. If the customer has no separate scheduling tool, we flag this gap during scoping so it is addressed before cutover.

Harri stores structured onboarding task checklists tied to new-hire Workers, including task name, completion status, due date, and custom fields. Task data migrates to Crelate as Note records attached to the Contact (worker) or as Task records with a custom onboarding category. We set the Task status to reflect Harri's completion flag. Because Crelate does not have a native onboarding workflow module, the task checklist structure is preserved as a Note or a structured custom field rather than an active workflow.

Harri tracks compliance data including certification expiry dates, mandatory training completion, and regulatory acknowledgements for hospitality-specific requirements. Compliance record types vary by jurisdiction and customer configuration. We pre-create custom fields on the Crelate Contact record for each compliance attribute (certification type, expiry date, training completion flag) during the schema design phase. If there are jurisdiction-specific compliance records, we group them under a custom field set and document the full compliance schema in the migration deliverable for the customer's admin to validate.

Harri stores employee documents (contracts, ID scans, policy acknowledgements) as file attachments. Document exports are file-based; we migrate them as attachments to the corresponding Worker Contact record in Crelate, preserving filenames and upload timestamps. Crelate supports file attachments on Contact records via its file management system. We verify that document MIME types (PDF, image, Word) are preserved during the transfer and that the linked Contact record exists before attaching files.

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. Customers who need historical engagement data should export it manually from Harri's UI before termination, as it will not be included in the standard data export. Crelate has no engagement survey module.

Harri does not process payroll natively; pay rates are defined at the Position level and maintained in an integrated third-party payroll provider. We migrate the pay rate from the Harri Position as a custom field on the Crelate Job record (for the pay rate associated with the role) and optionally on the Crelate Contact record (for the worker's current pay rate). Historical earnings, deductions, pay stubs, and tax withholdings live in the integrated payroll system and are not in Harri; we instruct the customer to export payroll data from their payroll provider separately.

Harri Workers commonly have custom properties beyond the standard fields: emergency contact information, food handler certifications, uniform sizes, language preferences, and hospitality-specific attributes. Crelate supports custom fields on Contact records for Text, Number, Decimal, Money, Date, Picklist, and Boolean types. We pre-create the destination custom fields in Crelate under Settings | Core Records | Contacts before migration, matching Harri's custom property names and data types. The Crelate API reference at help.crelate.com describes the Logical Name field used for API access to custom fields.

Harri Positions may include custom properties such as uniform requirements, tip-credit eligibility, break policy, or department-specific scheduling rules. These migrate as custom fields on the Crelate Job record. Crelate's field mapping documentation shows that field mappings can copy answers from custom forms directly to columns within a parent record (Contact, Company, or Opportunity), and custom fields on Job are accessible via the Crelate API v3. We create the custom Job fields during schema design and map them during the Position-to-Job import phase.