Migrate from PrimePay to BambooHR

PrimePay Employee records carry personal details, employment type, hire date, and status. We migrate these to BambooHR Employee records with standard field mapping for name, contact info, employment status, and hire date. Any custom employee properties map to BambooHR custom fields which we pre-create during schema design. The original_hire_date field in BambooHR captures the hire date without modification from subsequent job changes.

PrimePay's patented Position Management stores job title, salary, reporting line, and security permissions as a separate record type from the Employee. BambooHR has no native Position object; job context lives in the Employee's Job Info tab. During scoping, we present two options: merge Position fields into BambooHR Employee Job Info fields (suitable if historical position tracking is not required), or create a custom Position object in BambooHR and store the full position timeline as linked records (suitable if the customer needs audit-grade historical reporting on job changes). The customer's choice drives the destination schema design before migration begins.

PrimePay payroll records include wages, taxes, deductions, garnishments, and net pay per pay period. We extract payroll history in weekly batches to manage volume for clients with high-frequency payroll, and validate total record counts during scoping before committing to a timeline. BambooHR Payroll is a separate product and may not be in every customer's contract; we map historical payroll to a custom field set in the Employee record or a custom PayrollHistory object depending on the customer's BambooHR edition and reporting needs. Tax filing records and garnishment administration configurations do not migrate and require separate tax counsel reconfiguration.

Clock-ins, shift records, and leave entries from PrimePay map to BambooHR's Time Off and Time Tracking modules. Time-off requests and accrual balances migrate as-is. Approval workflow states from PrimePay (pending, approved, rejected) do not transfer because BambooHR manages approvals differently; we note the last-known state as a balance snapshot and advise the customer's admin to reset approval queues as needed before go-live.

PrimePay org structure, departments, and cost centers migrate directly to BambooHR Departments. PrimePay's hierarchical org chart replicates as a nested Department structure in BambooHR. We validate department assignments on Employee records during reconciliation to ensure no orphaned departments after migration.

Accrual policy configurations and current balance snapshots migrate from PrimePay to BambooHR Time Off. We extract the policy rules (accrual rate, carryover limits, rollover expiration) and the live balance per employee. Carryover rules from PrimePay do not always map 1:1 to BambooHR's carryover settings because the two systems handle rollover differently; we document the discrepancy in the policy mapping sheet and advise the customer to validate carryover logic after migration.

Employee documents including offer letters, employment contracts, and tax forms migrate from PrimePay where the file content is accessible via export. We migrate file references and document content where the export SOW includes document attachment access. Some document types — particularly those requiring wet signatures or notarized forms — may require manual re-upload; we flag these by document category in the migration manifest delivered before cutover.

Active onboarding task states and I-9 verification status migrate from PrimePay to BambooHR Onboarding. BambooHR Onboarding uses a task-based workflow with a New Hire Checklist. We map the active task states from PrimePay to the corresponding BambooHR checklist items. Completed onboarding history generally cannot be reconstructed in BambooHR; we deliver a summary of onboarding completion status as of the migration date and advise the admin to reset or reconfigure the onboarding template post-migration.

PrimePay's time-relational infrastructure stores effective-dated job-title changes and compensation adjustments as a chronological sequence. BambooHR natively stores current compensation only, with no built-in compensation history timeline. We extract the full effective-date sequence per employee from PrimePay and store it as a custom text field on the BambooHR Employee record, or as a custom CompensationHistory object if the customer's reporting requirements demand it. This ensures the historical audit trail is preserved even if BambooHR's UI shows only the current compensation.

Benefit plan assignments, coverage tiers, and per-pay-period deduction amounts migrate from PrimePay as current enrollment snapshots mapped to BambooHR Benefits. BambooHR Benefits manages benefit plan configuration and enrollment tracking; plan setup itself requires manual configuration by the customer or their benefits broker post-migration. We deliver the active enrollment data as a mapped import ready to load once the benefit plan configuration is in place.