HRMS migration

Migrate from Homerun to BambooHR

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

Homerun logo

Homerun

Source

BambooHR

Destination

BambooHR logo

Compatibility

80%

8 of 10

objects map 1:1 between Homerun and BambooHR.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Homerun to BambooHR is a structural migration for teams that have outgrown the 60 req/min API ceiling and need deeper HRIS functionality beyond ATS. Homerun was primarily an ATS until the 2025 HR module expansion, which introduced Employee records, Time Off, and document storage only recently. We scope the migration based on which modules were active at migration time to avoid attempting imports of objects that were never created. BambooHR uses a REST API with per-employee-per-month pricing (Core from $10, Pro from $17, Elite from $25) and separates ATS as an add-on module at higher tiers. We sequence the migration in dependency order: Jobs before Candidates, Employees before Time Off, so no orphaned records land in the destination. Workflows, automations, and email templates do not migrate; we deliver a written inventory for your admin to rebuild.

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

Homerun logo

Homerun

What's pushing teams away

  • Limited analytics and reporting mean HR teams with sophisticated workforce insights needs often outgrow the platform's built-in capabilities.
  • Growth-stage companies requiring advanced workflow automation or deep custom integrations find the feature set insufficient for complex use cases.

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

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

Homerun

Vacancy

maps to

BambooHR

Job

1:1
Fully supported

Homerun Vacancy records map to BambooHR Job postings. Each Vacancy's title, description (rich text), department assignment, and location map to the equivalent BambooHR Job fields. Pipeline stage configurations in Homerun map to BambooHR Job status values (Open, Closed, Draft, Archived). We verify job opening limits per BambooHR tier during scoping: Core allows 5, Advantage allows 25, and Elite allows 50 active job openings simultaneously.

Homerun

Candidate

maps to

BambooHR

Candidate

1:1
Fully supported

Homerun Candidate records migrate to BambooHR Candidates with full contact details, application history, source attribution, and pipeline stage assignment preserved. Resume files migrate as file attachments linked to the Candidate record. The Candidate's application timeline (stage transitions with timestamps) migrates as notes or custom history fields in BambooHR. We resolve the Job reference at migration time to link each Candidate application to the correct BambooHR Job.

Homerun

Employee

maps to

BambooHR

Employee

1:1
Fully supported

Homerun Employee records (available for accounts with the 2025 HR module active) map to BambooHR Employee records. We map name, email, job title, department, employment status, start date, and manager hierarchy. The manager relationship resolves via User email lookup at migration time. Employment status values (Active, Inactive, On Leave) map to BambooHR's employee status field. Historical employment data beyond what was stored in Homerun cannot be reconstructed.

Homerun

Time Off

maps to

BambooHR

Time Off

1:1
Mapping required

Homerun Time Off balances and requests migrate to BambooHR Time Off as current-state records with effective dates. We export the current balance per policy, approved and pending requests, and accrual rate references. Historical accrual patterns are mapped to BambooHR's accrual policy engine based on policy type (annual grant, anniversary-based, or accrual-per-pay-period). Any pending requests in Homerun are migrated as-is with their status preserved for your BambooHR admin to action.

Homerun

Document

maps to

BambooHR

Employee File

1:1
Fully supported

Employee documents stored in Homerun migrate to BambooHR Employee Files attached to the corresponding Employee record. We export file metadata (name, type, upload date, uploader) and content via chunked retrieval for large files. Expiring document reminders (such as certification or license expiry dates) migrate as BambooHR custom fields or file tags depending on availability. We flag documents that cannot be retrieved due to permission restrictions during the API discovery phase.

Homerun

User

maps to

BambooHR

User

1:1
Fully supported

Homerun team members and user accounts migrate to BambooHR User records. We preserve role assignments (Admin, Recruiter, Hiring Manager, Employee) and ownership relationships so that Candidate assignments and Vacancy ownership map to equivalent BambooHR access. Active Users resolve by email match; inactive users migrate with their status preserved for admin review. We flag any Users without valid email addresses for manual resolution before import.

Homerun

Pipeline Stage

maps to

BambooHR

Job Stage

lossy
Fully supported

Homerun Vacancy pipeline stages (such as Applied, Phone Screen, Interview, Offer, Hired, Rejected) map to BambooHR Job stage values. We create a stage mapping document during scoping that your BambooHR admin applies as Job status options before migration. Stages that exceed the target tier's job opening limit are flagged for consolidation or archiving.

Homerun

Scorecard

maps to

BambooHR

Interview Scorecard

1:1
Fully supported

Homerun evaluation scorecards and their ratings migrate to BambooHR Interview Scorecards. The score schema may not map 1:1 if Homerun uses numeric ratings and BambooHR uses a different scale; we normalize to the closest available match and preserve evaluator comments as text. We resolve evaluator references to BambooHR User records via email mapping and flag any evaluators without matching accounts.

Homerun

Offer

maps to

BambooHR

Offer

1:1
Fully supported

Homerun offer letters migrate to BambooHR Offers with compensation details, start dates, conditional terms, and offer status preserved. Salary, bonus, and equity fields migrate as custom fields in BambooHR since Offers in BambooHR have a flexible schema. We handle formatting differences in compensation strings (currency symbols, thousand separators) and validate against the BambooHR field type requirements before import.

Homerun

Custom Field

maps to

BambooHR

Custom Field

lossy
Fully supported

Custom fields on any Homerun object (Candidate, Vacancy, Employee, Offer) migrate to equivalent BambooHR custom fields. We enumerate all custom properties during scoping, build explicit value mappings for picklist fields (verifying that each value exists in the BambooHR picklist), and apply type conversions for date, numeric, and text fields. Multi-select picklist values migrate as comma-separated strings or as separate custom fields depending on the BambooHR field configuration.

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.

Homerun logo

Homerun gotchas

High

60 requests per minute API rate limit

High

No bulk export endpoint

Medium

Analytics limitations documented in reviews

Medium

2025 HR module expansion changes migration scope

Low

No public data on tier-specific API availability

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 export endpoint in Homerun API

    Every object in Homerun is read through paginated list endpoints with no batch or bulk alternative. There is no single API call that returns all records of a given type. We compensate by running parallel paginated streams tuned to the 60 req/min ceiling, aggregating pages server-side before writing to the destination. Accounts with large candidate pools or multi-year employee histories should expect migration windows of several hours to multiple days depending on record volume and the number of object types being migrated.

  • 60 requests per minute rate limit requires throttling coordination

    Homerun enforces a strict 60 req/min rate limit on all API endpoints with no burst allowance. During migration, we throttle export calls to stay within this limit and monitor response headers for 429 status codes. For accounts with large record volumes, we chunk the export into time-bounded windows and iterate nightly to avoid hitting the ceiling. If you run active integrations during migration, coordinate with us to co-authorize a reduced request budget.

  • 2025 HR module scope verification required before migration

    Homerun introduced Employee records, Time Off, and document storage only with its 2025 HR module expansion. Older accounts may not have these modules active, meaning records were never created in the first place. We verify which modules were active during the period your data covers before scoping the migration. If you need historical Employee data that was never stored in Homerun, that data does not exist to migrate.

  • Custom picklist values must match BambooHR allowed options

    BambooHR enforces picklist value validation during import. If a Homerun custom field contains picklist values that do not exist in the corresponding BambooHR picklist field, the import rejects that record. We enumerate all picklist fields during scoping, compare the Homerun value set against the BambooHR allowed values, and extend the BambooHR picklist before migration where possible. Values with no matching option are flagged for your admin to resolve.

  • BambooHR ATS is a tiered add-on that may not be included in your plan

    Unlike Homerun where ATS is bundled across all tiers, BambooHR separates the ATS module as an add-on available primarily at the Advantage tier and above. If your BambooHR plan does not include the ATS module, Candidate records cannot be imported to the Jobs module. We verify your BambooHR plan tier during scoping and flag whether the ATS add-on is required to accommodate the migrating Candidate and Vacancy data.

Migration approach

Six steps for a successful Homerun to BambooHR data migration

  1. Migration scope discovery and HR module verification

    We audit your Homerun account across all active modules (ATS and/or HR), object inventory (Vacancies, Candidates, Employees, Time Off, Documents), custom field definitions, pipeline stage count, and historical record volume. We verify the HR module activation date to confirm which object types existed in your account before 2025. The discovery output is a written migration scope document with record counts per object, a list of any objects unavailable due to module restrictions, and a plan for resolving them.

  2. Destination schema design and BambooHR tier verification

    We design the BambooHR target schema based on your plan tier, verifying ATS module inclusion and job opening limits. We map each Homerun object to its BambooHR equivalent, configure custom fields with correct types and picklist values, and define the stage mapping for Vacancy pipelines. We also verify that your BambooHR plan supports any employee count requirements for the migration scope.

  3. API discovery and rate limit testing

    We run API discovery against your Homerun account to confirm read access for all scoped object types, test pagination behavior, and measure actual throughput against the 60 req/min ceiling. We identify any objects returning 403 responses (indicating tier restrictions) and escalate to your Homerun account team if needed. We also verify BambooHR API credentials and test write access for the target objects.

  4. Trial migration and reconciliation

    We run a full trial migration into your BambooHR sandbox (or a test environment if no sandbox exists) using a representative sample of records. We validate record counts, spot-check field mappings against the source, and confirm that picklist value validation passes without rejection. Your HR admin reviews the output and signs off the mapping before production migration begins. Any corrections happen here, not in production.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Jobs (Vacancies) first so that Candidate applications have a valid Job reference; Employees second; Time Off and Documents third; Candidates fourth (with Vacancy references resolved); User accounts fifth (for role and ownership mapping); Scorecards and Offers last. We throttle all reads to the 60 req/min limit, batch records for bulk insert into BambooHR where supported, and emit row-count reconciliation reports after each phase. Pending Time Off requests are flagged for your admin to action post-migration.

  6. Cutover, delta migration, and automation rebuild handoff

    We freeze Homerun writes 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 a written inventory of every Homerun workflow, email template, and automation requiring rebuild in BambooHR, along with recommended equivalents. We do not rebuild these as code inside the migration scope; that is a separate engagement for your BambooHR admin or implementation partner. We support a one-week hypercare window for reconciliation issues.

Platform deep dives

Context on both ends of the pair

Homerun logo

Homerun

Source

Strengths

  • Visual design tools for job postings and career pages that genuinely differentiate employer branding.
  • Strong customer satisfaction scores and positive reviews on independent platforms.
  • All-in-one ATS plus HR platform reduces the number of tools a small team needs to manage.
  • Clean, modern interface that reduces onboarding time for hiring managers and recruiters.

Weaknesses

  • Analytics and reporting capabilities lag behind enterprise HRMS platforms with dedicated BI tools.
  • API has no bulk export endpoint; all reads use paginated list endpoints at 60 req/min.
  • Rate limit of 60 requests per minute makes large migrations require careful throttling and chunking.
  • Feature set is best suited to small and mid-market teams; larger organizations with complex workflows may find gaps.
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?

Moderate HRMS migration. 3 of 7 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    3 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

    Homerun: 60 requests per minute per API key.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Homerun 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 two and four weeks for accounts under 5,000 candidates with no complex employee history or extensive custom fields. Migrations involving full Employee records, Time Off balances, multi-year candidate histories (over 10,000 records), or extensive custom field schemas extend to four to eight weeks because of API pagination overhead and the HR module scope verification required for older accounts.

Adjacent paths

Related migrations to explore

Ready when you are

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