HRMS

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.

Encrypted end-to-end with one-click rollback
Talk to a real migration engineer in minutes
Jobtrain logo

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

G-Cloud 14 listed and suitable for UK public-sector procurement frameworks.No user, vacancy, or candidate count limits—flat-fee model removes volume-based billing surprises.Azure-hosted SaaS with fault-tolerant virtual infrastructure operating at ~20% capacity with no hard scaling ceiling.Highly configurable approval routing, vacancy templates, and cost-centre assignments accessible to super-users without vendor tickets.Documented NHS and local government references with 25 years of UK recruitment-software history.

Weaknesses

Pricing is not publicly available—fixed implementation fee only; no transparent per-seat or tier pricing for budgeting.12–16 week implementation is lengthy for organisations looking for quick ATS deployment or rapid migration to a new platform.Limited publicly documented API; bulk data export depends on Jobtrain's built-in reporting tools rather than a developer-facing REST or GraphQL endpoint.Configuration depth means every installation is effectively custom—migration field mapping requires per-client scoping rather than a standard schema.Competitors such as Greenhouse and Lever offer more internationally recognised platforms with better-documented APIs and broader integration ecosystems.

Where it works

UK public-sector organisations requiring G-Cloud compliance, including NHS trusts, NHS Scotland, and local government authorities with mandatory procurement frameworks.Large multi-site enterprises running high-volume recruitment campaigns where candidate counts fluctuate seasonally and per-candidate billing would create budget unpredictability.Organisations with complex multi-stage approval chains spanning multiple departments, cost centres, and job grades that require configurable vacancy templates and approval routing.UK-based hiring teams with dedicated super-users who prefer to own 85% of platform configuration internally rather than raising vendor tickets for routine changes.In-house recruitment teams managing structured hiring pipelines for regulated roles requiring audit trails, establishment control, and consistent scoring against predetermined norms.

Where it struggles

Organisations outside the UK public sector lacking G-Cloud procurement requirements, where internationally recognised platforms with better API ecosystems offer stronger value.Small teams or fast-moving startups needing ATS deployment within weeks rather than the 12-16 week implementation timeline Jobtrain requires for structured scoping.Organisations requiring transparent per-seat or tiered pricing to budget and compare total cost of ownership against alternative ATS platforms.Companies needing extensive API-driven integrations, automated HRIS syncing, or developer-facing bulk data exports—Jobtrain lacks a publicly documented REST or GraphQL endpoint.Organisations with simple, linear hiring needs and single-approver workflows where the depth of vacancy templates and cost-centre configuration adds unnecessary complexity.

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

Simple applicant tracking for smaller organisationsAI-assisted advert writing and candidate rankingWeb-based access across devicesConfigured by Jobtrain during onboarding

Need help selecting your HRMS?

Book a free 30 minute consultation

Pricing 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 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.

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

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 consultation

Most Jobtrain migrations under 1M records finish in 48–72 hours end-to-end. Larger orgs with custom objects or buyer-side security review typically take 5–7 days.

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.

Free scoping call Quote in 1 business day 1,784 platforms supported