Migrate your CVWarehouse data
CVWarehouse is a Belgium-based ATS built on 17 years of recruitment best practices, offering job posting, candidate management, and interview scheduling. It was acquired by BCS in 2024 and is best suited for mid-sized European organizations with multi-location or multi-brand hiring needs.
In its favor
Why people choose CVWarehouse
The signal that keeps CVWarehouse on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Belgian-origin ATS with 17+ years of recruitment-domain experience, used by hundreds of customers across 20+ countries in 10 languages — appealing to mid-market European organisations with multi-country hiring.
GDPR-compliant candidate engagement and portal tools (per-employer-brand privacy policy and cookie management) make it a defensible choice for EU organisations subject to data-protection scrutiny.
Multi-database layout supports separate talent pools per brand or location out of the box, which is harder to configure cleanly in flat ATSs.
Multi-posting to the customer's own careers site and external job boards is built in, removing the need for a separate sourcing layer.
Reviewers cite high uptime and a low-friction recruiter UI as reasons for long-term retention — multi-year zero-downtime reports surfaced in user reviews.
Per-feature and per-module pricing model causes cost to escalate as AI matching, multi-brand databases and advanced reporting are added — predictable all-inclusive pricing is not on offer.
Public REST/bulk-export API is not documented, making integrations with payroll, HRIS or BI platforms harder than at competitors like Greenhouse, Recruitee or Bullhorn.
Acquired by BCS in May 2024 — customers cite roadmap and long-term support uncertainty as a trigger to evaluate alternatives.
Feature breadth is described by some reviewers as excessive for smaller hiring teams; unused modules add complexity without value.
Competitors including Recruitee, Greenhouse, Breezy and Bullhorn surface more modern AI sourcing, candidate-matching and integration-marketplace capabilities than CVWarehouse exposes today.
Reasons to switch
Why people leave CVWarehouse
The recurring reasons buyers give for replacing CVWarehouse. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where CVWarehouse 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
CVWarehouse pricing overview
CVWarehouse uses a per-feature and per-user pricing model starting at approximately €50/month. Costs scale as organizations enable additional modules such as AI matching, multi-brand databases, and advanced reporting. Enterprise pricing is custom and negotiated directly with the vendor.
Starter
Tier 1 of 3
€50/month (starting, per feature)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on CVWarehouse's schedule — see our quote-based pricing →
What gets migrated
CVWarehouse object support
Object-by-object support for CVWarehouse migrations. Per-pair details surface during scoping.
Vacancies
Mapping requiredVacancies in CVWarehouse include job details, location, department, and a configurable Vacancy Template. We map these to the destination Jobs or Requisitions object and flag any custom template fields that require manual field-mapping during the scoping call.
Candidates
Mapping requiredCandidate profiles contain contact info, work history, education, and free-form notes. CVWarehouse stores candidates across separate databases per brand or location, so we run de-duplication across these pools before writing to the destination to prevent inflated candidate counts.
Applications
Mapping requiredAn Application links a Candidate to a Vacancy and tracks submission date and source channel. We map Applications to the destination's Jobs-to-Candidates association and preserve the application source for analytics in the new system.
Selection Rounds
Mapping requiredSelection Rounds define interview stages, reviewer assignments, and scoring within each Vacancy. We sequence them chronologically and map to the destination's pipeline stages, flagging any non-standard stage names that need a routing table.
Scorecards and Ratings
Mapping requiredInterviewer scorecards and structured ratings are stored per Selection Round. We map these to the destination's evaluation or rating object and note whether the destination supports structured scoring or only free-text feedback.
Attachments
Mapping requiredCVWarehouse stores CVs, cover letters, and portfolio files per Candidate or Application. We export these as binary blobs and write them to the destination's document attachment field, preserving the original filename and file type.
Vacancy Templates
Mapping requiredOrganizations that use Vacancy Templates to standardize job postings will have custom or shared template fields. These require explicit mapping during scoping since they are not standard across accounts.
Users and Roles
Mapping requiredRecruiters, hiring managers, and administrators have role-based access. We map Users to the destination's Owner or Assignee fields and flag any role names that do not have a direct equivalent in the target ATS.
Reports and Analytics
Not in this platformCVWarehouse reporting is UI-based and does not expose a documented analytics export API. We do not migrate built-in reports; instead we recommend configuring equivalent reports in the destination post-migration.
| Object | Support | Notes |
|---|---|---|
| Vacancies | Mapping required | Vacancies in CVWarehouse include job details, location, department, and a configurable Vacancy Template. We map these to the destination Jobs or Requisitions object and flag any custom template fields that require manual field-mapping during the scoping call. |
| Candidates | Mapping required | Candidate profiles contain contact info, work history, education, and free-form notes. CVWarehouse stores candidates across separate databases per brand or location, so we run de-duplication across these pools before writing to the destination to prevent inflated candidate counts. |
| Applications | Mapping required | An Application links a Candidate to a Vacancy and tracks submission date and source channel. We map Applications to the destination's Jobs-to-Candidates association and preserve the application source for analytics in the new system. |
| Selection Rounds | Mapping required | Selection Rounds define interview stages, reviewer assignments, and scoring within each Vacancy. We sequence them chronologically and map to the destination's pipeline stages, flagging any non-standard stage names that need a routing table. |
| Scorecards and Ratings | Mapping required | Interviewer scorecards and structured ratings are stored per Selection Round. We map these to the destination's evaluation or rating object and note whether the destination supports structured scoring or only free-text feedback. |
| Attachments | Mapping required | CVWarehouse stores CVs, cover letters, and portfolio files per Candidate or Application. We export these as binary blobs and write them to the destination's document attachment field, preserving the original filename and file type. |
| Vacancy Templates | Mapping required | Organizations that use Vacancy Templates to standardize job postings will have custom or shared template fields. These require explicit mapping during scoping since they are not standard across accounts. |
| Users and Roles | Mapping required | Recruiters, hiring managers, and administrators have role-based access. We map Users to the destination's Owner or Assignee fields and flag any role names that do not have a direct equivalent in the target ATS. |
| Reports and Analytics | Not in this platform | CVWarehouse reporting is UI-based and does not expose a documented analytics export API. We do not migrate built-in reports; instead we recommend configuring equivalent reports in the destination post-migration. |
Gotchas
What to watch for in CVWarehouse migrations
Issues we've hit on past CVWarehouse migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No documented public REST API for bulk exports
Separate databases per brand or location fragment candidate pools
Per-feature pricing creates tier ambiguity at migration time
Acquisition by BCS introduces roadmap uncertainty
Selection Round data depends on non-standard stage names
| Severity | Issue |
|---|---|
| High | No documented public REST API for bulk exports |
| High | Separate databases per brand or location fragment candidate pools |
| Medium | Per-feature pricing creates tier ambiguity at migration time |
| Medium | Acquisition by BCS introduces roadmap uncertainty |
| Low | Selection Round data depends on non-standard stage names |
Leaving CVWarehouse?
Where CVWarehouse customers move next
5 destinations CVWarehouse can migrate to.
How a CVWarehouse migration works
Four steps, CVWarehouse-specific
Connect
Not publicly documented into CVWarehouse. Scopes limited to read-only on the data we move.
Map
We translate CVWarehouse-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate CVWarehouse quirks before production.
Migrate
Full migration with CVWarehouse rate-limit handling. Rollback available throughout.
FAQ
CVWarehouse migration FAQ
Answers to the questions buyers ask most during CVWarehouse migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your CVWarehouse 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 CVWarehouse.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your CVWarehouse setup and destination — written quote back within a business day.