Migrate from BeyondPay to BambooHR

BeyondPay employee records map directly to BambooHR Employee. We preserve first name, last name, date of birth, hire date, termination date, job title, department, employment status, SSN, address, and emergency contact. We resolve the supervisor relationship by matching the supervisor's BeyondPay employee ID to the corresponding BambooHR employee record. Custom BeyondPay fields require a complete field inventory from the BeyondPay implementation team during discovery; each custom field is mapped to a BambooHR custom field or flagged for manual review.

Year-to-date wage totals, pay period earnings, deductions, and tax withholdings migrate as payroll summary data on the BambooHR Employee record. We chunk historical exports by calendar year and load prior-year data before activating any current-year payroll run in BambooHR. Running a payroll in BambooHR before loading historical data creates duplicate wage records that require correction before year-end W-2 filing. The source BeyondPay implementation team must deliver the export segmented by calendar year for this to succeed.

Federal EIN, filing status, tax rate tables, and FUTA configuration from BeyondPay translate to BambooHR's federal tax settings. We verify the federal EIN matches between systems before loading state-level data. BambooHR's payroll add-on handles federal tax calculation natively; we configure the tax tables based on the sourced values.

NJ and PA state tax codes, rates, filing statuses, and state unemployment insurance rates configured in BeyondPay map to BambooHR state tax settings. BeyondPay's state-specific configurations are translated to BambooHR's tax table format during transformation. Any state outside BeyondPay's standard NJ/PA coverage is flagged if the customer has employees in other states, as BambooHR requires manual state configuration for non-standard jurisdictions.

Bank routing numbers and account numbers for employee direct deposit migrate as encrypted payment information to BambooHR's Payment Information fields. We flag any employees with multiple split deposits (routing to two or more bank accounts) for manual verification before loading, as split deposit configurations vary between payroll systems and must be confirmed with the customer's bank setup.

Health, dental, vision, and retirement benefit elections and coverage levels migrate as current-state benefit snapshots in BambooHR. We map BeyondPay's benefit carrier names, plan names, coverage tiers (employee, employee plus spouse, family), and contribution amounts to BambooHR's Benefits module. Historical benefit election changes and effective-dated transitions are not carried forward; only active election snapshots at migration time transfer.

PTO and leave accrual balances transfer to BambooHR's Time-Off module. We verify whether BeyondPay tracks PTO and leave accruals separately from standard payroll processing, as not all payroll platforms expose accrual data via export. Accrual rates, carryover rules, and policy names map to BambooHR Time-Off policies. If BeyondPay does not export accrual balances separately, we recommend loading current balances as an initial seed and letting BambooHR's accrual tracking take over from the go-live date.

Court-ordered garnishments, voluntary deductions, and HSA or FSA contributions migrate as active deduction records in BambooHR. We flag inactive garnishments separately and confirm the destination system supports the specific garnishment type (wage garnishment, child support, tax levy, bankruptcy). Deduction amounts and frequency (per pay period, flat amount, percentage) translate directly to BambooHR deduction configuration.

WC class codes, rates, and carrier information configured in BeyondPay map to BambooHR's Workers Compensation settings. We verify that class code tables match between systems, as mismatches can cause audit findings during annual WC reporting. State-specific WC configurations for NJ and PA transfer with the class code, rate per $100 of payroll, and carrier name.

Hourly employee time entries, overtime calculations, and accrual balances migrate as time tracking records if BeyondPay maintains time data separately from payroll. We flag whether BeyondPay tracks time-off accruals independently and map accordingly. BambooHR's Time Tracking module receives the data; any Punch Clock integration configuration must be rebuilt in BambooHR post-migration as integration settings do not migrate.

BeyondPay custom fields configured per client lack a public schema and must be inventoried via the BeyondPay implementation team. Each custom field is mapped to an equivalent BambooHR custom field (text, number, date, dropdown, or checkbox type) during transformation. Fields without a clear BambooHR equivalent are flagged for customer review and either mapped to a custom field or excluded from the initial migration scope.

BeyondPay does not expose a documented report export or template API. Custom report definitions, scheduled reports, and saved report configurations cannot be migrated programmatically. We deliver a written inventory of all BeyondPay reports as a reference for BambooHR rebuild. BambooHR's report builder and template library provide the replacement capability; the customer's HR admin rebuilds reports post-migration.