HRMS migration
Field-level mapping, validation, and rollback between HR Director and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.
HR Director
Source
BambooHR
Destination
Compatibility
9 of 12
objects map 1:1 between HR Director and BambooHR.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from HR Director to BambooHR is a consolidation as much as a migration. HR Director covers core HR and payroll for UK SMBs, but BambooHR delivers a unified HRIS with native payroll, time tracking, benefits administration, applicant tracking, and performance management under one subscription. We extract the Employee record as the primary object, migrate Compensation history with effective dates preserved in BambooHR's pay-rate fields, map organisational structures to BambooHR's location and department hierarchy, and transfer absence balances as PTO accrual entries. Custom leave entitlement rules that exist as data in HR Director do not migrate as configured rules in BambooHR — we document every rule during discovery so your admin can rebuild them in BambooHR's Time Off policy editor. Workflows, approval chains, and payroll processing rules are not migrated as code; we deliver a written inventory of these for your admin to rebuild post-cutover. The BambooHR API is the primary ingestion path, with bulk CSV used for initial load and the API for delta updates during cutover.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a HR Director object lands in BambooHR, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
HR Director
Employee
BambooHR
Employee
1:1HR Director's Employee record maps directly to BambooHR's Employee record. The Employee object is the primary record; all other objects (compensation, absence, documents) link to it via the employee ID. We extract standard fields (name, date of birth, start date, employment status, job title, department, location, work email, work phone, address) and map them to the BambooHR employee field API names. Employment status in HR Director uses a status field; BambooHR's employmentStatus is read-only via the standard API and must be updated via the employmentStatus table, which we handle separately during import sequencing.
HR Director
Company / Organisation
BambooHR
Locations (Company-level)
1:1HR Director's Organisation-level fields (company name, registration number, address, logo) map to BambooHR's company-level profile settings and Locations. BambooHR does not have a standalone Company object separate from Employee; organisational hierarchy is represented through Departments and Locations attached to employee records. We create Location records in BambooHR that correspond to the HR Director organisation's registered addresses, and we map the primary company address to the BambooHR company profile.
HR Director
Department / Division
BambooHR
Department
1:1HR Director's departmental structure maps to BambooHR's Department field on the Employee record. We preserve the full department hierarchy (parent department, sub-department) by creating department records in BambooHR before employee import so that the department assignment on each employee record can reference a valid parent. Department name is the dedupe key during import.
HR Director
Compensation
BambooHR
Pay Rate Fields
1:1HR Director compensation records (effective salary, pay frequency, currency, pay effective date) map to BambooHR's payRate and payRateEffectiveDate fields on the Employee record. We sequence compensation records by effective date and import the most recent effective entry as the current pay rate. Historical compensation records beyond the current rate are documented as a compensation history note in BambooHR's employee record because BambooHR does not natively store a compensation history timeline. We flag any future-dated compensation changes for reconfiguration in BambooHR's payroll settings rather than importing them as historical records.
HR Director
PTO / Absence
BambooHR
Time Off
1:1HR Director absence records (leave type, start date, end date, status, days taken, notes) map to BambooHR's Time Off entries. We extract current PTO and holiday balances and import them as accrual balances in BambooHR's Time Off system, creating Time Off types that correspond to HR Director's leave categories (annual leave, sick leave, parental leave). BambooHR's Time Off policy editor defines entitlement rules; we document every entitlement rule from HR Director as a written configuration guide so that the customer's admin can recreate the rules in BambooHR rather than importing them as data. Balances are imported as seed values against each policy.
HR Director
Holiday Entitlement
BambooHR
Time Off (Holiday)
1:1HR Director's statutory and contractual holiday entitlement maps to a dedicated Holiday Time Off type in BambooHR. We import the contracted holiday allowance (typically 20-28 days plus bank holidays in the UK context) as the entitlement amount for the UK statutory holiday policy in BambooHR. The customer configures bank holiday dates in BambooHR's Time Off settings; we provide a checklist of the relevant UK bank holidays for the current and prior year.
HR Director
Emergency Contact
BambooHR
Emergency Contact Fields
1:1HR Director emergency contact records (name, relationship, phone number, email) map to the Emergency Contact section on the BambooHR Employee record. We import each emergency contact as a separate entry linked to the same employee record. Relationship values are mapped to BambooHR's allowed relationship types; any HR Director values not supported by BambooHR are flagged for admin review.
HR Director
Employee Document
BambooHR
Files (Documents)
1:1HR Director employee documents (contracts, ID copies, right-to-work documents, qualifications, certifications) map to BambooHR's Files section attached to the Employee record. We import documents as file attachments via the BambooHR file upload API, preserving the original file name and attaching it to the correct employee record. Document categories in HR Director map to BambooHR file categories (Contract, Personal, Benefits, Performance). Binary file upload requires chunking for files over 5 MB; we handle this with multipart upload sequencing.
HR Director
Custom Fields
BambooHR
Custom Fields
1:1HR Director custom employee attributes (uniform size, certifications, visa status, union membership, etc.) map to BambooHR custom fields created via the Custom Field Builder before migration. We identify all HR Director custom fields during discovery, create equivalent BambooHR custom fields with matching types (short answer, list, checkbox, date), and then import values during the employee migration phase. BambooHR's Custom Field Builder supports short answer, long answer, list (single-select), checkbox, date, file upload, and employee-type fields. Custom fields are scoped per module, so a field relevant only to HR records is created in the HR Data module.
HR Director
Employment History
BambooHR
Job History (Notes or Custom Fields)
lossyHR Director employment history entries (previous job titles, department changes, location changes, promotion dates) do not map to a native BambooHR object. BambooHR tracks the current job title and start date but does not maintain a native employment history timeline. We document each employment change event (promotions, transfers, title changes) as a note on the employee record in BambooHR with the date, change type, and relevant detail. For customers who require a full audit trail, we create a custom Job History object with fields for change date, previous title, new title, previous department, new department, and change reason.
HR Director
Benefit Enrollment
BambooHR
Benefits Administration
lossyHR Director benefit plan enrolments (health, dental, pension/401k) map to BambooHR's Benefits Administration module on the Pro and Elite tiers. Benefit elections (plan type, coverage tier, employee contribution, employer contribution, effective date) are imported as benefit records on the employee. BambooHR's Benefits Administration supports open enrollment workflows and life event processing; we seed current benefit elections and document the plan structure for the customer's admin to configure in BambooHR's Benefits settings. Benefits Administration is an add-on on Core tier.
HR Director
Approval Chain / Workflow
BambooHR
Workflows and Approvals
lossyHR Director approval chains on absence requests, new hire onboarding, and payroll runs do not migrate as configured rules to BambooHR. We document every active approval chain during discovery: the triggering event, the approver(s), any conditional routing, escalation path, and notification settings. This is delivered as a written inventory that the customer's HR admin uses to rebuild equivalent rules in BambooHR's Workflows and Approvals app. BambooHR workflows support approval chains with conditional routing, delegation, and reminders.
| HR Director | BambooHR | Compatibility | |
|---|---|---|---|
| Employee | Employee1:1 | Fully supported | |
| Company / Organisation | Locations (Company-level)1:1 | Fully supported | |
| Department / Division | Department1:1 | Fully supported | |
| Compensation | Pay Rate Fields1:1 | Mapping required | |
| PTO / Absence | Time Off1:1 | Fully supported | |
| Holiday Entitlement | Time Off (Holiday)1:1 | Fully supported | |
| Emergency Contact | Emergency Contact Fields1:1 | Fully supported | |
| Employee Document | Files (Documents)1:1 | Fully supported | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| Employment History | Job History (Notes or Custom Fields)lossy | Fully supported | |
| Benefit Enrollment | Benefits Administrationlossy | Mapping required | |
| Approval Chain / Workflow | Workflows and Approvalslossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
HR Director gotchas
Catalog ambiguity — 'HR Director' brand maps to multiple regional offerings
Sparse public reviewer data
No public developer API
BambooHR gotchas
Undocumented API rate limits can trigger 503 errors
Per-employee pricing model requires active record count verification
API credentials must be sent on every request to avoid extra round trips
Custom field schema varies per account and requires manual inventory
Document and attachment exports are not covered by standard report exports
Pair-specific challenges
Migration approach
Discovery and data audit
We audit the source HR Director instance across employee record count, custom fields, department hierarchy, absence record volume, document attachment count and file sizes, compensation history entries (with effective dates), and benefit plan structure. We also identify any active approval workflows, payroll run settings, and UK-specific configurations (RTI, auto-enrolment). The discovery output is a written migration scope with record counts per object, a list of custom fields requiring BambooHR field creation, and the entitlement-rule inventory that the customer uses to rebuild Time Off policies post-migration.
BambooHR account provisioning and custom field creation
We provision the destination BambooHR account and configure the foundational schema before any data import. This includes creating Department records to match HR Director's organisational structure, creating Locations for each site, and creating all custom fields via BambooHR's Custom Field Builder. Time Off policy types are created (Annual Leave, Sick Leave, Parental Leave, etc.) with placeholder accrual amounts; the customer populates the actual entitlement rules from the written inventory. The BambooHR account is set to Test Mode so that employee records can be loaded and validated before the account goes live.
Department, Location, and Pay Structure setup
We create the Department hierarchy in BambooHR before employee import so that each employee record can reference a valid department. Locations are created for each HR Director site (head office, regional offices). Pay frequency (monthly, weekly, bi-weekly) and pay components (basic salary, overtime, bonus) are mapped to BambooHR's payroll settings. If the customer uses BambooHR Payroll, we seed the payroll configuration with the pay schedule; if the customer retains a third-party UK payroll provider, we configure the payroll integration settings.
Employee master record import
We import employee master records via the BambooHR API in dependency order: departments and locations first (validation only), then employee records with all standard and custom fields. Employment status changes are submitted via the employmentStatus table endpoint in effective-date order after the employee record is created. Compensation effective-date entries are imported as the current pay rate and documented as a compensation history note. Emergency contacts are imported as a separate call per employee after the employee record exists.
PTO and absence balance migration
We import current PTO balances as seed values against each BambooHR Time Off policy. Historical absence records (approved absence entries from HR Director) are imported as Time Off entries in BambooHR's Time Off system, preserving the original absence type, start date, end date, and days taken. We do not migrate entitlement rules as data; the customer uses the entitlement-rule inventory to configure BambooHR's Time Off policies with the correct accrual method, carry-over limits, and tenure adjustments. UK bank holidays are documented as a checklist for manual entry in BambooHR's Time Off settings.
Document migration and file attachment
We migrate employee documents (contracts, right-to-work, certifications) as file attachments via the BambooHR file upload API, scoped to the correct employee record and categorised by type. Files over 5 MB are chunked or flagged for the customer to pre-process. All documents are validated against the employee record by employee ID before upload to avoid orphaning.
Cutover, delta migration, and entitlement rebuild handoff
We freeze writes to HR Director during the cutover window, run a final delta import of any records modified since the initial extraction, then hand off BambooHR as the system of record. We deliver the written approval-chain inventory and the written entitlement-rule inventory to the customer's HR admin. We support a one-week hypercare window to resolve data reconciliation issues. We do not rebuild approval chains in BambooHR Workflows and Approvals, configure Time Off policy entitlement rules, or set up UK payroll within the migration scope; these are separate configuration tasks for the customer's admin.
Platform deep dives
HR Director
Source
Strengths
Weaknesses
BambooHR
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 2 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across HR Director and BambooHR.
Object compatibility
2 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
HR Director: Not publicly documented..
Data volume sensitivity
HR Director doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during HR Director to BambooHR migration scoping. Not seeing yours? Book a call.
Walk through your HR Director to BambooHR migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave HR Director
Other ways to arrive at BambooHR
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.