Migrate your Homerun data
Visual-first HR suite combining ATS with time-off management and document storage, built for teams that care about employer brand and candidate experience.
In its favor
Why people choose Homerun
The signal that keeps Homerun on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Visual-first job posting and career page builder that helps teams differentiate their employer brand and attract candidates who fit their culture.
Near-perfect customer satisfaction ratings on independent review platforms reflect a product that is easy to set up and consistently delivers on its core promise.
All-in-one ATS plus HR approach means teams manage the full employee lifecycle—hiring through onboarding and ongoing employment—in a single tool.
Amsterdam-based with a modern design philosophy, appealing to European teams and globally distributed companies that want a polished, clean interface.
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.
Reasons to switch
Why people leave Homerun
The recurring reasons buyers give for replacing Homerun. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Homerun fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Homerun pricing overview
Homerun pricing starts at approximately $53 per month for the Starter plan and scales with the number of employee seats and active job postings. Higher tiers unlock additional job slots, team members, and HR module features. Enterprise pricing is custom and negotiated based on organizational needs.
Starter
Tier 1 of 3
From ~$53/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Homerun's schedule — see our quote-based pricing →
What gets migrated
Homerun object support
Object-by-object support for Homerun migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCandidates and their application history are fully accessible via paginated API endpoints. We pull all candidate records with their pipeline stage assignments and preserve the full application timeline during migration.
Job Openings
Fully supportedJob Openings (vacancies) are well-structured in the API with configurable stages. We map each job's title, description, department, and pipeline configuration to the equivalent object in the destination HRMS.
Employees
Mapping requiredEmployee records are available in the API but were introduced with the 2025 HR module expansion. We handle name, email, role, department, start date, and employment status, mapping custom HR properties as needed.
Time Off
Mapping requiredTime-off balances and requests are migrated as current-state records with effective dates. Historical accrual patterns are mapped based on the destination system's accrual engine requirements.
Documents
Mapping requiredEmployee documents stored in Homerun HR are accessible via API. We export file metadata and content URLs, handling large files through chunked retrieval where needed.
Users
Fully supportedTeam members and user accounts are fully importable. We preserve role assignments and ownership relationships during migration so access controls map to equivalent roles in the destination.
Pipeline Stages
Mapping requiredPipeline stage names, ordering, and associated actions vary between Homerun accounts. We apply sequential stage mapping aligned with the destination pipeline, flagging any stages that exceed the target's maximum stage count.
Scorecards
Mapping requiredEvaluation scorecards and their ratings are exported with answer values that may not map 1:1 to the destination's rating schema. We normalize scores and preserve evaluator comments during import.
Offers
Mapping requiredOffer letters including compensation details, start dates, and conditional terms are extracted from Homerun and mapped into the destination's offer object. We handle formatting differences in salary and equity fields.
Custom Fields
Mapping requiredCustom fields on any object are accessible via API and appear with their field IDs and data types. We enumerate custom properties during scoping and build explicit value mappings for picklist, date, and numeric fields.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Candidates and their application history are fully accessible via paginated API endpoints. We pull all candidate records with their pipeline stage assignments and preserve the full application timeline during migration. |
| Job Openings | Fully supported | Job Openings (vacancies) are well-structured in the API with configurable stages. We map each job's title, description, department, and pipeline configuration to the equivalent object in the destination HRMS. |
| Employees | Mapping required | Employee records are available in the API but were introduced with the 2025 HR module expansion. We handle name, email, role, department, start date, and employment status, mapping custom HR properties as needed. |
| Time Off | Mapping required | Time-off balances and requests are migrated as current-state records with effective dates. Historical accrual patterns are mapped based on the destination system's accrual engine requirements. |
| Documents | Mapping required | Employee documents stored in Homerun HR are accessible via API. We export file metadata and content URLs, handling large files through chunked retrieval where needed. |
| Users | Fully supported | Team members and user accounts are fully importable. We preserve role assignments and ownership relationships during migration so access controls map to equivalent roles in the destination. |
| Pipeline Stages | Mapping required | Pipeline stage names, ordering, and associated actions vary between Homerun accounts. We apply sequential stage mapping aligned with the destination pipeline, flagging any stages that exceed the target's maximum stage count. |
| Scorecards | Mapping required | Evaluation scorecards and their ratings are exported with answer values that may not map 1:1 to the destination's rating schema. We normalize scores and preserve evaluator comments during import. |
| Offers | Mapping required | Offer letters including compensation details, start dates, and conditional terms are extracted from Homerun and mapped into the destination's offer object. We handle formatting differences in salary and equity fields. |
| Custom Fields | Mapping required | Custom fields on any object are accessible via API and appear with their field IDs and data types. We enumerate custom properties during scoping and build explicit value mappings for picklist, date, and numeric fields. |
Gotchas
What to watch for in Homerun migrations
Issues we've hit on past Homerun migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
60 requests per minute API rate limit
No bulk export endpoint
Analytics limitations documented in reviews
2025 HR module expansion changes migration scope
No public data on tier-specific API availability
| Severity | Issue |
|---|---|
| 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 |
Leaving Homerun?
Where Homerun customers move next
5 destinations Homerun can migrate to.
How a Homerun migration works
Four steps, Homerun-specific
Connect
API key (Bearer token) into Homerun. Scopes limited to read-only on the data we move.
Map
We translate Homerun-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Homerun quirks before production.
Migrate
Full migration with Homerun rate-limit handling. Rollback available throughout.
FAQ
Homerun migration FAQ
Answers to the questions buyers ask most during Homerun migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Homerun migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Homerun.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Homerun setup and destination — written quote back within a business day.