Migrate from eBoss to BambooHR

eBoss employee records map to BambooHR Employee objects via the BambooHR API. Standard fields (firstName, lastName, dateOfBirth, employmentStatus, employeeNumber, workEmail, workPhone, homeAddress fields) transfer directly. The eBoss employee status property maps to BambooHR employmentStatus (values: Contractor, Full-Time, Part-Time, Terminated, Furloughed, or custom). Employee number maps to employeeNumber in BambooHR. Any eBoss custom fields on the employee record become custom fields in BambooHR, stored as name-value pairs using BambooHR's custom field API format. The email address is used as the primary dedupe key.

eBoss stores employment history and job changes (title, department, division, location, supervisor) with effective dates. BambooHR Job Information stores these as dated rows (date, employmentStatus, payRate, payType, payPeriod, jobTitle, department, division, location, supervisorId). We extract each eBoss job change as a separate Job Info row in BambooHR ordered by effective date. The most recent row drives the current state shown on the Employee summary view.

eBoss hierarchical reporting relationships map to BambooHR's supervisorId field on Employee. We resolve each supervisor reference at migration time by matching the supervisor's employee ID or email against the destination Employee table. Circular references are flagged in the discovery phase and escalated before import. The supervisor field drives the BambooHR org chart.

eBoss effective-dated compensation rows (base salary, bonus, commission, equity grant) map to the BambooHR Compensation table linked to the Job Information row. We preserve the compensation effective date (start and end), payRate, payType (salary, hourly, contractor), payPeriod (weekly, bi-weekly, semi-monthly, monthly), and any bonus or commission amounts as separate Compensation rows in BambooHR. Currency fields migrate as-is; any eBoss custom compensation fields become custom fields on the Job Info row.

eBoss PTO balances and accrual policies map to BambooHR Time Off balances. We extract each employee's current balance per policy (vacation, sick, personal) and create corresponding Time Off entries in BambooHR. Accrual methods are not importable as code; BambooHR calculates future accruals based on its configured policies. We flag any historical time-off requests and approvals as notes on the Employee record for the HR admin to re-enter or manually reconcile.

eBoss employee documents (offer letters, contracts, certifications, government IDs) migrate as BambooHR Employee Files. We export each file with its metadata (document type, upload date, category), then upload to BambooHR via the Files API and associate with the corresponding Employee record. Folder structure maps to BambooHR file categories (e.g., Personal, Offer Letters, Tax Documents, Certifications). Binary file integrity is verified by checksum before upload.

eBoss custom fields stored as name-value pairs on employee records become custom fields in BambooHR. We determine the appropriate BambooHR field type (text, number, date, dropdown, checkbox, or multiple-select) based on the source value format during discovery. Custom fields are created in BambooHR before any employee data loads, and the mapping is locked before the import phase begins to avoid schema drift mid-migration.

eBoss applicant and job posting records do not migrate into BambooHR Core or Pro because BambooHR Hiring is a separate add-on ($99-$199/month) with its own data model. If the customer has BambooHR Hiring enabled, we map applicants to Candidates and job postings to Jobs within the Hiring module. If BambooHR Hiring is not in the destination scope, we export the applicant data as a structured CSV and deliver it alongside the migration package for manual re-entry or a separate ATS migration. This is explicitly called out in discovery and confirmed before the migration plan is signed.

eBoss benefit plan enrollments and employee benefit elections map to BambooHR Benefits Administration (included on Pro and Elite plans). We extract enrollment records per employee per benefit type (health, dental, vision, 401k, HSA, FSA) and load them as Benefit Enrollment records in BambooHR. Plan configuration (carrier, plan type, employee cost, employer contribution) does not transfer; the customer's HR admin configures the benefit plan options in BambooHR before the enrollment records are associated.

eBoss department hierarchy and division structure map to BambooHR's Department and Division lists. Each eBoss department becomes a BambooHR Department entry with its supervisor. Division assignments migrate as a separate field on the Employee record. We verify that department codes or names are unique before import to avoid duplicate Department entries in BambooHR.