Migrate from HiBob HRIS to Crelate

HiBob employee records (People object) map to Crelate Candidate records. We map personal fields (legal name, preferred name, email, phone, address) directly. Work-related properties (title, department, employment status, start date, location) map to Crelate's work history and candidate profile fields. Employment status (active, terminated, on leave) migrates as a custom Candidate field. HiBob system IDs are preserved in a custom field hibob_id__c for reconciliation. Note: Crelate Candidates represent people in the recruiting pipeline, not employed people; if the customer needs to track both active employees and candidates, they must configure Crelate's candidate-employee distinction during setup.

HiBob custom fields on the People object migrate to Crelate custom fields on Candidate. List-type custom fields return internal string IDs rather than display values from HiBob's API; we resolve these against the list metadata endpoint before mapping to Crelate picklist or multi-select fields. Custom field type translation (date, boolean, number, text) maps directly. Fields that have no Crelate equivalent (e.g., compensation-related custom fields) are flagged during scoping and excluded from migration scope.

HiBob's org chart derives from employee reporting relationships stored on the People object. We extract manager-employee relationships and map them to Crelate's team and department structure, where applicable to recruiting workflow. Reporting line depth beyond the immediate manager is preserved in a custom text field hibob_reporting_chain__c. Note: Crelate's org structure is recruiting-oriented (hiring team, recruiters, hiring managers) rather than a full org chart; deep organizational hierarchies that exist in HiBob may need to be reduced or manually reconstructed in Crelate.

HiBob's Job Catalog (roles, job families, job family groups) can be referenced in Crelate as job titles on Job Orders. Position-to-employee assignments in HiBob do not map directly to Crelate because Crelate tracks open positions (Job Orders) rather than filled positions. We migrate job title and job family data as reference text on the Candidate record or as tags in Crelate's classification fields.

HiBob employee documents (offer letters, contracts, signed policies, onboarding docs) have metadata accessible via API. We extract document metadata (filename, type, upload date, associated employee) and map it to Crelate's document attachment model on the Candidate. Binary file downloads require a separate download step and re-upload into Crelate. Note: Crelate's document model is oriented around recruiting documents (resumes, cover letters, assessment results); HR documents (employment contracts, benefits elections, performance reviews) may not have a natural home in Crelate's schema.

HiBob performance review cycles and one-on-one records do not migrate. Crelate has no performance review object. We document the review history, ratings, and review text in a written archive report for the customer's HR team to store externally or import into a performance management platform they adopt post-migration. PDR cycle configuration (review periods, templates, rating scales) is also not migrated and is delivered as a written inventory.

HiBob's Goals and OKR data does not migrate to Crelate. Crelate is an ATS with no goals or key results object. We export goal hierarchies, progress data, and OKR linkages as a written inventory document for the customer to import into their chosen performance or OKR platform post-migration.

HiBob engagement survey templates, response data, and aggregated engagement scores do not migrate. Crelate has no survey or engagement object. We extract survey templates and historical responses as a structured CSV export and deliver it as part of the migration archive. Any downstream people analytics or engagement tooling the customer adopts post-migration can use this export as a seed dataset.

HiBob leave balances, entitlement history, pending requests, and approval workflows do not migrate. Crelate has no time-off or leave management capability. We export current leave balance snapshots and pending requests as a CSV file for the customer's HR team to use when setting up leave tracking in their new HR platform.

HiBob compensation bands, salary structures, and compensation history do not migrate to Crelate. Crelate is an ATS and has no compensation object. We export compensation data as a structured CSV with employee ID, effective date, compensation component, and amount for the customer's HR team to store or import into their chosen payroll or HR platform.

HiBob onboarding task templates, active onboarding states, task assignments, and completion tracking do not migrate. Crelate manages recruiting onboarding (offer letter, background check, onboarding checklist for new hires), not employee onboarding workflows within HiBob. We export active onboarding task configurations and states as a written inventory. Crelate's own onboarding checklist features can be configured by the customer's admin post-migration.

HiBob does not natively run payroll or benefits administration; it integrates with third-party providers. Neither HiBob payroll data nor Crelate supports payroll or benefits administration. We do not migrate payroll run history, tax filings, or benefits election data. Any payroll data the customer holds in HiBob or a connected payroll provider must be migrated separately through that provider's export tools.