Migrate your Jobtrain data
UK enterprise ATS built for high-volume, multi-site public-sector hiring. Two tiers—Jobtrain for complex orgs and JTGO for smaller teams—with a fixed-fee model and no published per-seat pricing.
In its favor
Why people choose Jobtrain
The signal that keeps Jobtrain on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
UK public-sector track record—trusted by NHS trusts, NHS Scotland, and local government authorities, making it a defensible procurement choice for organisations needing G-Cloud compliance and structured hiring workflows.
No per-user or per-candidate limits, so organisations with high-volume or seasonal hiring do not face surprise billing when candidate counts spike across a recruitment campaign.
AI-powered tools built on Microsoft Azure OpenAI, including advert generation and candidate ranking, offered as part of the standard platform for organisations looking to reduce manual writing effort.
Recruitment administration is reported reduced by 50% and time-to-hire by 31%, giving hiring managers measurable efficiency gains in structured multi-stage pipelines.
Approximately 85% of platform configuration is accessible to super-users without vendor involvement, giving in-house teams control over vacancy templates, approval routes, and workflow settings.
The 12–16 week implementation timeline creates significant switching costs and lock-in; organisations wanting to change ATS face a long, structured migration project before they can evaluate fit at the destination.
Pricing is opaque—there is no published per-seat or per-module cost, only a fixed setup and implementation fee—making it difficult to budget for a migration or compare total cost of ownership upfront.
The absence of a publicly documented bulk API means data export relies on manual Jobtrain reporting exports or vendor-assisted data pulls, increasing migration effort and dependency on Jobtrain's professional services team.
Organisations with simpler hiring needs may find Jobtrain's enterprise configuration model over-engineered; the platform is optimised for complex, multi-site, multi-approver workflows rather than small-team rapid hiring.
Reasons to switch
Why people leave Jobtrain
The recurring reasons buyers give for replacing Jobtrain. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Jobtrain 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
Jobtrain pricing overview
Jobtrain uses a single fixed setup and implementation fee covering scoping, configuration, testing, and training. Per-user or per-module pricing is not publicly published; prospective customers must contact Jobtrain directly for a quote. There are no stated limits on user counts, vacancies, or candidate records.
JTGO
Tier 1 of 2
Not publicly published
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Jobtrain's schedule — see our quote-based pricing →
What gets migrated
Jobtrain object support
Object-by-object support for Jobtrain migrations. Per-pair details surface during scoping.
Vacancies
Fully supportedVacancies are the primary Jobtrain object. We map vacancy title, reference number, grade/level, department, cost centre, advert sources, and approval routes. Custom vacancy fields are preserved as mapping work during scoping.
Candidates
Fully supportedCandidate profiles include contact details, application history, and source attribution. We import Candidates alongside their Applications to preserve the linkage to the originating Vacancy.
Applications
Fully supportedApplications link a Candidate to a Vacancy at a specific stage. We sequence Applications after both Candidates and Vacancies are staged, preserving the application date and status.
Vacancy Templates
Mapping requiredJobtrain supports reusable vacancy templates. We map template content to the destination's equivalent vacancy structure, which may require field-level mapping if the destination does not have a template object.
Job Grades and Levels
Mapping requiredJobtrain allows clients to define custom job grade and level hierarchies. We map these as text fields or lookups depending on what the destination supports for grading schemes.
Approvers and Approval Routes
Mapping requiredApproval routes are configurable per vacancy or globally. We capture the approver chain and route structure; reconstruction in the destination depends on the destination's workflow-engine support.
Cost Centres
Mapping requiredCost centres are defined and maintained in Jobtrain settings. We map cost centre codes and names; if the destination does not have a cost centre field we attach it as a vacancy or department property.
Departments
Mapping requiredDepartments are organisational units used to categorise vacancies and approver routing. We map department names and IDs and attach them to vacancies in the destination.
Communication Templates
Mapping requiredJobtrain stores email and letter templates used during recruitment stages. We export template content as structured data; the destination may store these as a separate document set or re-create them manually.
Advert Sources
Mapping requiredAdvert sources include origin channels and associated costs for reporting. We map source names and attributions; destination systems that lack a dedicated source field receive these as a tagged property on the vacancy.
Onboarding Templates and New Starter Documents
Not in this platformOnboarding templates and offer letters are managed within Jobtrain's onboarding module. These are document-centric objects without a stable structured export schema; we flag them as out of scope and recommend manual re-creation at the destination.
Custom Fields
Mapping requiredJobtrain allows super-users to add custom fields across vacancy, candidate, and application objects. Every custom field installation is unique; we discover the full custom-field set during scoping and build a per-field mapping plan.
Attachments
Mapping requiredAttachments on vacancies, candidates, and applications (CVs, cover letters, interview notes) are downloadable via the Jobtrain interface. We export them as files and associate them with the correct record in the destination by filename and record linkage.
| Object | Support | Notes |
|---|---|---|
| Vacancies | Fully supported | Vacancies are the primary Jobtrain object. We map vacancy title, reference number, grade/level, department, cost centre, advert sources, and approval routes. Custom vacancy fields are preserved as mapping work during scoping. |
| Candidates | Fully supported | Candidate profiles include contact details, application history, and source attribution. We import Candidates alongside their Applications to preserve the linkage to the originating Vacancy. |
| Applications | Fully supported | Applications link a Candidate to a Vacancy at a specific stage. We sequence Applications after both Candidates and Vacancies are staged, preserving the application date and status. |
| Vacancy Templates | Mapping required | Jobtrain supports reusable vacancy templates. We map template content to the destination's equivalent vacancy structure, which may require field-level mapping if the destination does not have a template object. |
| Job Grades and Levels | Mapping required | Jobtrain allows clients to define custom job grade and level hierarchies. We map these as text fields or lookups depending on what the destination supports for grading schemes. |
| Approvers and Approval Routes | Mapping required | Approval routes are configurable per vacancy or globally. We capture the approver chain and route structure; reconstruction in the destination depends on the destination's workflow-engine support. |
| Cost Centres | Mapping required | Cost centres are defined and maintained in Jobtrain settings. We map cost centre codes and names; if the destination does not have a cost centre field we attach it as a vacancy or department property. |
| Departments | Mapping required | Departments are organisational units used to categorise vacancies and approver routing. We map department names and IDs and attach them to vacancies in the destination. |
| Communication Templates | Mapping required | Jobtrain stores email and letter templates used during recruitment stages. We export template content as structured data; the destination may store these as a separate document set or re-create them manually. |
| Advert Sources | Mapping required | Advert sources include origin channels and associated costs for reporting. We map source names and attributions; destination systems that lack a dedicated source field receive these as a tagged property on the vacancy. |
| Onboarding Templates and New Starter Documents | Not in this platform | Onboarding templates and offer letters are managed within Jobtrain's onboarding module. These are document-centric objects without a stable structured export schema; we flag them as out of scope and recommend manual re-creation at the destination. |
| Custom Fields | Mapping required | Jobtrain allows super-users to add custom fields across vacancy, candidate, and application objects. Every custom field installation is unique; we discover the full custom-field set during scoping and build a per-field mapping plan. |
| Attachments | Mapping required | Attachments on vacancies, candidates, and applications (CVs, cover letters, interview notes) are downloadable via the Jobtrain interface. We export them as files and associate them with the correct record in the destination by filename and record linkage. |
Gotchas
What to watch for in Jobtrain migrations
Issues we've hit on past Jobtrain migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No publicly documented bulk export API
Custom field schema varies per installation
12–16 week implementation timeline
Onboarding and offer-letter documents are not structured for bulk export
Approval routes and approver chains are installation-specific
| Severity | Issue |
|---|---|
| High | No publicly documented bulk export API |
| High | Custom field schema varies per installation |
| Medium | 12–16 week implementation timeline |
| Medium | Onboarding and offer-letter documents are not structured for bulk export |
| Low | Approval routes and approver chains are installation-specific |
Leaving Jobtrain?
Where Jobtrain customers move next
5 destinations Jobtrain can migrate to.
How a Jobtrain migration works
Four steps, Jobtrain-specific
Connect
Client ID + API key issued after signing an API Partnership Agreement with Jobtrain. into Jobtrain. Scopes limited to read-only on the data we move.
Map
We translate Jobtrain-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Jobtrain quirks before production.
Migrate
Full migration with Jobtrain rate-limit handling. Rollback available throughout.
FAQ
Jobtrain migration FAQ
Answers to the questions buyers ask most during Jobtrain migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Jobtrain 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 Jobtrain.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Jobtrain setup and destination — written quote back within a business day.