Migrate your HR-ON data
European HR management platform focused on employee records, document workflows, and onboarding. Targets small to mid-sized organizations in German-speaking markets seeking structured HR administration tools.
In its favor
Why people choose HR-ON
The signal that keeps HR-ON on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small businesses in German-speaking markets choose HR-ON for its localized HR workflows and Danish language support out of the box.
Organizations with straightforward employee record needs appreciate the structured API that makes data extraction predictable for migrations.
Companies moving from spreadsheets or legacy HR systems cite HR-ON's intuitive design as a reason for initial adoption.
Teams seeking an affordable HRMS without the complexity of enterprise platforms select HR-ON for its focused feature set.
Organizations already using other HR-ON products (onboarding, payroll) extend their stack to HR-ON for integration consistency.
Conflicting public reporting on API availability — some sources say HR-ON has an open API while others state HR-ON Recruit specifically does not. Buyers needing certainty on programmatic access must confirm with HR-ON directly before contracting.
Suite plan at €317/month is materially more expensive than Recruit at €167/month — companies that only need ATS functionality may find the upsell to the full Suite expensive.
European focus means thinner partner network in North America and APAC compared with global HRIS providers.
Reporting and analytics depth lag mid-market HRIS leaders like BambooHR and HiBob.
Recruiting-focused entry point means HR-ON requires the Suite tier to cover onboarding and ongoing HR processes.
Reasons to switch
Why people leave HR-ON
The recurring reasons buyers give for replacing HR-ON. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where HR-ON 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
HR-ON pricing overview
HR-ON is a Danish HR vendor based in Odense with transparent pricing: Recruit (the ATS plan) starts at €167/month and Suite (the full HR + recruit + wellbeing stack) starts at €317/month. Setup is free and includes career-page configuration. Both plans are billed monthly; multilingual support (English, Danish, German, Japanese, Spanish, French) is included. Enterprise-tier pricing for larger headcounts is quoted via HR-ON sales.
Recruit
Tier 1 of 2
From €167 / month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on HR-ON's schedule — see our quote-based pricing →
What gets migrated
HR-ON object support
Object-by-object support for HR-ON migrations. Per-pair details surface during scoping.
Employees
Fully supportedHR-ON exposes a POST /v1/staff/employees endpoint with systemFields and standard employee properties. We read this directly via JWT auth and map fields 1:1 to the destination Employee object.
Document Templates
Mapping requiredHR-ON stores document templates with fields including name, description, documentType, dateFormat, and language (da_DK, en_US). We map documentType and language to the destination's template schema, but dateFormat handling varies by target platform.
Custom Fields
Mapping requiredHR-ON supports custom properties on Employees. We extract all non-systemFields and map them to the destination's custom field schema, flagging any with incompatible data types (e.g., multi-select vs. text) during the mapping phase.
Organizational Structure
Mapping requiredHR-ON stores org metadata within systemFields on Employee records rather than as separate objects. We parse these and reconstruct departments or reporting relationships in the destination based on field contents.
Users
Mapping requiredHR-ON user accounts map to the destination Users object. Role and permission structures differ between platforms, so we map default roles and flag any HR-ON-specific permissions that require manual reconfiguration.
Documents
Mapping requiredHR-ON generates documents via templates and stores them with dateFormat and language metadata. We export these as binary blobs or PDF links and associate them with the relevant Employee record in the destination.
Date Metadata
Mapping requiredHR-ON stores dates in flexible formats (20-07-2021, 20/07/2021, 2021-07-20, July 20, 2021). We normalize all dates to ISO 8601 before loading into the destination system.
Language Preferences
Fully supportedHR-ON explicitly stores language at da_DK (Danish) and en_US (English) per template and employee. We carry this through to the destination to preserve localized content rendering.
| Object | Support | Notes |
|---|---|---|
| Employees | Fully supported | HR-ON exposes a POST /v1/staff/employees endpoint with systemFields and standard employee properties. We read this directly via JWT auth and map fields 1:1 to the destination Employee object. |
| Document Templates | Mapping required | HR-ON stores document templates with fields including name, description, documentType, dateFormat, and language (da_DK, en_US). We map documentType and language to the destination's template schema, but dateFormat handling varies by target platform. |
| Custom Fields | Mapping required | HR-ON supports custom properties on Employees. We extract all non-systemFields and map them to the destination's custom field schema, flagging any with incompatible data types (e.g., multi-select vs. text) during the mapping phase. |
| Organizational Structure | Mapping required | HR-ON stores org metadata within systemFields on Employee records rather than as separate objects. We parse these and reconstruct departments or reporting relationships in the destination based on field contents. |
| Users | Mapping required | HR-ON user accounts map to the destination Users object. Role and permission structures differ between platforms, so we map default roles and flag any HR-ON-specific permissions that require manual reconfiguration. |
| Documents | Mapping required | HR-ON generates documents via templates and stores them with dateFormat and language metadata. We export these as binary blobs or PDF links and associate them with the relevant Employee record in the destination. |
| Date Metadata | Mapping required | HR-ON stores dates in flexible formats (20-07-2021, 20/07/2021, 2021-07-20, July 20, 2021). We normalize all dates to ISO 8601 before loading into the destination system. |
| Language Preferences | Fully supported | HR-ON explicitly stores language at da_DK (Danish) and en_US (English) per template and employee. We carry this through to the destination to preserve localized content rendering. |
Gotchas
What to watch for in HR-ON migrations
Issues we've hit on past HR-ON migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No bulk export endpoint forces sequential reads
Date format normalization required before import
Language-specific document types may not map directly
| Severity | Issue |
|---|---|
| High | No bulk export endpoint forces sequential reads |
| Medium | Date format normalization required before import |
| Low | Language-specific document types may not map directly |
Leaving HR-ON?
Where HR-ON customers move next
5 destinations HR-ON can migrate to.
How a HR-ON migration works
Four steps, HR-ON-specific
Connect
HR-ON's website references an open API for IT staff to set up integrations between HR-ON and other systems; auth specifics are confirmed with HR-ON during scoping. Multiple reviewer sources note conflicting information about API availability per product line (HR-ON Recruit specifically), so the API surface is verified per customer's plan. into HR-ON. Scopes limited to read-only on the data we move.
Map
We translate HR-ON-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate HR-ON quirks before production.
Migrate
Full migration with HR-ON rate-limit handling. Rollback available throughout.
FAQ
HR-ON migration FAQ
Answers to the questions buyers ask most during HR-ON migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your HR-ON 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 HR-ON.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your HR-ON setup and destination — written quote back within a business day.