Migrate from Aotal to BambooHR

Aotal employee records map to BambooHR Employee. The Aotal employee record contains personal data, employment dates, and job assignments. We map firstName, lastName, workEmail, hireDate, and terminationDate directly. Any Aotal custom employee fields migrate to BambooHR custom fields (referenced by field ID via GET /v1/meta/fields). BambooHR's field-request model means we must specify field IDs explicitly during migration rather than receiving all fields by default.

Aotal Department records map to BambooHR Department. Department is the parent entity for Employee in BambooHR's org hierarchy. We load Departments first in the migration sequence so that the Department ID reference is satisfied when Employees are inserted. Aotal's multi-level department hierarchy (parent and child departments) maps to BambooHR's flat department structure with a parentDepartment field if the destination account supports it.

Aotal Role records carry job title, effective start date, and end date for role history tracking. BambooHR does not natively store role history with effective dates. We map the current active role to the Employee's jobTitle field and preserve historical role assignments in a custom multi-value field or linked custom object if the customer requests full audit trail reconstruction. Effective-date sequencing is maintained by loading the most recent active role first.

Aotal competency profiles (skill ratings, competency assessments, proficiency levels) have no direct BambooHR equivalent. We split the competency data: numeric ratings map to custom number fields on the Employee record; text-based competency names and descriptions map to custom text fields or a custom object with an Employee lookup. The customer chooses between in-record custom fields (simpler, fewer lookups) or a competency custom object (more scalable for complex matrices) during scoping.

Aotal performance review cycles (goals, ratings, review dates, reviewer assignments) map to BambooHR Performance Management when the destination account includes the Performance add-on. Review status, rating scores, and feedback comments migrate as custom fields if the BambooHR Performance module is not included in the customer's plan. We preserve review dates as ActivityDate equivalents for audit ordering.

Aotal learning module records (courses completed, completion dates, curricula, certification dates) have no native BambooHR equivalent. We do not migrate the learning management system as a structured data model into BambooHR because it would require a custom object setup and ongoing maintenance. Instead, we export learning records as a structured CSV, recommend a dedicated LMS (such as BambooHR's integration partners or a standalone platform), and optionally store a completion flag or certification date as a custom field on the Employee record for quick reference.

Aotal onboarding workflow steps (documents to sign, tasks to complete, onboarding milestones) do not migrate as automated workflows. BambooHR Core includes a basic onboarding checklist builder. We deliver a written inventory of every Aotal onboarding step with its sequence, assignee, and completion criteria so that the customer's BambooHR admin rebuilds the checklist manually. This ensures the checklist reflects BambooHR's builder rather than a direct translation.

Aotal binary documents (employment contracts, signed agreements, offer letters) migrate as file attachments to the corresponding Employee record in BambooHR. We treat them as attachments-only because Aotal's internal document formats require case-by-case format review before any transformation. We flag any e-signature metadata (signing status, signer email, timestamp) as requiring a manual re-sign workflow in BambooHR's e-signature tool post-migration.

Aotal supervisor assignments on employee records map to BambooHR's supervisor field, which is a lookup pointing to another Employee record. We resolve supervisor assignments by matching Aotal supervisor employee ID to the migrated BambooHR Employee ID. If a supervisor record has not yet been migrated (dependency ordering issue), we hold the supervisor assignment and resolve it in a second pass after all Employees are loaded.

Aotal location data (office names, addresses, regional tags) maps to BambooHR Location. BambooHR uses Location as a lightweight org unit alongside Department. If Aotal stores multi-site data (which site an employee works at, remote vs office designation), we map it to the BambooHR Location field and note any Aotal regional groupings that do not have a direct BambooHR equivalent for manual consolidation.

Aotal employment history records (job title changes, department transfers, compensation adjustments with effective dates) do not migrate as a full audit log into BambooHR's employment history feature without a custom object setup. BambooHR Core provides basic employment status tracking (active, inactive, terminated). We map the current employment status directly; historical changes are preserved in a custom Employment_History__c object if the customer requires an audit trail, or noted as a reconciliation report for the HR admin to reference post-migration.