HRMS migration

Migrate from HR Director to BambooHR

Field-level mapping, validation, and rollback between HR Director and BambooHR. We move data and schema; workflows are rebuilt natively in BambooHR.

HR Director logo

HR Director

Source

BambooHR

Destination

BambooHR logo

Compatibility

75%

9 of 12

objects map 1:1 between HR Director and BambooHR.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

HR Director logo

HR Director

What's pushing teams away

  • Limited public footprint on G2 and Capterra makes peer validation difficult, and prospective buyers struggle to find verified reviewer feedback.
  • Reporting depth and analytics features fall short of mid-market HRIS leaders like BambooHR or HiBob.
  • No publicly documented developer API restricts integration into bespoke payroll or learning systems.
  • Vendor scale is smaller than international HRIS providers, so partner ecosystem and integration libraries are narrower.
  • Migration tooling is not documented publicly; data egress runs through admin export or vendor-assisted dumps rather than programmatic API.

Choosing

BambooHR logo

BambooHR

What's pulling them in

  • Lowest friction entry point for SMBs moving off spreadsheets — intuitive interface means most teams are functional within days, not weeks.
  • Consolidation value: BambooHR merges ATS, onboarding, HR records, time-off, and payroll into a single pane of glass that employees never need to leave.
  • Volume discounts applied automatically by headcount, so pricing scales predictably as the company grows without renewal negotiations.
  • BambooHR reports most customers go live in four to six weeks, making it a realistic commitment for under-resourced HR teams.
  • Award-winning Support Heroes cited frequently in reviews — responsive human support after implementation is a differentiator.

Object mapping

How HR Director objects map to BambooHR

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

maps to

BambooHR

Employee

1:1
Fully supported

HR 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

maps to

BambooHR

Locations (Company-level)

1:1
Fully supported

HR 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

maps to

BambooHR

Department

1:1
Fully supported

HR 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

maps to

BambooHR

Pay Rate Fields

1:1
Mapping required

HR 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

maps to

BambooHR

Time Off

1:1
Fully supported

HR 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

maps to

BambooHR

Time Off (Holiday)

1:1
Fully supported

HR 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

maps to

BambooHR

Emergency Contact Fields

1:1
Fully supported

HR 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

maps to

BambooHR

Files (Documents)

1:1
Fully supported

HR 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

maps to

BambooHR

Custom Fields

1:1
Mapping required

HR 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

maps to

BambooHR

Job History (Notes or Custom Fields)

lossy
Fully supported

HR 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

maps to

BambooHR

Benefits Administration

lossy
Mapping required

HR 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

maps to

BambooHR

Workflows and Approvals

lossy
Fully supported

HR 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.

Gotchas + challenges

What specifically takes care here

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 logo

HR Director gotchas

High

Catalog ambiguity — 'HR Director' brand maps to multiple regional offerings

Medium

Sparse public reviewer data

Medium

No public developer API

BambooHR logo

BambooHR gotchas

High

Undocumented API rate limits can trigger 503 errors

High

Per-employee pricing model requires active record count verification

Medium

API credentials must be sent on every request to avoid extra round trips

Medium

Custom field schema varies per account and requires manual inventory

Low

Document and attachment exports are not covered by standard report exports

Pair-specific challenges

  • Custom leave entitlement rules do not migrate as configured policies

    HR Director stores leave entitlement rules as data on employee records (e.g., additional annual leave days for tenure, contracted hours adjustments, carry-over limits). BambooHR's Time Off uses a policy-based entitlement model where rules are configured in the policy editor and assigned to employees. There is no BambooHR API endpoint that ingests entitlement rules as records. We seed current PTO balances as initial values in BambooHR's Time Off, but the customer's admin must recreate every entitlement rule in BambooHR's policy editor. We deliver a written entitlement-rule inventory listing each rule's parameters so the admin can rebuild them without reverse-engineering the logic from HR Director data.

  • Employment status updates require a separate API table in BambooHR

    BambooHR's employmentStatus field on the Employee record is read-only via the standard employee API (v1.1 and above). Status changes — including new hires, status changes (full-time to part-time), and terminations — must be submitted through BambooHR's employmentStatus table endpoint, which requires the employee ID, effective date, and the new status value. We handle this sequencing during migration by submitting status changes in effective-date order after the employee record is created. If HR Director stores termination records with a past effective date, those must be applied to BambooHR using the same effective-date sequence to avoid the employee appearing active when the account is first provisioned.

  • Document imports require separate authentication scope and chunking

    HR Director employee documents (contracts, right-to-work files, certifications) must be imported as file attachments to BambooHR Employee records via BambooHR's file upload API. The API requires an active BambooHR session with the Files scope and imposes a 5 MB per-file limit. Documents larger than 5 MB are split into chunks; PDFs over 20 MB are migrated as ZIP archives with a reference note on the employee record. We validate that all migrating documents are within these limits during the discovery phase and flag oversized files for the customer to split or convert before migration.

  • BambooHR does not have a native Company/Account object separate from Employee

    HR Director has a Company/Organisation level above the Employee record, storing the employer entity's details (name, registration number, registered address, logo). BambooHR does not have a standalone Company or Account object — the employer entity is represented by the BambooHR account itself, and employee records are the primary data container. We handle this by mapping HR Director's company-level data to BambooHR's company profile settings and Locations, rather than importing it as a separate record type. Any HR Director custom fields on the Company object are evaluated individually and migrated as employee-level custom fields or documented notes.

  • Payroll processing rules and RTI submissions do not migrate

    HR Director's integrated UK payroll module — including PAYE configuration, RTI submission settings, auto-enrolment pension scheme details, and custom pay components — does not have a direct equivalent in BambooHR's US-native payroll engine. BambooHR Payroll is designed for US payroll tax filing, direct deposit, and pay schedules. UK customers using HR Director's payroll functionality will need to either retain a separate UK payroll provider (BambooHR supports payroll integration with third-party providers) or configure a new payroll workflow post-migration. We do not migrate payroll configurations. We deliver a payroll data inventory (pay run history, pay components, pension contributions, garnishments) in CSV format for the customer's payroll admin to enter into their chosen payroll system.

Migration approach

Six steps for a successful HR Director to BambooHR data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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

Context on both ends of the pair

HR Director logo

HR Director

Source

Strengths

  • UK-focused statutory compliance and reporting out of the box.
  • Lower per-employee cost than enterprise HRMS platforms.
  • Cloud delivery without on-premise server requirements.
  • Combines core HR, payroll-relevant data, and absence in one tool.
  • Smaller-scale vendor model often translates to direct support access.

Weaknesses

  • Limited public reviewer presence makes validation difficult.
  • Reporting and analytics depth lag mid-market HRIS leaders.
  • No publicly documented developer API.
  • Smaller integration ecosystem than international HRIS providers.
  • Migration tooling not documented publicly.
BambooHR logo

BambooHR

Destination

Strengths

  • Single platform consolidating ATS, onboarding, HR records, payroll, and time-off reduces system sprawl for SMBs.
  • Fast implementation — BambooHR reports four to six weeks from kickoff to go-live for most customers.
  • Per-employee pricing with automatic volume discounts makes cost predictable as headcount grows.
  • Strong customer support reputation (Support Heroes) cited consistently across G2, Capterra, and direct testimonials.
  • Well-documented API with UTF-8 encoding, clear field types, and HTTPS-only access.

Weaknesses

  • Mobile application is significantly limited compared to the desktop experience, frustrating remote and field workers.
  • Companies above 150–200 employees frequently outgrow the platform's feature depth and customization surface.
  • Limited advanced reporting and analytics compared to enterprise HR platforms — custom report building is the ceiling.
  • PTO and profile customization are pain points — non-standard accrual policies and complex org structures require workarounds.
  • Document management and attachment handling lack the granularity of dedicated document-centric HR systems.

Complexity grading

How hard is this migration?

Standard HRMS migration. 2 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across HR Director and BambooHR.

  • Object compatibility

    B

    2 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    HR Director: Not publicly documented..

  • Data volume sensitivity

    B

    HR Director doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your HR Director to BambooHR migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about HR Director to BambooHR data migrations

Answers to the questions buyers ask most during HR Director to BambooHR migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 500 employees with clean data, no complex PTO accrual rules, and no document archives over 5 MB. Migrations with multi-year compensation histories, complex leave entitlement rules (tenure-based accruals, carry-over limits), large document attachment sets, or multi-location organisational structures move to eight to twelve weeks because of effective-date sequencing work, entitlement-rule documentation scope, and chunked file upload processing.

Adjacent paths

Related migrations to explore

Ready when you are

Move from HR Director.
Land in BambooHR, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day