Migrate from Sage HRMS to BambooHR

Sage HRMS Employee records map 1:1 to BambooHR Employee profiles using the employee ID as the dedupe key. Standard biographical fields (name, date of birth, hire date, termination date, employment status, gender, address, contact information) transfer directly. Any custom employee fields defined in Sage HRMS are inventoried during discovery and created as BambooHR custom fields before the import run. Employee Self Service visibility columns from Sage HRMS do not migrate because BambooHR's field visibility model is role-based and does not use the same column-linking approach.

Sage HRMS Positions define job titles, grade levels, and pay ranges as a structural layer. We extract the position table and map grade levels and pay ranges to BambooHR's Compensation section fields. Job titles from Sage HRMS transfer as BambooHR Job Title values, and we note that BambooHR does not have a separate position management hierarchy; organizations that depend on multi-level position grading in Sage HRMS should plan to replicate grade-step configurations in BambooHR's pay structure during post-migration setup.

Sage HRMS Departments (defined in a chart-of-accounts-style organizational structure) map directly to BambooHR Departments. We extract the full department tree including cost-center assignments used in Sage HRMS payroll allocation and re-create the hierarchy in BambooHR. If cost-center codes are used separately from department names, we carry them as a custom field on the department record or as an employee custom field for payroll allocation purposes.

Sage HRMS Pay Groups define pay frequency (weekly, bi-weekly, semi-monthly, monthly), deduction priorities, and tax jurisdiction. BambooHR uses Pay Schedules to define pay frequencies and reporting periods. We extract all Pay Group configurations and map them to BambooHR Pay Schedules, preserving deduction priority order as BambooHR deduction configuration entries. Note that BambooHR does not handle actual payroll processing; the Pay Schedule defines the cadence for the time-tracking and benefits reporting workflows.

Sage HRMS stores historical earnings, deductions, and tax withholdings across multiple fiscal-year tables. BambooHR does not have a payroll history storage module. We extract the last two to three fiscal years of pay stub data and deliver it as a structured CSV report keyed by employee ID, suitable for import into a third-party payroll system (Gusto, Paychex, ADP, or the customer's preferred payroll vendor). Historical earnings statements also serve as a hard-copy archive for employment verification and audit purposes. This is a critical migration-gap disclosure: payroll history does not live in BambooHR as a native module.

Sage HRMS Benefit Plan definitions (carrier assignments, coverage tiers, plan types: medical, dental, vision, life, FSA, HSA, 401k) and active employee enrollments map to BambooHR's Benefits module. BambooHR's Benefits module supports enrollment tracking and carrier reporting but is not a full benefits administration platform; organizations using Sage HRMS Advanced Benefits Administration should evaluate whether BambooHR's benefits module meets carrier EDI feed requirements before migration. We extract plan definitions, enrollment records, and coverage effective dates and map them to BambooHR benefit entries. Any EDI feed configuration from Sage HRMS does not migrate and must be re-established with the payroll or benefits vendor post-migration.

Sage HRMS accrual rules and current time-off balances per employee migrate to BambooHR's Time Off module. We extract accrual balances as of the migration date and seed BambooHR with opening balances for each employee. Sage HRMS accrual calculation rules (monthly, annual, carryover limits, forfeiture policies) are documented as a written policy handoff for the customer's HR admin to reconfigure in BambooHR's policy builder. BambooHR does not inherit Sage HRMS accrual calculation logic; manual policy reconstruction is required.

Federal, state, and local tax codes and rates stored in Sage HRMS are extracted as a reference table. BambooHR does not maintain a tax code library; organizations that need payroll tax filing in BambooHR use a third-party payroll provider. We deliver the Sage HRMS tax agency configuration (federal EIN, state agency accounts, filing frequencies) as a written reference document so the customer's payroll vendor or HR admin can re-establish tax filing relationships in the new system. This is scoped as a documentation delivery, not a data migration, because BambooHR does not have a tax code storage module.

Documents stored in Sage HRMS (I-9s, W-4s, offer letters, performance records, disciplinary files) are exported as a file bundle keyed by employee ID. We deliver the file bundle alongside the data migration JSON so the customer's HR admin can manually attach documents to the corresponding BambooHR Employee record, or host them in a linked document management system. BambooHR's native file attachment supports document upload per employee but does not have a bulk document ingestion API; this step requires manual admin action or a document management tool integration.

Sage HRMS review templates, ratings, and narrative responses map to BambooHR's Performance module. We extract available review data (review period, reviewer, reviewee, overall rating, dimension scores, and narrative fields) and map them to BambooHR Performance records. Sage HRMS review templates vary by customer configuration; we inventory the template structure during discovery and map each dimension to an equivalent BambooHR Performance dimension or custom field. Note that BambooHR's performance review workflows are distinct from Sage HRMS's; review cycle configuration does not migrate and must be rebuilt in BambooHR.

If the Sage HRMS ATS module is active, we extract job requisitions, candidate profiles, application status history, and notes. BambooHR includes an Applicant Tracking System on Growth and higher tiers. Candidate records migrate to BambooHR Candidates, with application status mapped to BambooHR's Application Status values. Active job postings do not migrate; they must be re-created in BambooHR's ATS job board or linked ATS tool. Candidate resume files are bundled separately for manual upload or ATS-attachment post-migration.

Sage HRMS custom fields on Employees, Jobs, and other objects are inventoried during discovery and mapped to BambooHR custom fields of equivalent data type (text, date, number, dropdown, checkbox). Sage HRMS custom fields tied to ESS column dependencies are flagged as a separate workstream because ESS column linkages do not survive the migration. We pre-create all BambooHR custom field definitions before the employee import run so that the import payload satisfies the schema without type-mismatch rejections.