Migrate your Eploy data
UK-based ATS and talent acquisition platform with integrated onboarding, serving mid-to-enterprise organisations across all industries since 1998. Targets organisations with 150 to over 150,000 employees requiring end-to-end recruitment lifecycle management.
In its favor
Why people choose Eploy
The signal that keeps Eploy on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Highly configurable recruitment workflows that adapt to organisation-specific hiring processes without requiring code changes
Excellent customer service ratings (4.9/5) indicate strong implementation and ongoing support during and after migration
Regular platform updates are included in the subscription at no additional cost, keeping the system current without surprise charges
Integrates with over 1,000 job boards, HRIS systems, background screening services, and assessment tools out of the box
End-to-end hiring lifecycle from job requisition through onboarding in a single unified system reduces data fragmentation
Steep learning curve and unintuitive interface require significant training investment before teams become productive
Reporting and analytics are considered complex to configure and use, frustrating teams that need ad-hoc insights
API rate limits (10 req/sec, daily tier caps up to 50,000) can constrain large-scale data exports and bulk imports
Small feature additions often incur disproportionate costs, leading to frustration when simple customisations require premium upgrades
Clunky interface undermines campaign coordination for high-volume recruitment teams managing complex hiring pipelines
Reasons to switch
Why people leave Eploy
The recurring reasons buyers give for replacing Eploy. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Eploy 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
Eploy pricing overview
Eploy uses a flat-rate monthly pricing model starting at approximately £695 per month for the entry tier. Pricing is quote-driven for higher tiers and scales with organisation size, hiring volume, and selected modules. No free tier is available and pricing is not self-serve.
Standard
Tier 1 of 3
£695/month (flat rate)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Eploy's schedule — see our quote-based pricing →
What gets migrated
Eploy object support
Object-by-object support for Eploy migrations. Per-pair details surface during scoping.
Jobs/Job Requisitions
Fully supportedJob requisitions in Eploy include title, department, location, salary bands, and workflow assignment. We map these 1:1 and preserve the job-to-workflow linkage. Custom job fields are supported via mapping.
Candidates
Fully supportedCandidate records contain contact details, application history, skills, notes, and status. We migrate candidates with full application history and preserve the link back to the originating job. Duplicate detection logic runs at import time.
Workflow Stages
Mapping requiredEploy's workflow stages are customisable per organisation. We capture the ordered stage names and transition timestamps as a separate audit object, mapping stage names to the destination platform's equivalent stages.
Hiring Manager Portals
Mapping requiredHiring manager assignments tie specific users to jobs and workflow stages. We migrate these as Owner/User assignment records and flag any role-based permissions that may not translate to the destination schema.
Offers
Fully supportedOffer records include salary, start date, role details, and e-signature status. We migrate active offers and preserve e-signature audit trails where available via the API.
Onboarding Records
Mapping requiredOnboarding data includes new hire information, reference collection, contract status, and compliance documents. Some of these live in a separate onboarding module; we migrate what is accessible via API and flag gaps for manual verification.
Employee Referrals
Mapping requiredReferral records link an employee to a referred candidate and include reward status. We preserve the referral attribution and map referral sources to the destination's equivalent field.
Talent Pools
Mapping requiredTalent pools are saved candidate collections used for future roles. We migrate pool memberships with pool names and preserve the candidate-to-pool association as a tag or segment.
Custom Properties
Mapping requiredOrganisations add custom fields to jobs, candidates, and other objects. We detect and map custom property schemas during scoping, then create corresponding fields in the destination or collapse them into structured notes.
Assessments
Mapping requiredAssessment scores and results attach to candidate records. We migrate available assessment data as structured fields where the API exposes them; visual scores may require mapping to text equivalents.
Documents/Attachments
Mapping requiredResumes, cover letters, and compliance documents attach to candidates and jobs. We download and re-upload documents as binary blobs, preserving filenames and associated record links.
Communication History
Mapping requiredEmail and SMS threads tied to candidates are stored in Eploy. We migrate email content and timestamps as conversation records, though formatting may flatten in transit.
| Object | Support | Notes |
|---|---|---|
| Jobs/Job Requisitions | Fully supported | Job requisitions in Eploy include title, department, location, salary bands, and workflow assignment. We map these 1:1 and preserve the job-to-workflow linkage. Custom job fields are supported via mapping. |
| Candidates | Fully supported | Candidate records contain contact details, application history, skills, notes, and status. We migrate candidates with full application history and preserve the link back to the originating job. Duplicate detection logic runs at import time. |
| Workflow Stages | Mapping required | Eploy's workflow stages are customisable per organisation. We capture the ordered stage names and transition timestamps as a separate audit object, mapping stage names to the destination platform's equivalent stages. |
| Hiring Manager Portals | Mapping required | Hiring manager assignments tie specific users to jobs and workflow stages. We migrate these as Owner/User assignment records and flag any role-based permissions that may not translate to the destination schema. |
| Offers | Fully supported | Offer records include salary, start date, role details, and e-signature status. We migrate active offers and preserve e-signature audit trails where available via the API. |
| Onboarding Records | Mapping required | Onboarding data includes new hire information, reference collection, contract status, and compliance documents. Some of these live in a separate onboarding module; we migrate what is accessible via API and flag gaps for manual verification. |
| Employee Referrals | Mapping required | Referral records link an employee to a referred candidate and include reward status. We preserve the referral attribution and map referral sources to the destination's equivalent field. |
| Talent Pools | Mapping required | Talent pools are saved candidate collections used for future roles. We migrate pool memberships with pool names and preserve the candidate-to-pool association as a tag or segment. |
| Custom Properties | Mapping required | Organisations add custom fields to jobs, candidates, and other objects. We detect and map custom property schemas during scoping, then create corresponding fields in the destination or collapse them into structured notes. |
| Assessments | Mapping required | Assessment scores and results attach to candidate records. We migrate available assessment data as structured fields where the API exposes them; visual scores may require mapping to text equivalents. |
| Documents/Attachments | Mapping required | Resumes, cover letters, and compliance documents attach to candidates and jobs. We download and re-upload documents as binary blobs, preserving filenames and associated record links. |
| Communication History | Mapping required | Email and SMS threads tied to candidates are stored in Eploy. We migrate email content and timestamps as conversation records, though formatting may flatten in transit. |
Gotchas
What to watch for in Eploy migrations
Issues we've hit on past Eploy migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limits cap daily call volumes per tier
API keys are tied to individual user records
Onboarding module data may live in a separate schema
Custom workflow stages require mapping table creation
Document attachments require separate download-then-upload passes
| Severity | Issue |
|---|---|
| High | API rate limits cap daily call volumes per tier |
| High | API keys are tied to individual user records |
| Medium | Onboarding module data may live in a separate schema |
| Medium | Custom workflow stages require mapping table creation |
| Low | Document attachments require separate download-then-upload passes |
Leaving Eploy?
Where Eploy customers move next
5 destinations Eploy can migrate to.
How a Eploy migration works
Four steps, Eploy-specific
Connect
OAuth 2.0 with API keys tied to user records into Eploy. Scopes limited to read-only on the data we move.
Map
We translate Eploy-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Eploy quirks before production.
Migrate
Full migration with Eploy rate-limit handling. Rollback available throughout.
FAQ
Eploy migration FAQ
Answers to the questions buyers ask most during Eploy migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Eploy 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 Eploy.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Eploy setup and destination — written quote back within a business day.