Migrate your SignalHire data
B2B contact discovery and lead generation platform aggregating 850M+ professional profiles. Primarily used by recruiters and sales teams to find verified emails, phones, and social links.
In its favor
Why people choose SignalHire
The signal that keeps SignalHire on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Massive database scale with 850M+ professional profiles and 30M+ company records gives recruiters and sales teams a single place to find contact details without manually sourcing each lead.
Browser extension enables one-click contact extraction directly from LinkedIn profiles and Sales Navigator without leaving the browser.
Credit pool model means one team subscription covers unlimited users with a shared credit budget, simplifying procurement for growing sales teams.
Verified contact data with deliverability scoring (Valid, Risky, Unknown) helps teams prioritize outreach and avoid bounces before sending campaigns.
CSV bulk enrichment allows uploading thousands of names and companies at once and receiving a complete enriched export with emails, phones, and social links.
The 'Unlimited' plan hides a 5,000-credit-per-month fair-usage cap in tooltip text, not on the pricing page, leading to budget surprises when teams exceed the limit.
Data freshness is inconsistent — multiple G2 reviews cite outdated email addresses and phone numbers that no longer reach the intended contacts.
Credit costs add up quickly on the lower tiers — the Phones plan delivers only 435 credits per month at $69, making phone-only outreach expensive relative to alternatives.
Platform coverage is skewed toward US and Western markets; users conducting global recruitment report significantly lower match rates outside these regions.
No native ATS capabilities mean SignalHire is purely a data source; teams needing full recruiting workflows still require a separate ATS.
Reasons to switch
Why people leave SignalHire
The recurring reasons buyers give for replacing SignalHire. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where SignalHire 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
SignalHire pricing overview
SignalHire uses a credit-based subscription model where each lookup consumes a credit. Monthly plans start at $69 for 1,000 email credits or 435 phone credits. The 'Unlimited' plan is marketed as unlimited but enforces a 5,000-credit-per-month cap under fair-usage policy — a detail buried in tooltip text rather than prominent pricing disclosure.
Free
Tier 1 of 6
$0/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on SignalHire's schedule — see our quote-based pricing →
What gets migrated
SignalHire object support
Object-by-object support for SignalHire migrations. Per-pair details surface during scoping.
People Profiles
Fully supportedThe primary object in SignalHire. Each profile contains name, LinkedIn URL, current job title, company, location, and a SignalHire-generated UID. We migrate all returned profile fields including work-history snippets scraped at time of lookup.
Company Profiles
Fully supportedSignalHire maintains 30M+ company records. Each contains company name, domain, industry, size range, location, and LinkedIn company page URL. We pull the full company object associated with each migrated person.
Email Addresses
Fully supportedEmail is the primary deliverable. Each person record may have multiple email addresses with verification status (Valid, Risky, Unknown). We preserve the status flag and the deliverability score alongside the address itself.
Phone Numbers
Fully supportedPhone numbers are stored with country code, line type (mobile/landline), and verification confidence. We migrate all returned phone variants per person record.
Social Profiles
Fully supportedSocial profile links (LinkedIn, Twitter, GitHub, etc.) are stored as URL arrays per person. We preserve the full list and the platform identifier for each link.
Lead Lists / Talent Pools
Mapping requiredUsers can create named lead lists and talent pools in SignalHire. List membership is a many-to-many relationship. We reconstruct list membership by mapping each list ID to its constituent profile UIDs. Custom list names and descriptions are preserved.
Team Members
Mapping requiredTeam plans allow multiple users under one account. Team member records include name, email, and role. We migrate team rosters but user-level permission structures are not exposed via API and must be reconfigured at the destination.
API Credentials
Not in this platformSignalHire API keys are scoped to the account, not individual records. Migration does not include API keys — new credentials must be generated in the destination platform. We do not transfer authentication tokens between systems.
Credit Balances
Not in this platformCredits are a SignalHire-specific billing mechanism with no equivalent in most destination platforms. We do not migrate credit balances. Unused credits are forfeited at cancellation.
Integration Configurations
Not in this platformCRM/ATS integration settings (field mappings, sync directions, webhook URLs) are destination-specific. We export the raw contact data; customers must reconfigure integrations at their new platform.
| Object | Support | Notes |
|---|---|---|
| People Profiles | Fully supported | The primary object in SignalHire. Each profile contains name, LinkedIn URL, current job title, company, location, and a SignalHire-generated UID. We migrate all returned profile fields including work-history snippets scraped at time of lookup. |
| Company Profiles | Fully supported | SignalHire maintains 30M+ company records. Each contains company name, domain, industry, size range, location, and LinkedIn company page URL. We pull the full company object associated with each migrated person. |
| Email Addresses | Fully supported | Email is the primary deliverable. Each person record may have multiple email addresses with verification status (Valid, Risky, Unknown). We preserve the status flag and the deliverability score alongside the address itself. |
| Phone Numbers | Fully supported | Phone numbers are stored with country code, line type (mobile/landline), and verification confidence. We migrate all returned phone variants per person record. |
| Social Profiles | Fully supported | Social profile links (LinkedIn, Twitter, GitHub, etc.) are stored as URL arrays per person. We preserve the full list and the platform identifier for each link. |
| Lead Lists / Talent Pools | Mapping required | Users can create named lead lists and talent pools in SignalHire. List membership is a many-to-many relationship. We reconstruct list membership by mapping each list ID to its constituent profile UIDs. Custom list names and descriptions are preserved. |
| Team Members | Mapping required | Team plans allow multiple users under one account. Team member records include name, email, and role. We migrate team rosters but user-level permission structures are not exposed via API and must be reconfigured at the destination. |
| API Credentials | Not in this platform | SignalHire API keys are scoped to the account, not individual records. Migration does not include API keys — new credentials must be generated in the destination platform. We do not transfer authentication tokens between systems. |
| Credit Balances | Not in this platform | Credits are a SignalHire-specific billing mechanism with no equivalent in most destination platforms. We do not migrate credit balances. Unused credits are forfeited at cancellation. |
| Integration Configurations | Not in this platform | CRM/ATS integration settings (field mappings, sync directions, webhook URLs) are destination-specific. We export the raw contact data; customers must reconfigure integrations at their new platform. |
Gotchas
What to watch for in SignalHire migrations
Issues we've hit on past SignalHire migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Unlimited plan credit cap is hidden in tooltip text
Credit consumed per lookup, not per successful result
API async mode requires a publicly accessible callback URL
Company profiles are scraped derivatives, not authoritative records
| Severity | Issue |
|---|---|
| High | Unlimited plan credit cap is hidden in tooltip text |
| Medium | Credit consumed per lookup, not per successful result |
| Medium | API async mode requires a publicly accessible callback URL |
| Low | Company profiles are scraped derivatives, not authoritative records |
Leaving SignalHire?
Where SignalHire customers move next
5 destinations SignalHire can migrate to.
How a SignalHire migration works
Four steps, SignalHire-specific
Connect
API key (per-account secret key passed in request header) into SignalHire. Scopes limited to read-only on the data we move.
Map
We translate SignalHire-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate SignalHire quirks before production.
Migrate
Full migration with SignalHire rate-limit handling. Rollback available throughout.
FAQ
SignalHire migration FAQ
Answers to the questions buyers ask most during SignalHire migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your SignalHire 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 SignalHire.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your SignalHire setup and destination — written quote back within a business day.