Migrate from E-Staff to BambooHR

E-Staff Employee records map to BambooHR Employee. The employee's firstName, lastName, dateOfBirth, ein, employeeNumber, department, division, employmentStatus, and hireDate migrate directly to their BambooHR standard field equivalents. E-Staff's employee photo (if stored as a file attachment) migrates as a separate ContentDocument record linked to the Employee. Employment status values (Active, Terminated, On Leave) map to BambooHR employmentStatus list values, with any E-Staff custom status values mapped to a custom list field or notes field.

E-Staff organizational hierarchy maps to BambooHR Department and Division standard list fields. We extract all distinct department and division values from E-Staff, validate them against BambooHR's allowed list format, and pre-populate the Department and Division picklist values in BambooHR admin before employee import. If E-Staff stores a multi-level org chart, we flatten it to Department and Division assignments per employee; a written org chart inventory is delivered for the customer's admin to configure in BambooHR's org chart display if needed.

E-Staff effective-dated compensation rows (salary, hourly rate, bonus, commission, equity grant) migrate to BambooHR Compensation records as independent inserts rather than field updates. Each row carries its effective date (pay effectiveDate in BambooHR), compensation type (payType), compensation rate (payChange), compensation frequency (payPer), and currency. The audit trail is preserved because BambooHR Compensation stores the history as separate rows with effective dates. This is the recommended approach to maintain the original audit trail rather than overwriting a current-compensation field.

E-Staff employment history events (title changes, department transfers, manager updates, status changes) map to BambooHR Job Info table records. Each job info entry carries its effective date (effectiveDate), job title (title), employment status (employmentHistoryStatus), work email (workEmail), work phone (workPhone), department (department), division (division), FLSA exempt status (exempt), EEO category (eeo), and location. We sequence job info entries in chronological order by effectiveDate before import to maintain the correct historical sequence in BambooHR.

E-Staff benefits enrollment records map to BambooHR Benefits Administration (Elite plan feature). Each enrollment record references the employee (BambooHR employeeId), benefit plan type (benefitPlan), coverage level (dependents), and enrollment date. Benefits Administration in BambooHR is an add-on product that requires separate configuration of benefit plan types and carriers; we migrate the enrollment data as records once the customer's admin has configured the plan types in BambooHR's Benefits settings. If the customer is not on BambooHR's Elite plan, we document the enrollment records as a CSV deliverable for the customer's admin to import manually.

E-Staff accrued time-off balances migrate to BambooHR Time Off Management as balance records for each employee by policy type (PTO, Sick, Personal, etc.). We map E-Staff accrual policy names to BambooHR time-off types, and carry the current balance, accrual rate, and carry-over amounts. BambooHR's time-off approval workflows are not migrated as automation; the admin configures these from BambooHR's Time Off settings post-migration.

E-Staff Candidate records have no direct equivalent in BambooHR's core HR platform. Candidates are staffing-specific: they represent job seekers in the pipeline before an offer. BambooHR's ATS is a separate paid add-on ($99-$199/month based on job opening limits) that tracks job postings, applications, candidate communications, and hiring pipelines. We do not migrate Candidate records as data rows. Instead, we deliver a written inventory of all active and historical Candidate records with their last status, source, and submitted date, so the customer's admin can determine which candidates to manually re-enter into BambooHR ATS or retain as a CSV for compliance.

E-Staff Placements (the staffing-specific record that links a Candidate to a job order, defines bill rate, pay rate, start date, and assignment terms for a contingent worker) have no equivalent object in BambooHR. BambooHR is not a staffing management tool. We do not migrate Placements as records. We deliver a written inventory of all active Placements with their terms (bill rate, pay rate, start/end dates, client or project reference, status) so the customer's admin can determine whether to maintain these in a spreadsheet, a dedicated staffing tool, or BambooHR as custom objects in the Elite plan.

E-Staff allows user-defined fields with no enforced naming convention. During scoping, we extract all custom field definitions (field name, data type, picklist values if applicable) from E-Staff and audit them against BambooHR's standard field list. Any standard field that exists in BambooHR (e.g., E-Staff custom field 'Shirt_Size' maps to a BambooHR custom field of type dropdown) is pre-created in BambooHR admin before any employee record import. E-Staff custom fields with no clear BambooHR equivalent are inventoried and mapped to the closest BambooHR custom field type, with a notes column explaining the mapping rationale. Field type mismatches (e.g., E-Staff stores a free-text date where BambooHR expects a date type) are resolved through data transformation during the import pipeline.

E-Staff stored documents (offer letters, contracts, signed agreements, I-9s, tax forms) attached to Employee records migrate as BambooHR Documents linked to the corresponding Employee. We extract file attachments from E-Staff, preserve file name and content, and upload to BambooHR Documents with the employee record as the parent. BambooHR's e-signature integration (built into Onboarding) handles new hire document signing post-migration. Historical signed documents are preserved as static PDF files.