Migrate your eBoss data
Cloud-based HRMS platform for small and mid-sized businesses managing employee records, payroll, time tracking, and recruitment workflows.
In its favor
Why people choose eBoss
The signal that keeps eBoss on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Affordable price point from £37.44/user/month (~US$60/month) compared with Workable, Recruiterbox, and Bullhorn — eBoss explicitly targets UK and Commonwealth recruitment agencies on tight budgets.
All features included with no upgrades or add-ons — AI matching, analytics, job boards, GDPR tooling, CV parsing, semantic search ship in the base subscription.
Native job board, social network, website, email, VOIP, and SMS integrations cover the recruiter's daily comms stack without a separate connector spend.
Built-in GDPR tooling appeals to UK/EU staffing firms that must demonstrate candidate consent and data audit trails.
Cloud-based with mobile-friendly access and a small support team that reviewers consistently call out as responsive.
Interface is described in reviews as old-fashioned compared to Workable, Recruiterbox, or Hire by Google — visual modernization is a common ask.
No public API — custom integrations are bespoke per customer, limiting the ability to wire eBoss into modern HRIS or BI stacks.
English-only across all modules, ruling out multilingual recruitment teams in continental Europe.
Scope is recruitment-only — no performance reviews, multi-country payroll, benefits admin, or learning modules — so teams growing into full HRMS outgrow it.
Smaller global footprint than Bullhorn or Workable means fewer integrator partners and a thinner community for shared best practices outside the UK.
Reasons to switch
Why people leave eBoss
The recurring reasons buyers give for replacing eBoss. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where eBoss 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
eBoss pricing overview
eBoss charges per user per month with a starting rate of £37.44/user/month (~US$60/month) and all features included in the single plan — no upgrade tiers or feature-gating. Free trial available; no free tier.
All-features plan
Tier 1 of 1
£37.44/user/month (~US$60/month)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on eBoss's schedule — see our quote-based pricing →
What gets migrated
eBoss object support
Object-by-object support for eBoss migrations. Per-pair details surface during scoping.
Candidates
Fully supportedPrimary object. Captures CV, contact details, parsed skills, status, and consent flags. We export the full candidate record with parsed-CV metadata and re-attach raw CV binaries during import.
Jobs
Fully supportedJob records carry title, client, status, requirements, and source job board. We map Jobs to destination requisitions and preserve client-to-job linkage.
Clients (Companies)
Fully supportedAgency clients with hiring authority and billing details. We map Companies to destination account/company records and preserve client-to-job-to-candidate chains.
Contacts
Fully supportedHiring manager and client-side contacts associated with Companies. We preserve relationship links during migration.
Activities (Calls, Emails, SMS)
Mapping requiredVOIP, email, and SMS history attaches to Candidates and Contacts. We export activity logs but reply-chain continuity may not survive into all destinations.
Custom Fields
Mapping requiredCustom fields are supported but no API documentation publishes the schema. We discover them during data profiling and map per-field.
GDPR Consents
Mapping requiredConsent records and data-subject request handling are tracked per Candidate. We preserve consent timestamps and source to maintain regulatory compliance after cutover.
Users
Mapping requiredRecruiter accounts with role-based access. We map users to destination identity systems by email and preserve ownership assignments.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Primary object. Captures CV, contact details, parsed skills, status, and consent flags. We export the full candidate record with parsed-CV metadata and re-attach raw CV binaries during import. |
| Jobs | Fully supported | Job records carry title, client, status, requirements, and source job board. We map Jobs to destination requisitions and preserve client-to-job linkage. |
| Clients (Companies) | Fully supported | Agency clients with hiring authority and billing details. We map Companies to destination account/company records and preserve client-to-job-to-candidate chains. |
| Contacts | Fully supported | Hiring manager and client-side contacts associated with Companies. We preserve relationship links during migration. |
| Activities (Calls, Emails, SMS) | Mapping required | VOIP, email, and SMS history attaches to Candidates and Contacts. We export activity logs but reply-chain continuity may not survive into all destinations. |
| Custom Fields | Mapping required | Custom fields are supported but no API documentation publishes the schema. We discover them during data profiling and map per-field. |
| GDPR Consents | Mapping required | Consent records and data-subject request handling are tracked per Candidate. We preserve consent timestamps and source to maintain regulatory compliance after cutover. |
| Users | Mapping required | Recruiter accounts with role-based access. We map users to destination identity systems by email and preserve ownership assignments. |
Gotchas
What to watch for in eBoss migrations
Issues we've hit on past eBoss migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API blocks programmatic extraction
GDPR consent records must be preserved with original timestamps
Reply-chain continuity for VOIP and SMS may not survive
| Severity | Issue |
|---|---|
| High | No public API blocks programmatic extraction |
| High | GDPR consent records must be preserved with original timestamps |
| Medium | Reply-chain continuity for VOIP and SMS may not survive |
Leaving eBoss?
Where eBoss customers move next
5 destinations eBoss can migrate to.
How a eBoss migration works
Four steps, eBoss-specific
Connect
Not applicable — no public API into eBoss. Scopes limited to read-only on the data we move.
Map
We translate eBoss-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate eBoss quirks before production.
Migrate
Full migration with eBoss rate-limit handling. Rollback available throughout.
FAQ
eBoss migration FAQ
Answers to the questions buyers ask most during eBoss migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your eBoss 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 eBoss.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your eBoss setup and destination — written quote back within a business day.