Migrate from OnePoint HCM to Crelate

OnePoint Employee records (Person ID anchored) map to Crelate Contact records for internal employees and Candidate records for external talent in the pipeline. Name, email, phone, address, hire date, termination date, and employment status transfer as standard Crelate fields. We apply a contact_type discriminator (Employee vs Candidate) based on the employee's current employment status in OnePoint. Active employees map as Contacts; separated employees with rehiring potential map as Candidates with a last_role_custom field carrying the former job title.

OnePoint employment assignment data (assignment type, HR assignment status code, system person type, job code, FLSA status, full-time/part-time indicator) has no native Crelate object equivalent. We extract assignment records per employee, flatten the active assignment into a set of custom fields on the Contact record (assignment_type__c, hr_status_code__c, job_code__c, flsa_status__c, employment_class__c), and package historical assignment records as a supplemental JSON data dictionary attached to the Contact. Crelate supports Text, Number (Integer), Number (Decimal), Number (Money), and advanced Logical Name custom fields for API access.

OnePoint Departments, Cost Centers, and Locations extract as a hierarchical reference table and map to Crelate Company records with a parent_company_id lookup to represent the org tree. We preserve the full hierarchy depth so that Crelate's filtering by company hierarchy works for reporting and candidate-to-hiring-manager assignment. Cost center codes map as a custom field on the Company record for integration with any downstream payroll system that receives cost center data from Crelate's ATS exports.

Employee documents (onboarding paperwork, signed I-9s, performance review files, offer letters) stored in OnePoint's employee file section export as downloadable files and attach to the corresponding Crelate Contact record via the Crelate file attachment mechanism. We preserve the original filename and document type classification. Crelate's document attachment supports multiple files per Contact. Large document bundles (thousands of files) require chunked import with batch size management to avoid timeout during the file attachment phase.

OnePoint compensation records (salary, pay grades, compa ratios, effective-dated compensation change history) have no native Crelate ATS field. We extract the full compensation timeline per employee and package it as a structured supplemental JSON export (compensation_history.json) attached to the Contact record or delivered as a separate data export. The customer's payroll or HR admin uses this export to initialize compensation data in the destination payroll platform. We do not load compensation records into Crelate because doing so would create data that Crelate's ATS workflows cannot act on.

OnePoint benefit plan assignments, coverage tiers, carrier connections, and enrollment effective dates do not map to any Crelate object. We extract the current benefits enrollment snapshot per employee and deliver it as a supplemental data export (benefits_snapshot.json) with plan name, tier, carrier, and enrollment date fields. The customer's HR admin reconciles this with their benefits administration platform (Ef Benefits, Benefitfocus, Employee Navigator) post-migration. We do not load benefits data into Crelate because it falls outside the ATS data model.

Time entries, accrual balances, scheduling data, and time-off requests stored in OnePoint's Time and Labor module do not transfer to Crelate. Crelate is an ATS and recruiting CRM; it has no time tracking or scheduling module. We extract a final accrual balance snapshot as of the migration cut-off date and package it as a supplemental export (accrual_snapshot.json) for the customer's payroll team. We do not migrate historical time punches or scheduling rules.

Historical payroll runs, earnings, deductions, and tax withholdings stored in OnePoint's payroll module have no Crelate equivalent. We extract the last 12 months of payroll summary data (total earnings, total deductions, net pay by period) per employee and deliver it as a supplemental export (payroll_summary.json) for the customer's finance or payroll team to load into the destination payroll platform. We do not migrate detailed payroll line items into Crelate.

OnePoint performance reviews, goal ratings, and performance review scores map to custom fields on the Crelate Contact record if the customer wants the data visible within Crelate's candidate record (useful for internal mobility scenarios). The most recent performance rating becomes performance_rating__c (Number, Integer). Full performance history goes to supplemental data package (performance_history.json) for HR file purposes. We flag any performance data that includes legally sensitive information requiring jurisdiction-aware handling.

OnePoint user accounts, manager assignments, and role-based access controls (HR Admin, Payroll Admin, Employee, Manager roles) map as a reconciliation inventory only. Crelate manages its own user accounts and permission sets independently. We extract the OnePoint role matrix and deliver it as a user_role_matrix.csv so the customer's Crelate admin can provision equivalent access in Crelate's settings. User-to-contact linking (which Crelate Contact corresponds to which Crelate User) is resolved during the Contact migration.

If OnePoint ATS job requisitions are in use (OnePoint's built-in recruiting module with Indeed and job board distribution), these map to Crelate Job Order records. Requisition title, department, location, employment type, and job description transfer. OnePoint's requisition status workflow maps to Crelate Job Order status values (Open, On Hold, Filled, Cancelled). Active job boards and posting URLs migrate as a custom field or note on the Job Order for re-posting setup in Crelate.

OnePoint ACA reporting data (1094/1095 form records, tax codes, deduction codes, exemption statuses) and compliance-adjacent fields do not map to any Crelate object. We extract ACA historical records and compliance-relevant fields and package them as a jurisdiction-tagged supplemental export (aca_compliance_export.json) with state and federal jurisdiction flags. The customer's compliance team or benefits broker handles ACA recordkeeping post-migration. We do not load compliance data into Crelate's ATS environment.