HRMS migration

Migrate from Breathe to BambooHR

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

Breathe logo

Breathe

Source

BambooHR

Destination

BambooHR logo

Compatibility

90%

9 of 10

objects map 1:1 between Breathe and BambooHR.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Breathe to BambooHR is a mid-market HRIS transition that requires explicit handling of five structural differences. Breathe stores documents in two UI-bound silos with no bulk export API, making document migration a manual step rather than an automated one. Leave balances in Breathe are calculated internally and must be independently verified against entitlement settings and approval records before loading to avoid carry-forward errors. BambooHR is US-centric and uses US employment forms; UK-specific fields such as National Insurance numbers, UK right-to-work schema, and statutory pay references require explicit mapping to BambooHR's custom field model rather than native fields. Performance review templates and historical review data migrate as structured records, but the review cycle definitions are configuration that requires rebuilding in BambooHR. Sickness entries and Breathe Learn completion records may fall outside the standard People Data Export if the customer is on a lower Breathe tier, requiring additional extraction steps identified during the pre-migration data audit.

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

Breathe logo

Breathe

What's pushing teams away

  • Organisations with more than 200 employees report that Breathe lacks the advanced HR features — including rich performance management, payroll integration depth, and configurable workflows — needed for complex operations.
  • Users on G2 and Capterra describe the interface as not user-friendly, with continued usability issues that persist across updates, making day-to-day navigation frustrating for HR administrators.
  • Reviewers who switched away cite limited customisation: custom fields are supported but the platform does not expose a flexible object model for building custom workflows or integrating with non-standard HR processes.
  • Absence reports and advanced analytics require higher tiers or add-on modules, and the reporting interface lacks the drill-down capabilities that growing HR teams expect from modern platforms.

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 Breathe objects map to BambooHR

Each row shows how a Breathe 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.

Breathe

Employee

maps to

BambooHR

Employee

1:1
Fully supported

Breathe Employees map to BambooHR Employees as the central record. The Breathe People Data Export provides the primary employee dataset including name, contact details, job role, department, start date, employment status, and emergency contacts. National Insurance numbers, UK right-to-work references, and other UK-specific fields have no native BambooHR equivalent and map to custom fields that we create in the destination before import. We use the employee's email address as the BambooHR dedupe key to prevent duplicate records on re-runs.

Breathe

Custom Fields

maps to

BambooHR

Custom Fields

1:1
Mapping required

Breathe custom fields on the Employee record extract from the People Data Export as field-name and value pairs. We map each to an equivalent BambooHR custom field, flagging any fields with unsupported data types (multi-select, date calculations, formula fields) that require type conversion or truncation. Fields present in Breathe that have no mapping target in BambooHR are flagged in the pre-migration data audit for the customer's HR admin to decide whether to retain or drop.

Breathe

Absence / Leave records

maps to

BambooHR

Time Off

1:1
Fully supported

Breathe annual leave, sick leave, and other absence types map to BambooHR Time Off records. Leave types (Annual Leave, Sick Leave, Other) are created as BambooHR Time Off Policies before record import. We verify leave balances independently by extracting entitlement settings and approval records and computing expected balances, then comparing against any pre-calculated balance fields in the export before loading. This resolves the common carry-forward error where Breathe's internal balance calculation is assumed to be accurate at a point-in-time.

Breathe

Sickness records

maps to

BambooHR

Time Off (Sick)

1:1
Fully supported

Breathe sickness entries are a distinct record type linked to employees. We export the full sickness history including dates, return-to-work dates, reasons, and Fit Note references where present. Sickness records migrate as BambooHR Time Off entries under a Sick leave policy. Fit Note metadata (return-to-work dates, fitness-to-work declarations) maps to custom fields on the Time Off record because BambooHR does not have a native Fit Note field.

Breathe

Performance reviews

maps to

BambooHR

Performance Reviews

1:1
Mapping required

Breathe Performance Review module records, review templates, and historical review data map to BambooHR Performance Management (Pro tier). We extract review cycle names, review periods, ratings, and reviewer comments as structured records. The review template structure and rating rubrics are configuration that does not migrate automatically; we deliver a written inventory of the existing templates with their structure so the customer's BambooHR admin rebuilds them in BambooHR's review builder.

Breathe

Onboarding

maps to

BambooHR

Onboarding / Employee setup tasks

1:1
Mapping required

Breathe onboarding records track new-hire tasks, pending documents, and workflow steps. We extract the task list and completion status as structured Employee Custom Fields or a supplementary onboarding checklist document. Onboarding workflow definitions are configuration and do not migrate; we document the source workflow steps for the customer's admin to rebuild in BambooHR's onboarding module.

Breathe

Remuneration Report

maps to

BambooHR

Employee Compensation Fields

1:1
Fully supported

Breathe provides a Remuneration Report covering salaries, additional payments, benefits, and auto-enrolment pension data via Reports > Payroll exports. We extract these as structured records and map salary, bonus, benefits, and pension contribution fields to BambooHR Employee fields and custom fields. Annual salary and pay frequency map to BambooHR's pay rate and pay frequency fields where supported. Auto-enrolment pension scheme and contribution percentages map to custom fields as BambooHR does not have a native UK pension scheme tracker.

Breathe

Documents (Company and Employee)

maps to

BambooHR

Employee Files

lossy
Not supported

Breathe stores Company documents and Employee documents in two separate UI sections with no bulk export API. We provide a guided checklist for the customer's HR admin to download documents from Company > Company Documents and Profile > More > Documents. Each file is attached to the corresponding BambooHR Employee record via the Files tab. Contract documents, right-to-work evidence, and offer letters attach directly; company-wide policy documents attach to a designated admin employee record or are stored in BambooHR's Company Files section if the destination account has this feature enabled.

Breathe

Breathe Learn (completion records)

maps to

BambooHR

Training / Custom Fields

1:1
Fully supported

Breathe Learn completion records (GDPR awareness, health and safety, and other compliance training) may not be included in the standard People Data Export depending on the customer's Breathe tier and module configuration. We perform a pre-migration data audit against the customer's module list and flag any modules that require additional extraction steps. Completion records that export are mapped to BambooHR custom fields or a training completion log as a supplementary record.

Breathe

Employment History

maps to

BambooHR

Job History / Employment (Custom Fields)

1:1
Fully supported

Breathe maintains employment history including previous job titles, department transfers, and salary changes as part of the Employee record timeline. We extract the employment history entries and map them to BambooHR Employee custom fields capturing job title, department, and employment status history with effective dates. BambooHR does not have a native employment history object, so we structure the data as dated entries in a custom field set.

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.

Breathe logo

Breathe gotchas

High

No bulk document export — manual download required

High

No direct migration path between Breathe accounts

Medium

People Data Export may omit data in non-standard modules

Medium

Leave balance carry-forward requires manual verification

Low

Tier-gated features may limit export coverage

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

  • No bulk document export in Breathe requires manual download

    Breathe does not expose a bulk document export endpoint via its API. Company documents and Employee documents must be downloaded individually from the Breathe UI. For an organisation with 150 employees, this can mean navigating to 300+ individual document pages. We advise customers to begin document archiving at the scoping stage and provide a guided checklist of the Company > Company Documents and Profile > More > Documents sections to visit. Document migration is priced as an add-on manual task because it cannot be automated through any available API or export mechanism.

  • Leave balance figures must be independently verified before import

    Breathe calculates leave balances internally based on entitlement settings and approval records. Pre-calculated balance fields in the People Data Export may reflect a point-in-time snapshot that does not account for pending approvals, carry-forward rules, or mid-year entitlement changes. We extract entitlement settings and approval records independently and compute expected balances, then compare against any exported balance fields before loading. Any discrepancy is reconciled with the customer's HR admin before the BambooHR import runs. Migrations that skip this step routinely result in employees with incorrect holiday balances on day one of the new system.

  • Breathe Learn and non-standard module data may be excluded from People Data Export

    The standard People Data Export covers core employee data, absence history, and sickness records. Modules such as Breathe Learn completion records, custom third-party add-ons, and bespoke custom fields created outside the standard framework may not be included. We perform a pre-migration data audit against the customer's module list and tier before extraction begins, flagging any modules that require additional extraction steps or that have no migration path. Customers on lower Breathe tiers should verify which modules are licensed because some data (historical absence analytics, custom report definitions) is only available in higher tiers.

  • UK-specific fields have no native equivalent in BambooHR

    BambooHR is US-centric and uses US employment forms (I-9, W-4, US state-level payroll). National Insurance numbers, UK right-to-work schema, statutory sick pay eligibility flags, and UK auto-enrolment pension scheme references do not have native BambooHR fields. We map these to custom fields on the Employee record, but the customer should verify that their BambooHR account is configured for UK employment law compliance (available through BambooHR's UK-specific product tier and compliance intelligence add-on). UK-based organisations should confirm that BambooHR's compliance intelligence module covers UK employment law before treating migrated data as compliance-ready.

  • Performance review templates and onboarding workflows require manual rebuild

    Review templates, rating rubrics, review cycle definitions, and onboarding workflow configurations in Breathe are not data that exports as records. They are configuration that must be rebuilt in BambooHR's equivalent builder. We deliver a written inventory of every active Breathe performance review template and onboarding workflow with its structure, steps, and settings so the customer's HR admin can rebuild them in BambooHR. The rebuild is outside the data migration scope and is typically handled by the customer's admin team or a BambooHR implementation partner.

Migration approach

Six steps for a successful Breathe to BambooHR data migration

  1. Pre-migration data audit and scope definition

    We audit the source Breathe account across tier (Starter/Professional/Enterprise), active modules, custom fields, absence history depth, sickness record count, performance review history, and Breathe Learn module status. We produce a written data audit report listing every record type, record count, and module with a migration path status (automated, manual, or not available). The customer reviews and approves the scope before extraction begins. Any tier-gated modules are identified at this stage so the customer can upgrade or extract from the correct licensed module.

  2. Schema design and custom field creation in BambooHR

    We design the destination schema in BambooHR before any data moves. This includes creating all custom fields needed for UK-specific data (National Insurance number, pension scheme, Fit Note references, Breathe Learn completion flags) and mapping Breathe custom fields to their BambooHR equivalents with appropriate field types. We create the required Time Off policies (Annual Leave, Sick Leave, Other) to match Breathe's absence types. Time Off policies and custom fields are deployed into a BambooHR test account first for validation.

  3. Leave balance verification

    We extract entitlement settings, approval records, and any pre-calculated balance fields from Breathe independently. We compute expected current-year and carry-forward balances using the entitlement settings and approval history, then compare against the exported balance figures. Discrepancies are flagged to the customer's HR admin for resolution before the BambooHR import. This step prevents the most common day-one migration error: employees logging in to find their holiday balance is wrong.

  4. Guided document archival checklist delivery

    Because Breathe has no bulk document export API, we deliver a structured checklist identifying every document section to visit in the Breathe UI. The checklist lists Company Documents and each Employee's Profile > More > Documents section, with the document name and associated employee. The customer's HR admin works through the checklist in parallel with the data migration. We receive the downloaded files, rename them per a naming convention (EmployeeName_DocumentType_Date), and bulk-upload them to the corresponding BambooHR Employee records as the final migration step.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Employees first (establishing the central record with all core fields and custom fields mapped), Time Off policies (ensuring the leave types exist before absence records are loaded), Absence records (with independently verified balances), Sickness records, Remuneration data, and Performance review history. Each phase emits a row-count reconciliation report comparing source record count to destination record count before the next phase begins. Document files are uploaded last once all employee records exist to attach them to.

  6. Cutover, validation, and configuration rebuild handoff

    We freeze writes to the Breathe account during cutover, run a final delta migration of any records modified during the migration window, then enable BambooHR as the system of record. We deliver the performance review template inventory and onboarding workflow inventory to the customer's HR admin for rebuild. We support a one-week post-cutover window where we resolve any record-level reconciliation issues. We do not rebuild Breathe Learn, performance review templates, or onboarding workflows as part of the data migration scope; these are configuration tasks documented for the customer's admin team.

Platform deep dives

Context on both ends of the pair

Breathe logo

Breathe

Source

Strengths

  • Transparent per-employee pricing with no hidden fees for core HR features
  • Covers the full SME HR lifecycle — onboarding, absence, performance, documents — in one platform
  • Breathe Learn satisfies standard compliance training (GDPR, health and safety) out of the box
  • Clear tiered feature table published publicly, simplifying purchase decisions
  • Document storage for both company-wide and employee-specific records is integrated rather than requiring a separate DMS

Weaknesses

  • Limited scalability: customers report Breathe works well only up to approximately 200 employees, after which advanced HR features are insufficient
  • No direct migration tool between two Breathe accounts; customers must export manually and re-import
  • Interface usability issues cited by multiple G2 reviewers as a persistent pain point
  • Bulk document export is not available via API; documents must be downloaded individually from the UI
  • Advanced analytics, custom reports, and payroll integration depth are tier-gated add-ons rather than core features
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. 1 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 Breathe and BambooHR.

  • Object compatibility

    B

    1 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

    Breathe: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Breathe 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 Breathe to BambooHR data migrations

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

Can't find your answer?

Walk through your Breathe 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 200 employees with core absence and sickness data and no historical performance review records. Migrations that include full absence history spanning multiple years, performance review history, remuneration data, Breathe Learn completion records, or larger employee populations move to six to nine weeks because of independent balance verification, multi-table extraction, custom field mapping, and document archival time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Breathe.
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