Migrate your JobScore data
Hiring headquarters for in-house recruiting teams. JobScore organizes job postings, candidate pipelines, interviews, and scorecards across a minimalist 3-page interface for SMBs.
In its favor
Why people choose JobScore
The signal that keeps JobScore on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Aggregates applicants from 40+ job boards into a single inbox per G2 reviewer feedback — teams advertise broadly but triage in one place, eliminating tab-switching across board portals.
Unlimited users, candidates, notes, and tags at every paid tier per JobScore's published plan structure — recruiting team growth doesn't trigger per-seat upcharges.
Job-count pricing instead of per-user means cost is tied to hiring volume, not team size — useful for SMBs where many people interview but few recruit full-time.
Built by experienced in-house recruiters per vendor positioning, which reviewers cite as the reason the workflow stages and scorecard model feel native to the hiring process.
4.2/5 average on G2 across 19+ reviews and 9.5/10 on TrustRadius — independent peer scores higher than many similarly-priced ATS competitors.
Customer support is described as 'minimal to borderline nonexistent' in some G2 reviews — phone calls go to voicemail and email response can take ~48 hours, frustrating teams with time-sensitive issues.
UI is described as 'clunky' and 'tedious to use' — basic actions like writing interview notes require multiple clicks per reviewer feedback.
Reporting and analytics are 'basic' — teams needing custom workforce planning or compliance reports outgrow JobScore's built-in dashboards.
Feature gating forces small teams to upgrade — templates, automation, and advanced offer tools sit behind higher plans, which can be painful for lean teams.
Additional fees for advanced tech support are documented in reviews — base subscriptions do not include premium support escalations.
Reasons to switch
Why people leave JobScore
The recurring reasons buyers give for replacing JobScore. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where JobScore 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
JobScore pricing overview
JobScore does not charge per user. Pricing scales with the maximum number of concurrent open jobs on the account. Annual billing saves up to 33% compared to monthly. Job postings to paid boards and JobScore Network credits are charged separately. No signup, termination, or support fees are listed.
Lite
Tier 1 of 4
$69/month (billed monthly)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on JobScore's schedule — see our quote-based pricing →
What gets migrated
JobScore object support
Object-by-object support for JobScore migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCore person record. Contains name, email, phone, resume, tags, notes, and a linked stage. Fully exportable via the v2 REST API and sortable by uid, created_on, and updated_on. We map Candidate records 1:1 into the destination ATS.
Jobs
Mapping requiredOpen position records with title, description, location, and status. Only 'published' jobs appear in the API and job feeds. We scope all Job exports to the published set and warn customers about unpublished roles that won't transfer automatically.
Applications
Fully supportedJoin table linking a Candidate to a Job. Contains stage history, application date, and custom form field responses. We carry all application-level fields and stage timestamps into the destination system.
Interviews
Fully supportedScheduled events tied to an Application. Contains date, interviewer assignment, interview type, and outcome. We export Interviews with their linked Application uids so they reconstruct correctly at the destination.
Scorecards
Fully supportedRating and evaluation forms submitted by interviewers post-interview. Contains ratings, comments, and interviewer uid. Standard object; we migrate Scorecards as attachments to their parent Interview record.
Documents
Mapping requiredUploaded resumes, cover letters, and attachments linked to Candidates or Applications. Resume parsing and scoring are platform-native features. We export raw document blobs and reattach them on the destination side.
Locations
Fully supportedJob location records with address, city, state, and country fields. Supported in the v2 API. We map Locations to the destination Jobs object.
Users (Employees)
Mapping requiredSystem users who can be assigned as interviewers, owners, or recruiters. The API exposes Users and Employees as separate endpoints. We map user assignments across all objects to the destination's owner model.
Custom Application Forms
Mapping requiredCustom form fields created per job. Responses are stored at the Application level. We extract custom field schemas from the source account and recreate them as custom properties at the destination.
Tags
Fully supportedFreeform labels applied to Candidates. Tag support is unlimited and fully exportable. We preserve all tag associations on each Candidate record.
Email Templates
Mapping requiredPersonalized message templates used in automated workflows. Stored as platform objects; we export template bodies, subject lines, and trigger conditions. Destination platform must support email template creation to restore them.
Workflow Stages
Mapping requiredFive standard stages (New, Active, Declined, Withdrawn, Hired) with customizable Active sub-stages. Standard stages cannot be renamed. We map each candidate's stage history and flag any custom stages that lack a direct destination equivalent.
Application Statuses
Fully supportedDisposition codes used to mark why a candidate moved to Declined or Withdrawn. Configurable per account. We export all status codes and apply them at the destination to maintain reporting continuity.
Job Feed / Careers Site
Mapping requiredPublished job listings exposed via JSON, JSONP, XML, or ATOM feeds. Requires admin access to retrieve feed URLs. We pull the feed as a secondary export to validate job completeness post-migration.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Core person record. Contains name, email, phone, resume, tags, notes, and a linked stage. Fully exportable via the v2 REST API and sortable by uid, created_on, and updated_on. We map Candidate records 1:1 into the destination ATS. |
| Jobs | Mapping required | Open position records with title, description, location, and status. Only 'published' jobs appear in the API and job feeds. We scope all Job exports to the published set and warn customers about unpublished roles that won't transfer automatically. |
| Applications | Fully supported | Join table linking a Candidate to a Job. Contains stage history, application date, and custom form field responses. We carry all application-level fields and stage timestamps into the destination system. |
| Interviews | Fully supported | Scheduled events tied to an Application. Contains date, interviewer assignment, interview type, and outcome. We export Interviews with their linked Application uids so they reconstruct correctly at the destination. |
| Scorecards | Fully supported | Rating and evaluation forms submitted by interviewers post-interview. Contains ratings, comments, and interviewer uid. Standard object; we migrate Scorecards as attachments to their parent Interview record. |
| Documents | Mapping required | Uploaded resumes, cover letters, and attachments linked to Candidates or Applications. Resume parsing and scoring are platform-native features. We export raw document blobs and reattach them on the destination side. |
| Locations | Fully supported | Job location records with address, city, state, and country fields. Supported in the v2 API. We map Locations to the destination Jobs object. |
| Users (Employees) | Mapping required | System users who can be assigned as interviewers, owners, or recruiters. The API exposes Users and Employees as separate endpoints. We map user assignments across all objects to the destination's owner model. |
| Custom Application Forms | Mapping required | Custom form fields created per job. Responses are stored at the Application level. We extract custom field schemas from the source account and recreate them as custom properties at the destination. |
| Tags | Fully supported | Freeform labels applied to Candidates. Tag support is unlimited and fully exportable. We preserve all tag associations on each Candidate record. |
| Email Templates | Mapping required | Personalized message templates used in automated workflows. Stored as platform objects; we export template bodies, subject lines, and trigger conditions. Destination platform must support email template creation to restore them. |
| Workflow Stages | Mapping required | Five standard stages (New, Active, Declined, Withdrawn, Hired) with customizable Active sub-stages. Standard stages cannot be renamed. We map each candidate's stage history and flag any custom stages that lack a direct destination equivalent. |
| Application Statuses | Fully supported | Disposition codes used to mark why a candidate moved to Declined or Withdrawn. Configurable per account. We export all status codes and apply them at the destination to maintain reporting continuity. |
| Job Feed / Careers Site | Mapping required | Published job listings exposed via JSON, JSONP, XML, or ATOM feeds. Requires admin access to retrieve feed URLs. We pull the feed as a secondary export to validate job completeness post-migration. |
Gotchas
What to watch for in JobScore migrations
Issues we've hit on past JobScore migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Phone-number deduplication silently overwrites candidate records on import
Only published jobs surface in the API and job feeds
Job-count pricing model creates billing risk during high-volume hiring periods
v2 API rate limits are not publicly documented
Custom workflow stages live only in the Active branch — standard stages are locked
| Severity | Issue |
|---|---|
| High | Phone-number deduplication silently overwrites candidate records on import |
| High | Only published jobs surface in the API and job feeds |
| Medium | Job-count pricing model creates billing risk during high-volume hiring periods |
| Medium | v2 API rate limits are not publicly documented |
| Low | Custom workflow stages live only in the Active branch — standard stages are locked |
Leaving JobScore?
Where JobScore customers move next
5 destinations JobScore can migrate to.
How a JobScore migration works
Four steps, JobScore-specific
Connect
HTTP Token (Bearer) or HTTP Basic with Personal Access Token into JobScore. Scopes limited to read-only on the data we move.
Map
We translate JobScore-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate JobScore quirks before production.
Migrate
Full migration with JobScore rate-limit handling. Rollback available throughout.
FAQ
JobScore migration FAQ
Answers to the questions buyers ask most during JobScore migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your JobScore 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 JobScore.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your JobScore setup and destination — written quote back within a business day.