Migrate from OnePoint HCM to BambooHR

OnePoint's Person ID record is the central anchor for all other modules. We map the full employee profile including name, contact information, employment dates, and organizational assignment to BambooHR Employee. OnePoint's HR assignment status code maps to BambooHR's employment status field, and the original Person ID is preserved as a custom field onehcm_person_id__c for audit and reconciliation. Employees load before any dependent records (compensation, benefits, time-off) so that BambooHR's foreign key relationships are satisfied on insert.

OnePoint tracks assignment-level data including assignment type, HR status code, and system person type that may differ from BambooHR's job title and department fields. We map OnePoint assignment status codes to BambooHR employment status values (Active, Inactive, On Leave), preserving the assignment type as a custom field if no direct BambooHR equivalent exists. Manager assignments migrate as BambooHR supervisor relationships.

OnePoint stores salary, pay grades, compa ratios, and compensation change history as effective-dated rows against the employee record. We export the full compensation timeline and load current salary as BambooHR Pay Rate, with historical compensation entries preserved as custom fields compensation_effective_date__c and compensation_amount__c. Multi-component compensation plans (base plus bonus, commission, stipends) map to BambooHR custom fields because the standard Pay Rate field holds a single numeric value per employee.

OnePoint calculates PTO, sick, and other leave accruals via its rules engine and stores current balances against the employee record. We export current balances as of the migration cut-off date and load them as BambooHR Time-Off balances by type (PTO, Sick, Personal). BambooHR's accrual calculation method (granting or accrual-per-hours-worked) is configured by the customer post-migration; we document OnePoint's accrual rules and rule effective dates so that the customer's admin can replicate the configuration or switch to BambooHR's own accrual method.

Benefit plan assignments, coverage tiers, and carrier connections require mapping to BambooHR's plan library. Pre-loaded carrier forms and benefit plan configurations differ between platforms, so we export the full benefit enrollment snapshot from OnePoint (plan name, coverage tier, employee cost, employer cost, enrollment date, benefit effective date) and load it as a structured data set in BambooHR's Benefits module. BambooHR's Benefits add-on supports carrier connections for major carriers. We flag any benefit types (health, dental, vision, life, 401k) that do not map directly and package them as supplemental data for the customer's benefits admin to configure post-migration.

Time-off requests, approved hours, and accrual usage history migrate as BambooHR Time-Off entries. We export OnePoint time-off request records (request date, type, hours, status) and load them as historical time-off entries in BambooHR. BambooHR does not replicate OnePoint's time-clock integration or punch data model; if the customer used OnePoint's time-clock hardware integration, we flag the existing device model and recommend BambooHR-compatible time-clock options or a third-party integration partner.

Departments, cost centers, locations, and the org hierarchy migrate as BambooHR Departments and Locations before employee records load. We extract the full org tree from OnePoint (including any inactive departments) and map it to BambooHR's structure, preserving department codes and cost center references as custom fields. If OnePoint uses a nested department hierarchy deeper than BambooHR's flat department model, we flatten and document the original nesting for the customer's reference.

Employee document files (onboarding paperwork, signed forms, performance reviews) stored in OnePoint's employee file area migrate as BambooHR employee files. We export available documents in bulk, naming them with a consistent convention (EmployeeID_DocumentType_Date) and loading them into BambooHR's document management area for each employee. BambooHR's file storage limits apply based on the customer's plan tier.

OnePoint user accounts, manager assignments, and role-based access controls must be mapped to BambooHR user accounts. Role names and permission sets differ significantly between HCM vendors, so we export OnePoint's role structure as a written inventory and recommend a BambooHR role mapping for the customer's admin to configure post-migration. BambooHR's permission model (Employee, Manager, Admin) differs from OnePoint's more granular role definitions, so we document the delta and provide a role translation guide.

Historical payroll runs, earnings, deductions, and tax withholdings export from OnePoint as audit records or opening balances. BambooHR's optional payroll module does not replicate full payroll history from prior systems; instead, we load the most recent payroll run data (current earnings YTD, deductions YTD, tax withholdings YTD) as opening balances in BambooHR's payroll module. Full historical pay stub detail is preserved as an exported data set for the customer's payroll admin to access outside BambooHR if needed for compliance or employee inquiries.

Performance reviews, goals, and ratings stored as linked records to the employee in OnePoint export to BambooHR's Performance module. We map available performance data (review date, rating, reviewer, comments) to BambooHR performance review entries, flagging any goal structures or competency frameworks that do not have a direct BambooHR equivalent. BambooHR's performance module supports goal tracking and review cycles; we document OnePoint's goal hierarchy so that the customer's admin can rebuild it in BambooHR's goal-setting framework.