Migrate your JOIN data
Recruiting ATS that distributes job postings across 250+ job boards and manages candidates through a structured hiring pipeline, built for SMB to mid-market HR teams.
In its favor
Why people choose JOIN
The signal that keeps JOIN on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Distributes job postings across 250+ job boards from a single interface, saving recruiting teams the manual effort of reposting roles individually on each platform.
Provides a structured hiring pipeline with clear stage gates from sourcing through offer, giving HR teams a visual view of where each candidate stands.
Includes built-in candidate communication tools such as templated emails and scheduling integration that reduce back-and-forth coordination for interview booking.
Offers a free tier or low entry price point that lets small businesses pilot the ATS without committing to a high-cost annual contract upfront.
Provides candidate profiles that consolidate resume, social links, and notes in one place, giving hiring managers a centralised view of each applicant.
Users report bugs and account downgrades that cause data loss, disrupting active hiring pipelines and leading recruiting teams to seek more stable alternatives.
Employer branding tools and candidate experience features lag behind competitors, causing larger companies with strong employer brand priorities to migrate to platforms with more polished candidate-facing pages.
Pricing becomes opaque at higher volumes, with job posting credits and seat limits that generate unexpected overage charges at renewal time.
Customer support response times frustrate teams managing active pipelines, especially when urgent issues like posting failures or candidate data errors arise during peak recruiting periods.
Reasons to switch
Why people leave JOIN
The recurring reasons buyers give for replacing JOIN. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where JOIN 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
JOIN pricing overview
JOIN publishes pricing as a per-seat monthly subscription with a free tier for small teams. Job posting credits scale with the plan tier, and custom enterprise plans offer unlimited postings and advanced reporting. Exact per-user pricing is available on request rather than listed on the public pricing page.
Standard (Free)
Tier 1 of 4
Free
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on JOIN's schedule — see our quote-based pricing →
What gets migrated
JOIN object support
Object-by-object support for JOIN migrations. Per-pair details surface during scoping.
Jobs
Fully supportedJobs is the parent posting entity in JOIN. We extract the full job record including title, description, department, location, employment type, and posting status. Standard fields map cleanly to Greenhouse, Lever, BambooHR, and Workday Recruiting.
Candidates
Fully supportedCandidate records carry contact info, work history, education, skills tags, source attribution, and lifecycle stage. We migrate Candidates 1:1 for most destinations. The Candidate's current pipeline stage is preserved as a property-level field during migration.
Applications
Fully supportedApplications are the join table linking a Candidate to a Job, with applied date, referral source, and rejection/offers flags. We migrate Applications as a distinct object or as properties on the Candidate record depending on the destination schema.
Pipeline Stages
Mapping requiredJOIN exposes a set of stage names (Screening, Interview, Offer, etc.) that vary by plan and by job. We map the customer's actual stage sequence at migration scoping and apply that sequence to the destination ATS. Custom or non-standard stage names require explicit mapping during the chunk phase.
Scorecards and Interview Feedback
Mapping requiredInterview evaluations stored as structured feedback or free-text notes are migrated. Where the destination uses a rubric-based scorecard object, we flatten the JSON into readable text and attach it to the application record.
Custom Fields
Mapping requiredJOIN allows custom fields on Jobs and Candidates. We extract the full schema during the scan phase, then map each custom field to an equivalent in the destination or flag it as a custom property that needs manual review post-migration.
Attachments and Resume Files
Mapping requiredCandidate resume files and any attached supporting documents are exported from JOIN and uploaded to the destination as binary blobs or linked file references. File naming conventions from JOIN may need normalisation during load.
Activity and Communication History
Not in this platformInternal email threads, scheduled interview events, and activity log entries are stored in JOIN's activity timeline. The current JOIN API does not expose a documented endpoint for bulk activity export. We flag this gap at scoping and recommend exporting the timeline manually as a CSV complement to the API-driven migration.
| Object | Support | Notes |
|---|---|---|
| Jobs | Fully supported | Jobs is the parent posting entity in JOIN. We extract the full job record including title, description, department, location, employment type, and posting status. Standard fields map cleanly to Greenhouse, Lever, BambooHR, and Workday Recruiting. |
| Candidates | Fully supported | Candidate records carry contact info, work history, education, skills tags, source attribution, and lifecycle stage. We migrate Candidates 1:1 for most destinations. The Candidate's current pipeline stage is preserved as a property-level field during migration. |
| Applications | Fully supported | Applications are the join table linking a Candidate to a Job, with applied date, referral source, and rejection/offers flags. We migrate Applications as a distinct object or as properties on the Candidate record depending on the destination schema. |
| Pipeline Stages | Mapping required | JOIN exposes a set of stage names (Screening, Interview, Offer, etc.) that vary by plan and by job. We map the customer's actual stage sequence at migration scoping and apply that sequence to the destination ATS. Custom or non-standard stage names require explicit mapping during the chunk phase. |
| Scorecards and Interview Feedback | Mapping required | Interview evaluations stored as structured feedback or free-text notes are migrated. Where the destination uses a rubric-based scorecard object, we flatten the JSON into readable text and attach it to the application record. |
| Custom Fields | Mapping required | JOIN allows custom fields on Jobs and Candidates. We extract the full schema during the scan phase, then map each custom field to an equivalent in the destination or flag it as a custom property that needs manual review post-migration. |
| Attachments and Resume Files | Mapping required | Candidate resume files and any attached supporting documents are exported from JOIN and uploaded to the destination as binary blobs or linked file references. File naming conventions from JOIN may need normalisation during load. |
| Activity and Communication History | Not in this platform | Internal email threads, scheduled interview events, and activity log entries are stored in JOIN's activity timeline. The current JOIN API does not expose a documented endpoint for bulk activity export. We flag this gap at scoping and recommend exporting the timeline manually as a CSV complement to the API-driven migration. |
Gotchas
What to watch for in JOIN migrations
Issues we've hit on past JOIN migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Activity log and communication history are not exported via JOIN API
Pipeline stage names vary per job and per plan
Custom fields on Candidates require manual equivalence review
Resume and attachment export format is non-standard
| Severity | Issue |
|---|---|
| High | Activity log and communication history are not exported via JOIN API |
| Medium | Pipeline stage names vary per job and per plan |
| Medium | Custom fields on Candidates require manual equivalence review |
| Low | Resume and attachment export format is non-standard |
Leaving JOIN?
Where JOIN customers move next
5 destinations JOIN can migrate to.
How a JOIN migration works
Four steps, JOIN-specific
Connect
API key into JOIN. Scopes limited to read-only on the data we move.
Map
We translate JOIN-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate JOIN quirks before production.
Migrate
Full migration with JOIN rate-limit handling. Rollback available throughout.
FAQ
JOIN migration FAQ
Answers to the questions buyers ask most during JOIN migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your JOIN 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 JOIN.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your JOIN setup and destination — written quote back within a business day.