Migrate from HROne to Crelate

HROne Employee records map to Crelate Candidate. Name, email, phone, department, employment type, status, hire date, and manager relationship transfer as standard Candidate fields. Compensation summary (current salary, pay frequency, currency) migrates to custom fields on the Candidate record since Crelate Candidate has no native compensation object. We flag every HROne custom field discovered during API profiling and add a corresponding custom field in Crelate under Settings | Core Records | Contacts before import begins.

HROne employees who represent client companies or hiring managers map to Crelate Contact records. The employee name becomes the Contact name; their HROne email becomes the Contact email; their department becomes a custom field. Contact type (internal vs external) is set based on whether the employee's organization matches the Crelate destination company's organization.

HROne departments and cost centers map to Crelate Company records when they represent business entities or client organizations. Internal departments without a client counterpart become custom picklist values on Candidate records. We preserve the reporting hierarchy (manager-employee relationships) as manager lookup fields on Candidate during import.

HROne job postings (available on Professional and Enterprise tiers) map to Crelate Job records. Job title, department, location, employment type, and posting status transfer directly. Applicant status pipeline stages from HROne map to Crelate Candidate Job Activities with status values normalized to Crelate's stage model. Open date and close date map to Job startDate and endDate fields.

HROne applicant records attached to job openings map to Crelate Candidate records linked to the corresponding Crelate Job via Candidate Job Activity records. Application status, submission date, source (referral, job board, direct), and any interview stage ratings transfer as Candidate Job Activity fields. Custom recruiter fields from HROne migrate to custom fields on the Candidate Job Activity in Crelate.

HROne compensation records (salary components, pay frequency, allowances, effective dates) aggregate by employee into a compensation summary that migrates to custom fields on the Crelate Candidate record. Pay frequency and currency normalize to single values; component breakdowns (basic, HRA, transport, bonus) flatten into text or numeric custom fields. Compensation history with multiple effective-date records merges into the most recent active compensation snapshot plus a notes field carrying the history summary.

HROne employee documents (offer letters, employment contracts, ID proofs) export as file binaries with metadata. We extract the file and map it as a Crelate Candidate document attachment. Crelate supports document uploads on candidate records with file type, language, and custom tags. We match document type from HROne (offer letter, contract, ID proof) to the appropriate Crelate document category during import.

HROne appraisal cycles, goals, ratings, and reviewer assignments have no native Crelate equivalent. We carry the most recent appraisal rating, review date, and reviewer name as custom fields on the Crelate Candidate record. Detailed goal lists and multi-cycle appraisal history flag as a data-gap item in the migration inventory: these require either a custom object in Crelate (provisioned during migration) or a manual handoff document for the customer's admin.

HROne engagement logs — calls, emails, meetings, and tasks — attached to employee or applicant records map to Crelate Activity records linked to the corresponding Candidate or Contact. Activity type, date, subject, notes, and outcome disposition transfer directly. Crelate's Activity Forms feature (screener questions, interview prep) is configured during migration but existing form responses migrate as Activity notes rather than structured data.

HROne leave balances (entitled, accrued, used, pending) have no native equivalent in Crelate's ATS model. We carry the most recent leave balance snapshot as custom fields on the Crelate Candidate record (leave_type, balance, accrued_to_date). Leave approval workflows do not migrate; we document each HROne leave workflow for the customer's admin to rebuild in Crelate or retain in a separate HRMS. Leave data is flagged as a data-gap risk if the customer needs it for payroll or compliance purposes.

HROne clock-in/out logs, shift assignments, and overtime records have no Crelate equivalent. Crelate is an ATS, not an attendance system. We do not migrate attendance data into Crelate. Instead, we deliver a written record of the attendance data schema from HROne's export for the customer's admin to evaluate: if payroll processing continues in HROne or moves to a separate payroll system, attendance data should remain there. If attendance records are needed for compliance or HR audits, we recommend a separate export and storage solution.

HROne custom fields are instance-specific and may not appear in the API export. We perform a dual-profiling step: extract a sample employee record from HROne's UI export alongside the API export, compare field counts, and flag any discrepancy as a manual custom field to be added in Crelate under Settings | Core Records | Customize Fields before migration begins. Crelate supports Short Answer, Long Answer, Date, Numeric, Picklist, and multi-select custom field types. We match HROne field types to Crelate equivalents during schema design.