Migrate from OnePoint HCM to Recruit CRM & ATS

OnePoint's employee records in the recruitment module contain candidate-identifying fields: name, contact information, resume or CV URL, employment history within OnePoint, and application status. We extract these as a filtered subset from the full employee export, using the Person ID as the dedupe key. Fields like social security number, date of birth, and emergency contact are withheld because Recruit CRM has no fields to receive HR-sensitive PII and we do not transfer PII to systems outside the HR domain. The customer's admin approves the field selection before extraction.

OnePoint stores assignment-level job history (job title, employer, start/end dates, supervisor) as linked records to the Person ID. These map to Recruit CRM's Work History section on the Candidate profile. Multiple assignments from the same employer are loaded as sequential entries. Assignment status codes (active, terminated, on leave) are mapped to Recruit CRM's employment status picklist.

OnePoint's internal job requisitions created in its recruitment module map to Recruit CRM Job records. The requisition title, job description, location, department, employment type, and required qualifications transfer to Recruit CRM's Job fields. OnePoint's hiring-manager assignment maps to Recruit CRM's internal user assignment. Closed or filled requisitions are migrated with status preserved.

Benefit plan enrollments, coverage tiers, carrier associations, and deduction codes are HR-specific data with no equivalent in Recruit CRM. We do not transfer benefit data to the recruitment CRM. A supplemental data dictionary is delivered documenting benefit plan names and enrollment dates for any compliance or audit purpose the customer's HR team requires.

Historical payroll runs, earnings, deductions, tax withholdings, and GL coding are not migrated because Recruit CRM has no payroll module and no fields to receive payroll data. We export payroll history as a separate file for the customer's HR or finance team to retain in their payroll system of record. We do not load payroll data into Recruit CRM even as historical reference because it creates data confusion in a recruitment context.

PTO, sick, and other leave accrual balances calculated by OnePoint's rules engine are not relevant to Recruit CRM's recruitment workflow. These records are excluded from the candidate migration. We flag the accrual data for extraction as a standalone HR export that the customer's payroll or HR admin retains.

OnePoint departments, cost centers, and locations used in the recruitment module are extracted as reference data and mapped to Recruit CRM's Department or Division fields on Job and Candidate records. The org hierarchy (reporting lines) is not migrated because Recruit CRM does not model internal org charts; it models candidate-client-job relationships only.

OnePoint user accounts linked to recruitment module access are mapped to Recruit CRM user accounts by email. Role names (HR Admin, Recruiter, Hiring Manager, Employee Self-Service) are reconciled against Recruit CRM's permission model (Admin, Standard, Read-Only). Any OnePoint user without a Recruit CRM license is placed in a reconciliation queue for the customer's admin to provision accounts.

Employee document files accessible via OnePoint's file repository, including resumes, CVs, and signed onboarding forms, are exported and attached to the corresponding Candidate record in Recruit CRM. Document type is preserved as a tag. We do not migrate benefit documents, payroll statements, or tax forms because they are outside Recruit CRM's document scope.

Performance reviews, goals, and ratings stored against the employee record in OnePoint are not migrated to Recruit CRM. These are HR assessment records with no equivalent in a recruitment CRM's data model. We deliver a written list of performance record counts per employee for the customer's HR team to retain.

Time entries, scheduling data, and shift records from OnePoint's Time & Labor module are not migrated. Recruit CRM does not model time tracking or scheduling. Accrual balances as of the migration cutoff date are extracted as a supplemental HR export for the customer's payroll team.