Migrate from EPAY HCM to BambooHR

EPAY Employee records (personal info, employment history, job titles, departments, locations, hire dates, termination dates) map directly to BambooHR Employee. We use BambooHR's GET /v1/employees/directory endpoint for the initial export and resolve custom fields via GET /v1/meta/fields per the BambooHR field-request model. BambooHR does not paginate the employee list — all employees return in a single response, so large workforces require chunked processing in the transformation layer. Employment status (active, inactive, terminated) maps from EPAY's employmentHistoryStatus to BambooHR's status field.

EPAY's pay rate, salary history, pay frequency, bonus payments, and effective-dated compensation changes map to BambooHR's payRate, payType, payPeriod, and effectiveDate fields. BambooHR supports one active compensation record at a time per employee; we handle EPAY's historical compensation timeline by creating a sequence of compensation records with effectiveDate stamps during the migration. Bonuses and one-time payments migrate as separate entries in BambooHR's payRate where the payType indicates bonus or supplemental pay. Note that BambooHR does not support complex multi-component compensation structures (such as market-indexed pay or graduated commission tiers) in native fields.

EPAY benefit plan assignments, coverage tiers, enrollment dates, and dependent information map to BambooHR's Benefits module. Plan names, carrier information, and coverage level (employee, employee-plus-spouse, family) migrate as structured benefit records. However, many insurance carriers require employees to re-enroll directly through the carrier portal or BambooHR's carrier integration after migration. We export the full enrollment dataset as supporting documentation and map it to BambooHR's benefits module, but advise budgeting for a two-to-four week parallel re-enrollment window with each benefits vendor before the first BambooHR payroll run.

EPAY's clock-in/clock-out data, overtime records, accrual balances, and scheduling rules represent a data volume that BambooHR does not natively store or display. We map active accrual balances (PTO, sick leave, holiday hours) to BambooHR Time Off policies as opening balances, enabling employees to continue using accrued time after cutover. Historical punch-level data (clock events, break times, overtime hours) does not have a destination equivalent in BambooHR and is exported as a CSV archive for the customer's records. Scheduling rules and shift configurations do not migrate; we document the active schedule structures for the customer's admin to reconfigure in BambooHR's scheduling module or a dedicated scheduling tool.

EPAY job costing features (cost center assignments, project code allocations, department-level labor budgeting) have no native equivalent in BambooHR's object model. We export the active cost center and project code assignments per employee as a reference CSV, map them to a custom multi-select picklist field in BambooHR (configured during migration), and flag that BambooHR does not support labor allocation reporting or job costing rollups. Customers relying on EPAY's job costing for billing, project tracking, or cost accounting must retain access to EPAY's reporting for these functions or implement a third-party labor allocation tool post-migration.

EPAY payroll run records (earnings, deductions, taxes, net pay by pay period) do not migrate into BambooHR as historical payroll records because BambooHR stores payroll data differently depending on the tier and does not maintain a full payroll run history accessible as an importable object. We export the most recent twelve months of payroll summaries per employee as a structured CSV archive and map year-to-date earnings and tax withholding totals to BambooHR's payRate and custom year-to-date fields for payroll processing continuity. Tax filing history and historical W-2 data remain in EPAY for lookback purposes.

EPAY court-ordered garnishments, wage deductions, and voluntary deduction codes with current balances have no BambooHR equivalent object. Active garnishment orders require manual re-entry in BambooHR's payroll module (if payroll is subscribed) or in the customer's payroll provider's system before the first post-migration payroll run. We export the current deduction codes, deduction types, percentage or fixed amounts, and remaining balances as a structured handoff document. This is one of the highest-risk migration items: missed or incorrectly entered garnishments can result in legal liability for the employer.

EPAY performance review cycles, 360-degree feedback, journaling entries, and review status tracking map to BambooHR's Performance Reviews module. Review dates, overall scores, status (draft, submitted, approved), and reviewer names migrate directly. Written feedback content migrates as text fields attached to the review record. Note that BambooHR's review cycle structure (annual, semi-annual, custom) may differ from EPAY's; we map the source review frequency to the closest BambooHR equivalent and flag any review templates requiring manual reconstruction.

EPAY course completion records, custom certificates, and training status map to BambooHR where the training module is available on the subscribed tier. Completion dates, course names, and certificate metadata migrate as training entries. BambooHR's training module supports course tracking and completion records but does not replicate complex custom course structures or curriculum sequences from EPAY. We export the full training history as a CSV archive and map what the BambooHR training module can consume; the customer's HR admin rebuilds curriculum structures in BambooHR if needed.

EPAY ACA measurement data, coverage offer records, and enrollment status for Affordable Care Act compliance have no native equivalent in BambooHR. We export the current ACA measurement period data, eligibility status, and coverage offer history as a compliance archive. The customer's HR team or legal counsel must determine how to maintain ACA compliance documentation post-migration, which may involve a separate ACA tracking tool or retaining EPAY access for compliance lookback during the measurement period.

EPAY stored employee documents (offer letters, contracts, signed agreements, identification copies) migrate as BambooHR Employee Files attached to the corresponding employee record via the BambooHR Files API. We resolve file attachments by employee ID match and map the document type (I-9, W-4, offer letter, etc.) to the BambooHR file category. BambooHR's file storage limits apply per the subscribed plan; we verify storage availability before importing large document volumes.