Migrate from Eddy to BambooHR

Eddy Employee records map directly to BambooHR Employee. The employment status (active, inactive, contractor) maps to BambooHR's employmentStatus field. For contractors, we set employmentStatus to Contractor rather than creating a separate object, preserving headcount reporting in BambooHR. Name, contact details, job title, department, hire date, and termination date transfer 1:1. The Eddy employee number maps to BambooHR's employeeNumber field as the dedupe key.

Eddy contractor records map to BambooHR Employee with employmentStatus set to Contractor. BambooHR does not have a separate contractor object; contractors live in the same employee directory with their classification preserved via the status field. We extract contractor-specific fields (contract type, rate, end date) and map them to custom fields in BambooHR or to the closest standard fields available in the destination account.

Eddy PTO accruals and current balances migrate to BambooHR Time Off records. Each PTO policy type in Eddy (vacation, sick, personal) creates a corresponding Time Off type in BambooHR. The current balance amount and accrual date transfer as the initial balance snapshot in BambooHR. Carry-forward rules from Eddy are documented as a manual configuration step because Eddy does not expose carry-forward policy data via export; we flag this for the customer admin to configure post-migration.

Eddy employee documents (offer letters, signed agreements, contracts) migrate as file blobs to BambooHR Employee Files. We preserve original file names and attach each document to the correct employee via the BambooHR employee file API. PDF and standard document formats supported by Eddy transfer without format conversion. Documents without an associated employee (org-level policies) are migrated as company files and attached to the company-level document section.

Eddy's onboarding step checklists require manual extraction because no public API endpoint exposes the active task list and completion status. We extract the current onboarding workflow state per employee via screen-scraped export or guided manual pull, map the completed steps to BambooHR's onboarding checklist format, and create checklist items in BambooHR. Any steps that cannot be extracted are listed in a manual handoff document. This is the highest-effort object in the migration and contributes to the timeline range difference between straightforward and complex scopes.

Eddy training and certification records map to BambooHR Training. Certification name, status (completed, expired, in-progress), issue date, and expiration date transfer to the equivalent BambooHR training fields. Field naming differs between platforms; we create a mapping spreadsheet during discovery that pairs each Eddy training field to the BambooHR counterpart. Any certification records with status of expired or expiring within 30 days of migration are flagged for admin review.

Eddy's employee directory is derived from the underlying employee records, so migration is handled at the Employee object level. Organizational hierarchy information (reporting chains, department assignments, location assignments) transfers via the department, location, and supervisor fields on the BambooHR Employee record. Custom organizational chart fields in Eddy map to BambooHR's organizational structure fields.

Eddy company-level departments map to BambooHR Departments. Department name, location, and manager assignment transfer directly. If Eddy uses nested departments (sub-departments), we flatten the hierarchy during migration and create separate Department records in BambooHR, noting the parent-child relationship for manual reconstruction in BambooHR's org chart settings.

Eddy's HR and payroll modules are not fully integrated per reviewer reports on G2 and Capterra. Pay run history and payroll records require manual extraction via CSV or manual export from Eddy's payroll module. We extract any available payroll records during migration scoping and flag that full payroll data reconciliation is a manual step at the destination. BambooHR Payroll is a separate licensed add-on; the customer must set up payroll configuration separately from the HR data migration.

Eddy Hire job postings do not have a documented API export. Active job postings require manual export of the posting content, description, requirements, and pipeline stage. BambooHR's ATS has posting limits by plan (5 on Core, 25 on Pro, 50 on Elite); we confirm the customer's BambooHR plan before migration to ensure the job count is within limits. Any postings exceeding the plan limit are flagged for admin decision on archiving or selective migration.