Migrate from Easy Tech to BambooHR

Core employee record maps directly to BambooHR's Employee object. We preserve Easy Tech's employee ID as a custom field (EmployeeID__c) for traceability. Personal information fields map field-by-field to BambooHR's standard fields and custom fields where no native equivalent exists. During migration we also validate data completeness and flag any missing required fields before writing to BambooHR.

If Easy Tech stores name components, address, and contact details in a separate linked object, we merge these into BambooHR's Employee record before writing. Name fields (firstName, lastName) map directly; address fields merge into BambooHR's addressLine fields. We also ensure country-specific address formats are normalized to match BambooHR's expected field structure, and any missing phone numbers are flagged for manual review.

Easy Tech's employment record (job title, hire date, department, employment type) maps to BambooHR's Employee work tab. We flatten the relationship so job title becomes the jobTitle field, hireDate maps to hireDate, and employment type maps to employmentHistoryStatus. If the employment record includes a start date for each job change, we store the most recent start date as the official hireDate and flag prior job history for reference.

If Easy Tech maintains a history of job title changes or department transfers, we cannot preserve the full audit trail natively in BambooHR. We migrate the most recent job title as the current jobTitle and store the history as a custom field (Job_History_JSON__c) for reference.

Easy Tech's compensation record may contain payRate, payFrequency, and payType in separate fields. We flatten these into BambooHR's payRate and payType fields. Hourly rates, salaried amounts, and contractor rates require value mapping from Easy Tech's codes to BambooHR's payType enumeration.

BambooHR's native location field stores physical work locations. If Easy Tech uses departments as organizational units rather than physical locations, we create a custom Department__c field and map Easy Tech department names to that field. BambooHR's Locations feature can be used as a secondary structure if your team sets it up.

Easy Tech's PTO or time-off balance records map to BambooHR's Time-Off tracking. We read accrued hours, used hours, and balance for each policy type and create corresponding accrual records in BambooHR. Note that BambooHR manages accruals through its policy engine — we create the opening balances and your admin configures accrual rules.

Easy Tech custom fields migrate to BambooHR custom fields. BambooHR supports text, number, date, and dropdown field types. Multi-select or complex custom fields in Easy Tech require an alternative handling strategy — we discuss this with your admin before migration and document any fields that cannot map natively.

Employee documents attached to records in Easy Tech (offer letters, certifications, resume) re-upload to BambooHR's Files section on the Employee record. We preserve file names and original upload dates. BambooHR's 25MB per-file limit applies. If a file exceeds the 25MB limit, we split it into smaller parts or notify the admin to reduce file size before migration.

Easy Tech workflows, approval chains, and automation rules do not migrate. They must be rebuilt in BambooHR's workflow builder or documented manually. We export Easy Tech workflow definitions as a reference document so your BambooHR admin can recreate them. The exported document includes each step's conditions, assigned users, and any escalation paths. This serves as a step‑by‑step guide for rebuilding the logic in BambooHR.