Migrate from OrangeHRM to BambooHR

OrangeHRM's PIM (Personal Information Module) maps to BambooHR's Employee table with standard fields (name, date of birth, contact information, job title, supervisor) transferring directly. We preserve OrangeHRM's custom fields at the employee level as key-value pairs, creating equivalent custom fields in BambooHR's Employee table during schema setup. Custom field data types must be reconciled: OrangeHRM stores some custom fields with integer or date semantics that BambooHR may store as text; we apply type coercion during import. OrangeHRM's Employee ID is preserved as a cross-reference field for audit and reconciliation.

OrangeHRM leave entitlements (balances by leave type per employee) map to BambooHR's Time Off module with configurable PTO policies. We produce a leave-type reconciliation table during the mapping phase, explicitly mapping OrangeHRM leave type IDs and names to BambooHR policy types (e.g., OrangeHRM 'Annual Leave' → BambooHR 'Vacation', 'Medical Leave' → 'Sick'). Accrual methods (monthly, yearly, front-loaded) must be agreed with the customer because OrangeHRM and BambooHR store accrual logic differently. Pending and approved leave requests migrate as historical records with status preserved.

OrangeHRM punch-in/punch-out records and attendance summaries migrate to BambooHR's time-tracking module. OrangeHRM's Attendance module captures raw clock events; BambooHR focuses on time-off accrual and approval rather than raw time punches. We extract the attendance snapshot per employee per period, flagging records where OrangeHRM's attendance configuration uses a shift model that may not map directly to BambooHR's simplified time tracking. Starter-tier OrangeHRM instances may not have an attendance module at all; we confirm this during discovery.

OrangeHRM Performance module data (review cycles, ratings, reviewer assignments) maps to BambooHR's Performance Management module, available on the Pro plan ($17/user/mo). Goal and competency data from OrangeHRM migrates as custom fields in BambooHR since naming conventions differ. The customer's BambooHR plan tier must be Pro or Elite for the performance module to be available post-migration; we confirm tier selection during scoping. Review history and ratings transfer as audit records.

OrangeHRM Recruitment module candidate records and application status history map to BambooHR's built-in ATS. Vacancy associations migrate as job openings in BambooHR. The BambooHR ATS enforces plan-based job opening limits: Core allows 5 open positions, Pro allows 25, and Elite allows 50. We confirm the customer's plan tier and flag any vacancy count that exceeds the limit before migration. Status pipeline stages must be explicitly mapped; OrangeHRM's application stages differ from BambooHR's default ATS workflow.

OrangeHRM onboarding and offboarding tasks migrate to BambooHR's onboarding checklist feature, which supports customizable new-hire checklists and electronic signatures. Task type definitions and per-employee task assignments export from OrangeHRM via CSV (Starter) or API (Advanced). Onboarding task records are reconstructed in BambooHR as checklist items with completion status and assignee. The BambooHR onboarding feature is a standard feature at all paid tiers.

OrangeHRM vacancy records (title, description, hiring manager, status) migrate to BambooHR job openings. Active versus closed vacancy status is set explicitly in BambooHR at import time. OrangeHRM's job specification and hiring manager fields map to BambooHR's job opening metadata. We flag any OrangeHRM vacancies that are in a 'filled' or 'cancelled' state that should not create active BambooHR job openings.

OrangeHRM's supervisor-employee relationships (direct-report mappings and sub-department assignments) map to BambooHR's org chart and reporting structure. We extract direct-report mappings from OrangeHRM's PIM supervisor field and reconstruct the hierarchy in BambooHR. Cost center and sub-department assignments require field-level mapping to BambooHR's Department or custom fields.

OrangeHRM version 7.13+ introduced structured Work Schedules with shift pattern definitions per employee. We extract schedule assignments and map them to BambooHR's scheduling model where applicable. BambooHR does not have an equivalent shift-pattern model for multi-shift operations; organizations using complex shift scheduling in OrangeHRM may need to document schedules as employee custom fields or handle shift assignment as a post-migration administrative task.

OrangeHRM stores employee document uploads (contracts, ID scans, certifications) as file references. We export document metadata (filename, upload date, document type, associated employee) and provide a file copy package. The actual file content transfers separately as a file bundle organized by employee ID, which the customer's BambooHR admin uploads to the Files tab on each employee record. We deliver the file package with a mapping manifest linking each file to its target employee record.