Migrate your Longlist data
Chrome-extension recruiting tool that finds and surfaces candidate contact data (emails, phone numbers) directly in-browser for talent sourcers working high-volume pipelines.
In its favor
Why people choose Longlist
The signal that keeps Longlist on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Longlist combines a Chrome sourcing extension with a CRM and ATS — recruiters can find candidates on LinkedIn or job boards and push them into a managed pipeline without switching tools.
Free data migration from Excel and 10+ competing recruiting CRMs lowers the switching cost from incumbent platforms.
Multi-channel outreach (email, SMS, WhatsApp) ships in the core product rather than as a paid add-on.
Per-user pricing starts at $59/month for Growth tier with unlimited open jobs — competitive against ATS-only competitors that gate on requisition count.
30-day full refund policy provides risk-free evaluation, unusual for SaaS recruiting tools.
Longlist is positioned for small-to-mid recruiting agencies and lean in-house teams — enterprises with complex hiring workflows, compliance requirements, or large hiring volumes typically outgrow it.
No free tier means teams must commit to a paid plan from day one, which is friction relative to free-tier competitors like Recruit CRM trials.
Integrated phone calling, SMS, and custom reports are gated to the Plus tier ($79/user/month) and above, pushing the effective price up for teams that need them.
SSO and whitelabel options are Enterprise-only with custom pricing, blocking mid-market teams from those features without sales negotiation.
Limited public review presence and small market footprint versus Greenhouse, Lever, or Workable creates procurement hesitation for larger evaluators.
Reasons to switch
Why people leave Longlist
The recurring reasons buyers give for replacing Longlist. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Longlist 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
Longlist pricing overview
Longlist publishes three tiers with monthly and annual billing (annual saves about 20%): Growth at $59/user/month, Plus at $79/user/month (marked 'Most Popular'), and Enterprise at custom pricing. Growth includes unlimited open jobs, resume parsing, Gmail / Outlook integration, email sequences, data migration support, and 24x5 support. Plus adds integrated phone calling, SMS, custom reports, and priority support. Enterprise adds SSO and whitelabel options. There is no free tier; the vendor offers a 30-day full refund policy in lieu of one.
Growth
Tier 1 of 3
$59/user/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Longlist's schedule — see our quote-based pricing →
What gets migrated
Longlist object support
Object-by-object support for Longlist migrations. Per-pair details surface during scoping.
Employees
Mapping requiredLonglist's user / team member records hold name, email, role, and assigned jobs. We migrate user accounts and preserve role-based ownership of Candidates and Jobs.
Compensation
Mapping requiredCandidate-level salary expectation and offered compensation are stored as custom fields on the Candidate record rather than as a first-class object. We migrate compensation data as candidate properties.
Time Off
Not in this platformLonglist is a recruiting / sourcing platform, not a core HRMS — time-off tracking is not part of the data model.
Onboarding
Not in this platformOnboarding workflows are not part of Longlist's scope. Candidates that move to hired status are typically handed off to a downstream HRMS or ATS for onboarding.
Performance Reviews
Not in this platformPerformance management is out of scope — Longlist focuses on the pre-hire pipeline.
Org Chart
Not in this platformLonglist does not maintain an organizational hierarchy beyond the user / team structure.
Custom Fields
Mapping requiredCustom fields can be added to Candidate and Job records. We inventory active custom fields during scoping and map them to destination custom properties.
Documents
Mapping requiredResume files and supporting documents attach to Candidate records. We extract files via the platform's export and re-associate them with the parent Candidate in the destination.
| Object | Support | Notes |
|---|---|---|
| Employees | Mapping required | Longlist's user / team member records hold name, email, role, and assigned jobs. We migrate user accounts and preserve role-based ownership of Candidates and Jobs. |
| Compensation | Mapping required | Candidate-level salary expectation and offered compensation are stored as custom fields on the Candidate record rather than as a first-class object. We migrate compensation data as candidate properties. |
| Time Off | Not in this platform | Longlist is a recruiting / sourcing platform, not a core HRMS — time-off tracking is not part of the data model. |
| Onboarding | Not in this platform | Onboarding workflows are not part of Longlist's scope. Candidates that move to hired status are typically handed off to a downstream HRMS or ATS for onboarding. |
| Performance Reviews | Not in this platform | Performance management is out of scope — Longlist focuses on the pre-hire pipeline. |
| Org Chart | Not in this platform | Longlist does not maintain an organizational hierarchy beyond the user / team structure. |
| Custom Fields | Mapping required | Custom fields can be added to Candidate and Job records. We inventory active custom fields during scoping and map them to destination custom properties. |
| Documents | Mapping required | Resume files and supporting documents attach to Candidate records. We extract files via the platform's export and re-associate them with the parent Candidate in the destination. |
Gotchas
What to watch for in Longlist migrations
Issues we've hit on past Longlist migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Outreach history (email sequences, SMS, WhatsApp) must be extracted to preserve candidate context
Resume parsing data is a separate artifact from the original file
Chrome extension scope vs CRM scope creates data lineage questions
Integrated phone / SMS depends on telephony provider configuration
| Severity | Issue |
|---|---|
| High | Outreach history (email sequences, SMS, WhatsApp) must be extracted to preserve candidate context |
| Medium | Resume parsing data is a separate artifact from the original file |
| Medium | Chrome extension scope vs CRM scope creates data lineage questions |
| Low | Integrated phone / SMS depends on telephony provider configuration |
Leaving Longlist?
Where Longlist customers move next
5 destinations Longlist can migrate to.
How a Longlist migration works
Four steps, Longlist-specific
Connect
Not publicly documented on the marketing site — Longlist exposes Gmail / Outlook integrations and Chrome-extension flows, but a developer portal with API authentication details is not openly published. Confirm with vendor during scoping. into Longlist. Scopes limited to read-only on the data we move.
Map
We translate Longlist-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Longlist quirks before production.
Migrate
Full migration with Longlist rate-limit handling. Rollback available throughout.
FAQ
Longlist migration FAQ
Answers to the questions buyers ask most during Longlist migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Longlist 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 Longlist.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Longlist setup and destination — written quote back within a business day.