Migrate your OnePoint HCM data

Employees are the central record in OnePoint's single-database architecture. Every other object (payroll, benefits, time, performance) links back to this record via a shared Person ID. We migrate the full employee profile including demographics, employment status, and job history as the anchor for all dependent objects.

OnePoint tracks assignment-level data including assignment type, HR assignment status code, and system person type. These statuses may differ between source and destination systems, so we map them explicitly and flag any effective-dated assignment changes that require multi-row inserts in the target platform.

Salary, pay grades, compa ratios, and compensation change history are stored as effective-dated rows against the employee record. We preserve the full compensation timeline, including historical entries needed for payroll audit trails or benefits eligibility recalculation.

Benefit plan assignments, coverage tiers, and carrier connections require mapping to the destination's plan library. Pre-loaded carrier forms and benefit plan configurations differ between platforms, so we map enrolled plans to equivalent target offerings and flag any plan elections that cannot be auto-matched.

Time entries, accrual balances, and scheduling data are deeply integrated with OnePoint's rules engine. We extract punch data, time-off requests, and accrual balances as a bundle, mapping them to the destination's corresponding time module and handling any timezone or rounding differences.

PTO, sick, and other leave accrual balances are calculated by OnePoint's rules engine and stored against the employee record. We export current balances as of the migration cut-off date and apply them as opening balances in the destination system, preserving any in-flight pending requests separately.

Employee document files (onboarding paperwork, signed forms, performance reviews) are stored in the employee file and accessible for download in the OnePoint UI. We export available documents and map them to the destination's document management structure, noting any file size or format restrictions.

Departments, cost centers, locations, and the org hierarchy are migrated as reference data before employee records load. We extract the full org tree and map it to the destination's structure, preserving any manager-report relationships embedded in the hierarchy.

User accounts, manager assignments, and role-based access controls must be mapped between OnePoint and the destination platform. Role names and permission sets differ significantly across HCM vendors, so we create a role mapping matrix during scoping and apply it at migration time.

Historical payroll runs, earnings, deductions, and tax withholdings are migrated as audit records or opening balances depending on the destination's payroll initialization approach. OnePoint's payroll export includes labor distribution and GL coding, which we preserve for downstream accounting reconciliation.

Performance reviews, goals, and ratings are stored as linked records to the employee. We extract available performance data and map it to the destination's performance module structure, flagging any custom review templates or rating scales that require manual reconfiguration.