Migrate from HR-ON to Recruit CRM & ATS

HR-ON Employee records map to Recruit CRM Candidate records. Standard employee properties (firstName, lastName, email, phone, hireDate, department) map to Candidate's corresponding fields. HR-ON's systemFields containing organizational metadata (department, manager, location) are parsed and stored in Candidate custom fields for reference. We use HR-ON's POST /v1/staff/employees endpoint with JWT auth to retrieve records individually and resolve any existing candidate records in Recruit CRM by email deduplication before insert.

HR-ON custom properties on Employee records that lack a standard Candidate field equivalent map to Recruit CRM's custom fields on the Candidate object. We extract all non-systemFields from HR-ON, validate data types (text, number, date, single-select map cleanly; multi-select requires configuration in Recruit CRM), and flag any with incompatible formats. The customer's admin reviews the custom field schema in Recruit CRM before migration to confirm field creation and data type assignment.

HR-ON stores department and organizational hierarchy metadata within systemFields on Employee records rather than as separate objects. We extract these values, deduplicate departments into Company or Client records in Recruit CRM, and link each Candidate to their employing Client. If HR-ON tracks multiple employers or organizational units, we create separate Client records and resolve the Candidate-to-Client relationship at migration time using the department field as the linking key.

HR-ON document templates with name, description, documentType, dateFormat, and language (da_DK, en_US) are exported as metadata associations rather than migrated as functional templates. Recruit CRM stores candidate documents as file attachments linked to the Candidate record. We export each document's template name, language, and dateFormat as metadata fields on the attachment record and flag the customer for manual relinking of any document types that require template recreation in Recruit CRM's document generation tool.

HR-ON user accounts map to Recruit CRM User records for team members who will access the recruitment platform. Role and permission structures differ between HR-ON and Recruit CRM; HR-ON role definitions do not map directly to Recruit CRM's permission model. We extract user email, name, and status, and flag the customer to configure Recruit CRM User roles and access levels post-migration based on their recruitment team structure.

HR-ON stores language preference at da_DK (Danish) and en_US (English) per template and employee. We carry these through to a Candidate custom field (preferred_language__c) in Recruit CRM to preserve locale context for candidate communications, job board postings, and localized email templates. This is especially relevant for organizations migrating from Danish-market HR-ON to Recruit CRM for English-language or multi-language recruitment.

HR-ON stores dates in four distinct formats depending on locale and template settings: DD-MM-YYYY, DD/MM/YYYY, YYYY-MM-DD, or written form (July 20, 2021). We parse and normalize all date values to ISO 8601 during extraction and validate against Recruit CRM's expected date field formats before loading. This includes hireDate, startDate, documentDate, and any custom date fields on Employee records.

HR-ON does not have a native Job or Position object; however, if HR-ON tracks open roles or requisitions within employee systemFields or related records, we extract these as Candidate-to-Job associations in Recruit CRM. For organizations using HR-ON for internal hiring alongside employee management, we reconstruct the hiring pipeline as Recruit CRM Job records linked to Candidates in relevant pipeline stages.

If HR-ON stores engagement history (onboarding tasks, document completion events, status updates) on Employee records, we extract these as Activity records or Notes attached to the corresponding Candidate in Recruit CRM. HR-ON's engagement scope is narrower than a full CRM activity timeline; we map onboarding milestones and document events to Candidate Notes for audit continuity.

Recruit CRM distinguishes between Clients (organizations the agency places candidates with or serves) and Candidates (job seekers). HR-ON has no equivalent to the Client object. We create Client records during migration based on HR-ON department and organizational unit data, or leave Client creation for the customer's admin to configure post-migration if their use case involves external clients rather than internal organizational units.

Recruit CRM's recruitment pipeline (Applied, Screening, Interview, Offer, Hired, Rejected) has no direct HR-ON equivalent because HR-ON does not manage candidate hiring pipelines. We configure a default pipeline structure in Recruit CRM during migration setup, with the customer's admin defining custom stages that reflect their recruitment process. The pipeline configuration is delivered as a written specification for admin setup.