Migrate your Jobtoolz data
Lightweight Belgian ATS built for SME recruitment, with employer branding and candidate tracking under one flat-rate plan. Most useful for teams that need to publish careers pages and track applicants without a complex enterprise feature stack.
In its favor
Why people choose Jobtoolz
The signal that keeps Jobtoolz on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Single flat-rate pricing removes budget negotiation friction for SMEs evaluating multiple ATS platforms simultaneously.
Employer branding tools including a careers site builder are included without requiring a separate product tier or integration.
Customers in government and public sector cite the tool as super user-friendly and meeting all their needs out of the box, per customer testimonials on the Jobtoolz website.
Candidate tracking from initial application through to hire is managed in one platform without requiring third-party plugins.
Integration with Jobtoolz's content API lets development teams build a custom front-end while HR teams continue using the back-end.
The platform is described by at least one reviewer as not yet fully up to speed with feature depth available in competing ATS platforms.
Role templates and customization options are limited compared to enterprise ATS solutions, restricting teams with highly specialized workflows.
With only around 3,000 users across 5 countries, the partner and integration ecosystem is narrower than global ATS players.
Some customers report the ATS portion of the platform lags behind the employer branding tools in feature maturity.
As a Belgian-founded product, documentation and support are stronger during European business hours, creating response delays for US and APAC teams.
Reasons to switch
Why people leave Jobtoolz
The recurring reasons buyers give for replacing Jobtoolz. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Jobtoolz 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
Jobtoolz pricing overview
Jobtoolz uses a single flat-rate pricing model with no tiered plans. The price is approximately €231 per month as a flat rate, with all features available to all users from day one. This model benefits teams that want full platform access without evaluating which tier includes which feature, though it offers no lower-cost entry point for small teams with minimal hiring volume.
Standard Plan
Tier 1 of 1
~€231/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 Jobtoolz's schedule — see our quote-based pricing →
What gets migrated
Jobtoolz object support
Object-by-object support for Jobtoolz migrations. Per-pair details surface during scoping.
Candidates
Mapping requiredCandidates are the core records in Jobtoolz. We export candidate lists to CSV via the built-in export function and map them to Contact or Candidate objects in the destination ATS. Custom candidate properties are preserved as custom fields with value mapping where schema differs.
Applications
Mapping requiredApplications link a Candidate to a Vacancy and store stage history. We map the Application status to the destination's pipeline stage concept, noting that Jobtoolz stages are user-defined and may not map 1:1 to standard ATS stage labels.
Vacancies
Mapping requiredVacancies are the job posting objects in Jobtoolz. We map Vacancy fields (title, department, location, employment type, description) to the destination's Job or Position object. Custom vacancy fields require explicit field-level mapping.
Pipeline Stages
Mapping requiredJobtoolz allows custom pipeline stage names and counts. We capture the full stage sequence during scoping and reconstruct it in the destination, merging any stages that exceed the target platform's maximum.
Custom Candidate Fields
Mapping requiredJobtoolz supports custom fields on candidate records. We export the field schema, preserve all values, and recreate the fields as custom properties in the destination ATS, flagging any type mismatches (e.g. date vs. text).
Documents and Attachments
Mapping requiredResume and cover letter attachments associated with candidates can be exported. We download attachments via the authenticated session and re-attach them to the corresponding candidate record in the destination platform.
Employer Branding Content
Fully supportedCompany branding assets, career site content, and job ad templates are managed via the Jobtoolz Content API. This API is fully authenticated with Bearer tokens, and we migrate these as structured content blocks compatible with most destination careers page builders.
Users and Team Members
Mapping requiredWe migrate team member accounts and map them to users in the destination ATS. Role and permission structures differ between platforms, so we assign default recruiter roles and flag any accounts that require elevated permissions.
| Object | Support | Notes |
|---|---|---|
| Candidates | Mapping required | Candidates are the core records in Jobtoolz. We export candidate lists to CSV via the built-in export function and map them to Contact or Candidate objects in the destination ATS. Custom candidate properties are preserved as custom fields with value mapping where schema differs. |
| Applications | Mapping required | Applications link a Candidate to a Vacancy and store stage history. We map the Application status to the destination's pipeline stage concept, noting that Jobtoolz stages are user-defined and may not map 1:1 to standard ATS stage labels. |
| Vacancies | Mapping required | Vacancies are the job posting objects in Jobtoolz. We map Vacancy fields (title, department, location, employment type, description) to the destination's Job or Position object. Custom vacancy fields require explicit field-level mapping. |
| Pipeline Stages | Mapping required | Jobtoolz allows custom pipeline stage names and counts. We capture the full stage sequence during scoping and reconstruct it in the destination, merging any stages that exceed the target platform's maximum. |
| Custom Candidate Fields | Mapping required | Jobtoolz supports custom fields on candidate records. We export the field schema, preserve all values, and recreate the fields as custom properties in the destination ATS, flagging any type mismatches (e.g. date vs. text). |
| Documents and Attachments | Mapping required | Resume and cover letter attachments associated with candidates can be exported. We download attachments via the authenticated session and re-attach them to the corresponding candidate record in the destination platform. |
| Employer Branding Content | Fully supported | Company branding assets, career site content, and job ad templates are managed via the Jobtoolz Content API. This API is fully authenticated with Bearer tokens, and we migrate these as structured content blocks compatible with most destination careers page builders. |
| Users and Team Members | Mapping required | We migrate team member accounts and map them to users in the destination ATS. Role and permission structures differ between platforms, so we assign default recruiter roles and flag any accounts that require elevated permissions. |
Gotchas
What to watch for in Jobtoolz migrations
Issues we've hit on past Jobtoolz migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No bulk ATS data API forces manual CSV exports for migration scoping
Custom pipeline stages lack a standard schema for destination mapping
HireHive acquisition may introduce schema divergence in future
| Severity | Issue |
|---|---|
| High | No bulk ATS data API forces manual CSV exports for migration scoping |
| Medium | Custom pipeline stages lack a standard schema for destination mapping |
| Low | HireHive acquisition may introduce schema divergence in future |
Leaving Jobtoolz?
Where Jobtoolz customers move next
5 destinations Jobtoolz can migrate to.
How a Jobtoolz migration works
Four steps, Jobtoolz-specific
Connect
Bearer token into Jobtoolz. Scopes limited to read-only on the data we move.
Map
We translate Jobtoolz-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Jobtoolz quirks before production.
Migrate
Full migration with Jobtoolz rate-limit handling. Rollback available throughout.
FAQ
Jobtoolz migration FAQ
Answers to the questions buyers ask most during Jobtoolz migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Jobtoolz 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 Jobtoolz.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Jobtoolz setup and destination — written quote back within a business day.