Migrate from HR-ON to BambooHR

HR-ON Employee records map 1:1 to BambooHR Employee File records using the POST /v1/staff/employees endpoint on HR-ON and the BambooHR employees API. Standard fields (firstName, lastName, workEmail, workPhone, dateOfBirth, hireDate, employmentHistoryStatus) transfer directly. The HR-ON id field becomes the BambooHR employee number, preserving the original identifier for reconciliation. All fields are validated against BambooHR's required-field schema before insert.

HR-ON stores organizational metadata (cost center, employment type, approval chain, location code) within systemFields on each Employee record rather than in separate objects. We extract all non-standard systemFields during scoping, classify them by data type (text, date, picklist), and map them to BambooHR custom fields created via the Custom Field Builder before migration. Any systemFields with incompatible types (e.g., multi-select from HR-ON without a BambooHR multi-select equivalent) are flagged in the mapping document for customer decision.

HR-ON document templates carry language variants (da_DK, en_US) as separate records, each with a documentType, dateFormat, and language tag. BambooHR supports document templates as a standard feature but does not natively differentiate templates by locale variant. We import the primary-language template and flag the language variant copies in the document mapping inventory, listing each with its source language code so the customer can reassign post-migration if bilingual documents are needed.

HR-ON does not expose a separate Department object; org metadata lives as systemFields on Employee (department name, division, location, reporting manager id). We parse these systemFields, deduplicate department names, create Department records in BambooHR, and resolve the reporting manager id against the migrated Employee records to build the correct manager-employee hierarchy. If HR-ON stores flat text manager names rather than IDs, we perform fuzzy name matching against the imported Employees.

HR-ON user accounts map to BambooHR user accounts. We extract user email, display name, role, and status. HR-ON-specific permission structures (e.g., granular Danish-document-access roles) map to BambooHR's role model as the closest equivalent, with any permissions that have no BambooHR analog flagged in the user mapping inventory for the customer's admin to configure post-migration.

HR-ON generates documents from templates and stores them with dateFormat and language metadata, either as binary blobs or as PDF links. We export the document content and metadata, then attach the files to the corresponding BambooHR Employee record under the Files tab. Document naming conventions from HR-ON are preserved in the file name. Any documents that cannot be linked because the source employee was not found in BambooHR are placed in an unassigned queue with a reference to the original HR-ON employee ID.

HR-ON stores dates in DD-MM-YYYY, DD/MM/YYYY, YYYY-MM-DD, or written form depending on the employee record's locale and template settings. We normalize all date values to ISO 8601 (YYYY-MM-DD) during extraction before loading into BambooHR. Date fields confirmed include dateOfBirth, hireDate, terminationDate, and any date custom fields carried from HR-ON systemFields.

HR-ON explicitly stores language at da_DK (Danish) and en_US (English) per template and per employee. We carry the language preference through to BambooHR's language field on the Employee record, preserving the source locale code. BambooHR's interface localization respects this setting for the employee-facing portal.

HR-ON stores employment status (active, inactive, on leave, terminated) as systemFields on Employee. BambooHR has a standard employmentStatus field with account-specific options. We map HR-ON status values to BambooHR status options during scoping, with unmapped statuses flagged for the customer to configure as BambooHR employment status options before production migration.

HR-ON custom properties on Employees that are not systemFields are extracted as custom fields on the Employee record. We map the field name, data type, and current value to a BambooHR custom field of matching or nearest type (short answer, long answer, checkboxes to multi-select picklist). Fields with HR-ON-specific picklist values are mapped to BambooHR picklist options with unmapped options flagged for the admin to resolve.