Migrate your RECRU data
AI-driven recruiting platform that parses CVs and matches candidates beyond keyword matching, aimed at SMBs and mid-market teams seeking faster placements.
In its favor
Why people choose RECRU
The signal that keeps RECRU on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
RECRU's AI agent matches candidates from natural-language job descriptions, reducing time spent manually searching resumes and LinkedIn for qualified applicants.
The platform combines ATS, recruiting CRM, and workflow automation in one subscription, avoiding the need for multiple disconnected tools at the SMB price point.
A 14-day free trial with no credit card required lets small teams evaluate the full feature set before committing to a paid plan.
European pricing in euros appeals to companies outside the US seeking a recruiting tool with GDPR-compliant data handling built into the product.
Strong customer service ratings and responsive helpdesk staff reduce friction during onboarding and day-to-day operational issues.
Automatic reply templates and email communication tools are difficult to configure, leading to repetitive manual outreach when automation fails.
Some users report UI responsiveness issues on certain pages and occasional glitches during high-volume recruitment periods.
Teams outgrow the platform when they need deeper integrations with HRIS, payroll, or background-check vendors not currently supported.
Reasons to switch
Why people leave RECRU
The recurring reasons buyers give for replacing RECRU. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where RECRU 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
RECRU pricing overview
RECRU is priced at a flat per-month rate starting at €39, positioning it in the SMB-to-mid-market range for recruiting software. No per-user pricing is listed in public materials, suggesting a single-tier or feature-gated model rather than seat-based billing.
Standard
Tier 1 of 1
€39.00 per month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on RECRU's schedule — see our quote-based pricing →
What gets migrated
RECRU object support
Object-by-object support for RECRU migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCandidate profiles in RECRU include parsed CV data, AI-generated match scores, application history, and custom properties. We map all standard fields including name, email, phone, skills, and work history. AI scores are preserved as a custom float field in the destination.
Jobs
Fully supportedJob requisitions in RECRU carry title, description, department, location, salary range, and hiring pipeline stages. We migrate Jobs as-is and preserve the pipeline stage order from the source account.
Workflows
Mapping requiredRECRU's workflow automation rules are JSON-backed in the database but the UI exposes them as a visual rule builder. We export the rule structure and attempt to replicate the logic in the destination ATS, though complex multi-step conditional branches may collapse into a single automation step.
Users
Fully supportedUser accounts in RECRU carry name, email, role, and team assignment. We migrate active user records and map them to corresponding owner fields on Candidates and Jobs.
Custom Fields
Mapping requiredCustom candidate properties added by the tenant are migrated as key-value pairs. We extract the field name and type and create equivalent custom fields in the destination where supported, falling back to a JSON blob if the destination schema does not allow arbitrary custom properties.
Communications
Mapping requiredEmail threads and message logs attached to candidate records are migrated as a flattened activity log. The original thread structure is not preserved in most destination systems, so we render each message as a timestamped note entry.
Interviews
Mapping requiredInterview events stored in RECRU carry date, interviewer, and outcome. We map these to calendar or event objects in the destination where the target ATS supports interview scheduling records.
Tags
Fully supportedTags applied to candidates in RECRU are migrated as flat label arrays attached to the candidate record in the destination.
Hiring Pipeline Stages
Mapping requiredPipeline stage names and order are migrated. If the destination uses a predefined pipeline structure, we map RECRU stages to the closest equivalent stage name and flag any stages that have no clear destination equivalent.
Scorecards
Mapping requiredEvaluation scorecards submitted by interviewers are migrated as JSON objects attached to the candidate record. Destination systems that do not natively support scorecard objects will receive them as structured notes.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Candidate profiles in RECRU include parsed CV data, AI-generated match scores, application history, and custom properties. We map all standard fields including name, email, phone, skills, and work history. AI scores are preserved as a custom float field in the destination. |
| Jobs | Fully supported | Job requisitions in RECRU carry title, description, department, location, salary range, and hiring pipeline stages. We migrate Jobs as-is and preserve the pipeline stage order from the source account. |
| Workflows | Mapping required | RECRU's workflow automation rules are JSON-backed in the database but the UI exposes them as a visual rule builder. We export the rule structure and attempt to replicate the logic in the destination ATS, though complex multi-step conditional branches may collapse into a single automation step. |
| Users | Fully supported | User accounts in RECRU carry name, email, role, and team assignment. We migrate active user records and map them to corresponding owner fields on Candidates and Jobs. |
| Custom Fields | Mapping required | Custom candidate properties added by the tenant are migrated as key-value pairs. We extract the field name and type and create equivalent custom fields in the destination where supported, falling back to a JSON blob if the destination schema does not allow arbitrary custom properties. |
| Communications | Mapping required | Email threads and message logs attached to candidate records are migrated as a flattened activity log. The original thread structure is not preserved in most destination systems, so we render each message as a timestamped note entry. |
| Interviews | Mapping required | Interview events stored in RECRU carry date, interviewer, and outcome. We map these to calendar or event objects in the destination where the target ATS supports interview scheduling records. |
| Tags | Fully supported | Tags applied to candidates in RECRU are migrated as flat label arrays attached to the candidate record in the destination. |
| Hiring Pipeline Stages | Mapping required | Pipeline stage names and order are migrated. If the destination uses a predefined pipeline structure, we map RECRU stages to the closest equivalent stage name and flag any stages that have no clear destination equivalent. |
| Scorecards | Mapping required | Evaluation scorecards submitted by interviewers are migrated as JSON objects attached to the candidate record. Destination systems that do not natively support scorecard objects will receive them as structured notes. |
Gotchas
What to watch for in RECRU migrations
Issues we've hit on past RECRU migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
GDPR-compliant deletion requests run inside RECRU before migration
Workflow automation rules may not map 1:1 to destination ATS
AI-generated match scores are proprietary and destination-agnostic
| Severity | Issue |
|---|---|
| Medium | GDPR-compliant deletion requests run inside RECRU before migration |
| Medium | Workflow automation rules may not map 1:1 to destination ATS |
| Low | AI-generated match scores are proprietary and destination-agnostic |
Leaving RECRU?
Where RECRU customers move next
5 destinations RECRU can migrate to.
How a RECRU migration works
Four steps, RECRU-specific
Connect
API token issued from the RECRU admin console. Specific OAuth or auth-header conventions are documented within the API page at recruhr.com/api/. into RECRU. Scopes limited to read-only on the data we move.
Map
We translate RECRU-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate RECRU quirks before production.
Migrate
Full migration with RECRU rate-limit handling. Rollback available throughout.
FAQ
RECRU migration FAQ
Answers to the questions buyers ask most during RECRU migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your RECRU 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 RECRU.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your RECRU setup and destination — written quote back within a business day.