Migrate from HiBob HRIS to Recruit CRM & ATS

HiBob People records do not map directly to Recruit CRM Candidates because the data model semantics differ — HiBob employees have employment history, compensation, and HR status, while Recruit CRM Candidates represent applicants in a hiring pipeline. We map active HiBob employees to Candidates only if the customer intends to use Recruit CRM as an internal ATS for future hiring. We flag terminated or offboarded employees as archived records outside Recruit CRM's scope. First name, last name, email, phone, location, and job title migrate as standard Candidate fields; employment status and start date become custom fields if the customer requires them in Recruit CRM.

HiBob Job Catalog positions and job family profiles map to Recruit CRM Job Orders. The job title, job family, job family group, and any budget or headcount data on the Position object migrate as Job Order fields. HiBob's Position to Employee linkage does not transfer — Recruit CRM's Job Order tracks open requisitions and placements, not current staffing levels. We extract Position records via the Bob Workforce Planning API and map them to open Job Orders in Recruit CRM, creating one Job Order per distinct active position.

HiBob time-off balances and leave history have no equivalent in Recruit CRM. Recruit CRM is an ATS and recruitment CRM — it does not track employee PTO, sick leave, or leave approvals. We export time-off balance snapshots and pending leave requests as CSV exports for the customer's HR team to retain outside Recruit CRM. Leave history is documented in the migration inventory but does not import into the destination platform.

HiBob custom fields on the Employee object (list-type and text fields) map to custom Candidate and Job Order fields in Recruit CRM. HiBob list-type custom fields return internal string IDs rather than display labels — we resolve these via HiBob's list metadata endpoint before mapping to Recruit CRM picklist or multi-select fields. Custom field transformation requires a field-by-field review during scoping because field type compatibility between HRIS custom fields and ATS custom fields is not guaranteed.

HiBob employee documents (offer letters, contracts, identification, performance reviews stored in Bob Docs) migrate as attachments on the corresponding Candidate record in Recruit CRM. HiBob exposes document metadata via API; binary files require a separate download step. We extract document metadata alongside employee records and attach files to Candidates during import. Document naming conventions from HiBob are preserved in the file name so the customer's team can verify provenance.

HiBob performance review cycles, one-on-one records, ratings, goals, and Key Results do not have equivalents in Recruit CRM. Recruit CRM does not include a performance management module. We export PDR records and goal hierarchies as CSV and JSON for the customer's HR team to archive or import into a dedicated performance management platform. Goals and OKR data are outside Recruit CRM's data model and are flagged as requiring a separate system post-migration.

HiBob engagement survey templates and historical response data do not map to Recruit CRM. Recruit CRM does not have an engagement survey feature. We export survey templates and aggregated engagement scores as a written inventory. Survey response history and engagement metrics are preserved in CSV for the customer's HR team to archive.

HiBob onboarding workflow templates and active onboarding task states do not transfer to Recruit CRM. Recruit CRM has limited candidate onboarding task functionality scoped to new-hire onboarding within the hiring process, not the full HR onboarding flow that HiBob manages (document signing, IT provisioning, first-day checklists). We export onboarding flow configurations as a written map for the customer's admin to configure as candidate tasks in Recruit CRM.

HiBob's org chart derives from employee reporting relationships and does not map directly to Recruit CRM's Client or Company objects, which represent external recruitment clients and client organizations in an agency context. We extract reporting line data as a CSV for the customer's HR team if org chart preservation is required in a separate org chart tool. Internal company structure is not a Recruit CRM object.

HiBob compensation bands, salary structures, and compensation history on the Employee object migrate to custom fields on the Candidate record in Recruit CRM only if the customer explicitly requires this for placement or offer tracking. HiBob compensation data is HR-sensitive and may require anonymization before migration depending on the customer's data governance policy. Salary expectations, offer amounts, and placement fees are more relevant in Recruit CRM's placement workflow than historical employee compensation.