Migrate your eArcu data
Talent acquisition suite covering career sites, applicant tracking, assessments, and onboarding for enterprise organisations across multiple continents.
In its favor
Why people choose eArcu
The signal that keeps eArcu on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Highly configurable candidate-facing experience lets enterprise brands (British Airways, Volkswagen Financial, Virgin Active) present a hiring process aligned to their culture and employer brand.
Built-in assessment suite with cognitive tests, personality questionnaires, and situational judgement tests reduces the need for third-party screening vendors.
Responsive, mobile-adaptive career portal keeps candidates engaged across devices and provides real-time application status tracking throughout the hiring process.
Social media job distribution to LinkedIn, Facebook, and Twitter centralises recruitment marketing activity within a single platform rather than across disconnected tools.
End-to-end coverage from career sites through onboarding reduces the number of integrations, suppliers, and overall total cost for talent acquisition operations.
After the PageUp brand consolidation following the EQT acquisition, some customers evaluate alternatives when their contract renewal aligns with the rebrand rollout timeline.
Customers seeking a broader HCM footprint beyond talent acquisition eventually consolidate onto platforms like Workday or SAP SuccessFactors that offer payroll and core HR in a single suite.
Organisations with complex multi-country hiring requirements report that localisation and compliance features for certain regions lag behind purpose-built global HR platforms.
Reasons to switch
Why people leave eArcu
The recurring reasons buyers give for replacing eArcu. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where eArcu 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
eArcu pricing overview
eArcu does not publish pricing on its website. Plans are offered on a per-seat or per-module basis with custom enterprise quotes that vary by organisation size, feature scope, and deployment region. Annual contract terms are standard.
Enterprise
Tier 1 of 3
Custom (per-request)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on eArcu's schedule — see our quote-based pricing →
What gets migrated
eArcu object support
Object-by-object support for eArcu migrations. Per-pair details surface during scoping.
Candidates
Mapping requiredCandidate records carry name, contact details, work history, and custom profile fields. We extract all standard fields and map any custom properties to the destination schema. Assessment scores and tags stored on the candidate record are preserved as custom fields in the target system.
Job Requisitions
Mapping requiredRequisitions include title, department, location, employment type, and pipeline assignment. We map requisition metadata and preserve any custom approval workflow configurations by documenting them as a separate step in the migration runbook.
Applications
Fully supportedApplication records link a Candidate to a Requisition with timestamps for each stage transition. These map directly to standard application objects in most destination ATS platforms.
Hiring Stages / Pipeline Stages
Mapping requiredeArcu supports configurable pipeline stages per requisition. We extract the full stage history per application including stage-entry dates, which we translate to the destination pipeline's stage model.
Assessments
Mapping requiredCognitive test results, personality questionnaire scores, and situational judgement data are stored as linked records attached to the candidate. We export raw scores and assessment types; mapping to the destination's assessment object depends on whether the target system has an equivalent evaluation module.
Career Site Content
Mapping requiredCareer portal pages, job board widgets, and branding assets are HTML and CSS configurations rather than structured database records. We export the content export package where available and flag any assets that require re-authoring in the destination platform.
Documents / Attachments
Mapping requiredCVs, cover letters, and supporting files attached to candidates or applications are binary blobs stored in eArcu's document store. We extract and re-upload these to the destination ATS, preserving original filenames and association to the correct candidate record.
Hiring Team / Users
Mapping requiredUser accounts, roles, and permissions define who can view or act on requisitions and candidates. We export the user roster with role assignments and map to the destination's permission model.
Offers
Mapping requiredOffer records include compensation details, start dates, and approval status. Where the destination ATS has a separate offer object, we map fields directly; otherwise we attach offer data as custom properties on the application record.
Onboarding Packages
Not in this platformAnimated onboarding content and structured onboarding task lists are platform-native configurations that cannot be meaningfully transferred to a different ATS. We export the package structure as a reference document for rebuilding manually in the destination system.
| Object | Support | Notes |
|---|---|---|
| Candidates | Mapping required | Candidate records carry name, contact details, work history, and custom profile fields. We extract all standard fields and map any custom properties to the destination schema. Assessment scores and tags stored on the candidate record are preserved as custom fields in the target system. |
| Job Requisitions | Mapping required | Requisitions include title, department, location, employment type, and pipeline assignment. We map requisition metadata and preserve any custom approval workflow configurations by documenting them as a separate step in the migration runbook. |
| Applications | Fully supported | Application records link a Candidate to a Requisition with timestamps for each stage transition. These map directly to standard application objects in most destination ATS platforms. |
| Hiring Stages / Pipeline Stages | Mapping required | eArcu supports configurable pipeline stages per requisition. We extract the full stage history per application including stage-entry dates, which we translate to the destination pipeline's stage model. |
| Assessments | Mapping required | Cognitive test results, personality questionnaire scores, and situational judgement data are stored as linked records attached to the candidate. We export raw scores and assessment types; mapping to the destination's assessment object depends on whether the target system has an equivalent evaluation module. |
| Career Site Content | Mapping required | Career portal pages, job board widgets, and branding assets are HTML and CSS configurations rather than structured database records. We export the content export package where available and flag any assets that require re-authoring in the destination platform. |
| Documents / Attachments | Mapping required | CVs, cover letters, and supporting files attached to candidates or applications are binary blobs stored in eArcu's document store. We extract and re-upload these to the destination ATS, preserving original filenames and association to the correct candidate record. |
| Hiring Team / Users | Mapping required | User accounts, roles, and permissions define who can view or act on requisitions and candidates. We export the user roster with role assignments and map to the destination's permission model. |
| Offers | Mapping required | Offer records include compensation details, start dates, and approval status. Where the destination ATS has a separate offer object, we map fields directly; otherwise we attach offer data as custom properties on the application record. |
| Onboarding Packages | Not in this platform | Animated onboarding content and structured onboarding task lists are platform-native configurations that cannot be meaningfully transferred to a different ATS. We export the package structure as a reference document for rebuilding manually in the destination system. |
Gotchas
What to watch for in eArcu migrations
Issues we've hit on past eArcu migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Post-acquisition brand consolidation creates schema ambiguity
No publicly documented API limits export feasibility
Onboarding content cannot be programmatically migrated
| Severity | Issue |
|---|---|
| High | Post-acquisition brand consolidation creates schema ambiguity |
| Medium | No publicly documented API limits export feasibility |
| Low | Onboarding content cannot be programmatically migrated |
Leaving eArcu?
Where eArcu customers move next
5 destinations eArcu can migrate to.
How a eArcu migration works
Four steps, eArcu-specific
Connect
Not publicly documented into eArcu. Scopes limited to read-only on the data we move.
Map
We translate eArcu-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate eArcu quirks before production.
Migrate
Full migration with eArcu rate-limit handling. Rollback available throughout.
FAQ
eArcu migration FAQ
Answers to the questions buyers ask most during eArcu migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your eArcu 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 eArcu.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your eArcu setup and destination — written quote back within a business day.