Migrate from HROne to Recruit CRM & ATS

HROne Employee records map to Recruit CRM Candidate profiles. Core fields (full name, email, phone, employment type, department) transfer directly. HROne employee status (active, resigned, on hold) maps to Candidate status in Recruit CRM. HROne custom fields on the Employee object are discovered during the manual custom-field step and mapped to Recruit CRM custom fields on the Candidate record. HROne does not have a separate Candidate object; employee records being considered for external roles become Candidates in Recruit CRM.

HROne job postings (available on Professional and Enterprise tiers) map to Recruit CRM Job records. Fields include job title, department, location, employment type, and job description. HROne applicant status values map to Recruit CRM pipeline stages. HROne job postings without applicants migrate as open Jobs; HROne applicants in the pipeline migrate as Candidate applications linked to the Job.

HROne applicant records (candidates tied to job postings) map to Recruit CRM Candidate records with an active Application linked to the corresponding Job. Applicant status, interview scores, and recruiter notes from HROne migrate to the Candidate profile and application notes in Recruit CRM. Custom fields capturing applicant-specific data (source, referral, screening scores) map to Candidate custom fields.

HROne departments, cost centers, and the reporting hierarchy map to Recruit CRM department tags and optionally to Company department records. Manager relationships from HROne's org chart are preserved as a custom field on the Candidate record (reporting_to__c) or as a note, since Recruit CRM does not have a native org hierarchy object. Department-level cost centers do not migrate as these are payroll and finance concepts not represented in Recruit CRM.

HROne salary structures, pay components, and compensation histories have no native Recruit CRM equivalent. We migrate the most recent compensation record as Candidate custom fields (current_ctc__c, currency__c, pay_frequency__c) and archive the full compensation history in a JSON blob in a long-text custom field (compensation_history__c) or in a separate spreadsheet delivered alongside the migration. Compensation data is marked as sensitive and handled under the data processing agreement.

HROne clock-in/out logs, shift assignments, and overtime records have no equivalent in Recruit CRM. For recruitment contexts where attendance data is relevant (for example, reference checks or behavioral screening), we migrate the last 90 days of attendance summary as custom fields on the Candidate record (attendance_rate__c, late_days_90d__c). Full attendance logs are excluded or delivered as a separate export file. Timezone normalization is applied during extraction per HROne's documented timezone issue.

HROne leave entitlements, accrual policies, and current balances are HR-specific records with no Recruit CRM analog. Leave data is excluded from the Recruit CRM migration scope. If the customer requires leave records for onboarding or compliance purposes, we deliver a separate leave summary export and advise that Recruit CRM does not natively support leave management.

HROne employee documents (offer letters, contracts, ID proofs) migrate as attachments on the corresponding Candidate record in Recruit CRM. Document type metadata from HROne (offer_letter, contract, id_proof) maps to the attachment name prefix in Recruit CRM. File binaries are extracted from HROne exports and uploaded as candidate attachments via the Recruit CRM API. Documents without a valid candidate match are held in a reconciliation queue.

HROne goals, appraisal cycles, and review ratings are excluded from the Recruit CRM migration. Recruit CRM does not have a native performance appraisal module. We deliver a written summary of appraisal dates and ratings per employee as a reference document for the customer's HR team to maintain separately or import to a dedicated performance management tool.

HROne instance-specific custom fields on Employee, Job, and Application objects are discovered via the manual custom-field step (comparing UI export against API export). Each discovered custom field is mapped to a Recruit CRM custom field of equivalent type (text, number, date, picklist). If a HROne custom field has no Recruit CRM equivalent, it is either created as a new custom field during migration setup or flagged for the admin to handle post-migration. Custom field values that reference HROne-specific picklist options are translated to Recruit CRM-compatible picklist values.

HROne Employee records have an owner (assigned HR admin or recruiter). These map to Recruit CRM users who will own the corresponding candidate or job records. We match by email and flag any HROne owner without a Recruit CRM user account for the admin to provision before the candidate migration phase.

Organizations using HROne's client-facing recruitment module (if present on their tier) may have client company records. These map to Recruit CRM Company records, preserving company name, contact, location, and any custom fields. If HROne does not have an explicit client company object, we extract companies referenced in job postings or applicant source fields and create Company records in Recruit CRM during migration.