Migrate from Namely to BambooHR

Namely employee profiles (demographics, employment status, job title, department, hire date, work location, manager reporting line) map directly to BambooHR Employee records. We preserve the employment start date as hire_date and termination date if applicable. Custom employee properties in Namely (e.g., shirt size, emergency contact fields) migrate as BambooHR custom fields discovered via API before migration. The mapping type is 1:1 for the core record; extended properties require custom field provisioning in BambooHR first.

Namely salary history, bonus amounts, and compensation effective-dates migrate to BambooHR Pay Rate fields and custom historical compensation fields. Each effective-date change in Namely becomes a compensation timeline entry at the destination. BambooHR Pay Rate supports a single current pay rate; historical compensation beyond the current rate is stored in a custom multi-row table or note if the customer's plan includes the Compensation module (Elite tier). We flag whether the destination plan includes compensation tracking before importing historical data.

Namely benefit elections (health, dental, vision, 401k, FSA, HSA) are extracted as enrollment records tied to plan years and enrollment periods. We flag upfront that Namely plan IDs are carrier-specific and have no direct equivalent at BambooHR. The customer must configure equivalent benefit plans in BambooHR's Benefits Tracking module before employee enrollments can be applied. We extract enrollment data in a carrier-neutral format (election type, coverage level, contribution amounts) that maps to the new plan structure. PEO tier migrations require full carrier re-enrollment under the customer's own EIN.

Namely payroll runs (earnings, deductions, taxes, direct deposit details, YTD gross and net pay) are exportable. We preserve year-to-date earnings and deduction totals per employee per payroll period. BambooHR Payroll is a separate add-on product; if the customer does not license BambooHR Payroll, payroll history migrates as historical records for reference only and does not interface with BambooHR's payroll engine. We confirm the payroll add-on decision during scoping.

Namely PTO, sick leave, and accrual balances migrate to BambooHR's Time-Off Management module. For accrual-based policies, we export current balances and accrual histories. For unlimited PTO policies, there is no balance record to export because Namely does not track balances under unlimited plans. We confirm the PTO policy type during discovery, flag unlimited policies in the scope, and recommend exporting a policy summary document as a placeholder rather than a data import. BambooHR's unlimited PTO tracking requires manual balance entry or custom accrual configuration.

Namely employee documents (offer letters, I-9s, tax forms, contracts) export as binary files from the Documents module. Namely file naming conventions are inconsistent (e.g., 'Smith_Joe_I9.pdf' vs 'I-9_Smith.pdf'). We normalize document naming during extraction using employee ID plus document type conventions to ensure clean imports into BambooHR's employee file structure. Document metadata (upload date, uploader) is preserved as a JSON sidecar. BambooHR's file attachment limits and e-signature workflow for new hire documents are separate configuration items.

Namely departments, cost centers, reporting hierarchies, and org chart data map to BambooHR Departments and Locations. We extract the full org hierarchy and reconstruct it as BambooHR department records with the reporting manager relationship resolved via employee ID lookup. Custom org-level fields in Namely require field-level mapping to BambooHR custom fields on the Employee record. Multi-location companies should configure Locations in BambooHR during setup, as this affects time-off calendars and compliance jurisdiction fields.

Namely performance ratings, review cycle data, goals, and feedback migrate to BambooHR's Performance Management module (available on Pro and Elite tiers). Review templates and historical ratings export cleanly; we map the source rating scale to BambooHR's configurable rating scale. Custom rating scales used in Namely may not map 1:1 to BambooHR's scale values and are flagged for the customer's HR admin to remap post-migration. We confirm the destination BambooHR plan tier during scoping to ensure Performance Management is licensed before importing.

Namely custom properties on employee records migrate to BambooHR custom fields. We discover all active custom field definitions via the Namely API before migration, identify their data types (text, date, dropdown, checkbox, number), and map them to equivalent BambooHR field types. Multi-select picklists in Namely may require mapping to a BambooHR custom dropdown with pre-defined options. Custom field ordering within the BambooHR employee tab is configurable post-import.

Namely workflow configurations, approval chains, and automation rules are not structurally portable to BambooHR. The two platforms use different workflow models (Namely's rule-based approval workflows vs BambooHR's built-in workflow templates for time-off requests and employee data updates). We do not migrate workflows as code. We deliver a written inventory of every active Namely workflow with its trigger conditions, approvers, and actions for the customer's HR admin to rebuild using BambooHR's workflow tools. This inventory is part of the standard migration deliverable.