Migrate your Bullhorn Connexys ATS data
Bullhorn Connexys ATS is a Salesforce-built recruitment platform for staffing agencies that prioritises deep customisation and global scale, but comes with opaque pricing, strict API rate limits, and a steep onboarding curve.
In its favor
Why people choose Bullhorn Connexys ATS
The signal that keeps Bullhorn Connexys ATS on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Bullhorn Connexys ATS runs on the Salesforce platform, giving agencies access to deep customisation, third-party integrations, and global infrastructure trusted by regulated industries across Europe.
The platform consolidates candidate, client, and job data into a single searchable database, reducing the manual work of cross-referencing spreadsheets and disparate tools throughout the recruitment lifecycle.
Resume parsing automates the intake of candidate information, accelerating sourcing and reducing data-entry errors when high-volume pipelines are involved.
Bullhorn's acquisition of Connexys brought enterprise-grade automation, relationship intelligence, and marketplace add-ons to European staffing agencies at scale.
Agencies upgrading from entry-level tools or spreadsheets choose Bullhorn for its scalability and the professional credibility that a recognised platform provides to clients and candidates.
The platform lacks native support for temporary or shift-based recruitment workflows, forcing agencies in the temporary staffing segment to build custom workarounds or accept fragmented processes.
Value-for-money scores are consistently below average in user reviews, with agencies citing opaque pricing, large annual contracts, and surprise renewal increases of around 20% as key pain points.
Steep onboarding complexity and a steep learning curve for new users lead to extended implementation timelines and require significant internal training investment before teams reach productivity.
Email deliverability issues have been reported, with candidate communications occasionally landing in spam folders, which disrupts communication workflows critical to recruitment pipelines.
Support quality varies by contract tier, and agencies on lower plans report slower response times and limited access to advanced troubleshooting resources.
Reasons to switch
Why people leave Bullhorn Connexys ATS
The recurring reasons buyers give for replacing Bullhorn Connexys ATS. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Bullhorn Connexys ATS 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
Bullhorn Connexys ATS pricing overview
Bullhorn uses per-user, subscription-based pricing with three primary tiers ranging from approximately $99 to $315+ per user per month, billed annually. Minimum seat requirements are typically 5–10 users. All pricing is negotiated individually, and Bullhorn does not publish standard rates. Implementation fees, add-ons, and reported 20% renewal increases add significantly to total cost of ownership.
Bullhorn ATS (Core)
Tier 1 of 4
$99–$129/user/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Bullhorn Connexys ATS's schedule — see our quote-based pricing →
What gets migrated
Bullhorn Connexys ATS object support
Object-by-object support for Bullhorn Connexys ATS migrations. Per-pair details surface during scoping.
Candidates
Fully supportedCandidate records are the core object in Bullhorn, capturing name, email, resume, work history, skills, salary, and tax information. Standard fields export cleanly via CSV or REST API. We map all standard fields and preserve resume attachments during migration.
JobOrders (Jobs)
Fully supportedJobOrders store job details, requirements, and salary ranges. They link to pipeline stages and track candidate progression. Standard job fields export and import reliably; we map custom job fields individually.
Accounts (Companies/Clients)
Fully supportedAccount records represent client companies and contain billing, industry, and contact association data. Full field export is supported. We handle the one-to-many relationship between Accounts and multiple JobOrders during migration.
Contacts
Fully supportedContact records store hiring-manager and client-side contact information, linked to Accounts. Standard and custom Contact fields export via API. We preserve the Account-Contact associations and any custom fields.
Placements
Fully supportedPlacement records capture the final hire outcome, linking Candidate to JobOrder and recording start date, salary, and status. Full field support exists. We map Placements and preserve their links to the originating Candidate and JobOrder.
Pipeline Stages
Mapping requiredBullhorn represents pipeline stages as a sequence from Application through Submittal, Interview, Offer, and Placement. The Job Reporting custom junction object tracks each transition. We preserve the full stage history and map stage names to the destination system's pipeline structure.
Opportunities
Mapping requiredOpportunities track potential placements or client deals with revenue estimates. Standard fields export, but custom Opportunity fields vary by instance. We map standard Opportunity fields and flag any custom fields for manual review.
Custom Objects
Mapping requiredCustom Objects extend Candidates, Contacts, Accounts, Jobs, and Placements with up to 55 fields each. Limits are 10 for Front Office Growth/Enterprise and 2 for Bullhorn ATS. We export Custom Object data via REST API and map fields to destination equivalents, but non-indexed fields may require additional handling.
Users (Owners/Recruiters)
Fully supportedUser records represent recruiters, administrators, and managers. Owner assignment on Candidate, JobOrder, and Placement records links data to Users. We preserve owner assignments and map them to corresponding users in the destination system.
Attachments and Resumes
Mapping requiredResume parsing is native to Bullhorn and extracts structured data from uploaded files. File attachments export via the REST API but may require chunked handling for large volumes. We preserve parsed resume data and file associations, though file format conversion may be needed.
Job Reporting (Stage History)
Mapping requiredJob Reporting is a custom junction object tracking candidate stage transitions with timestamps and associated User. Incomplete or inaccurate Job Reporting records can cause errors during Candidate stage moves. We export the full Job Reporting history and reconstruct stage timelines at the destination.
Tax Info and Compliance Data
Mapping requiredCandidate Tax Info captures federal filing status and exemptions. Compliance-related custom fields vary by region and configuration. We map standard compliance fields and flag any GDPR consent records for explicit handling.
Activity and Notes
Mapping requiredBullhorn tracks activity feeds and notes on Candidate, Contact, JobOrder, and Placement records. Activity timestamps and note content export via API. We preserve note body text and timestamps; linked file attachments are handled separately.
Data Hub (External Data)
Mapping requiredBullhorn Data Hub accepts external data via API with a registered JSON schema. Schema definitions require Bullhorn support to set up via a support ticket. We work within these constraints and map external data to standard Bullhorn entities where applicable.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Candidate records are the core object in Bullhorn, capturing name, email, resume, work history, skills, salary, and tax information. Standard fields export cleanly via CSV or REST API. We map all standard fields and preserve resume attachments during migration. |
| JobOrders (Jobs) | Fully supported | JobOrders store job details, requirements, and salary ranges. They link to pipeline stages and track candidate progression. Standard job fields export and import reliably; we map custom job fields individually. |
| Accounts (Companies/Clients) | Fully supported | Account records represent client companies and contain billing, industry, and contact association data. Full field export is supported. We handle the one-to-many relationship between Accounts and multiple JobOrders during migration. |
| Contacts | Fully supported | Contact records store hiring-manager and client-side contact information, linked to Accounts. Standard and custom Contact fields export via API. We preserve the Account-Contact associations and any custom fields. |
| Placements | Fully supported | Placement records capture the final hire outcome, linking Candidate to JobOrder and recording start date, salary, and status. Full field support exists. We map Placements and preserve their links to the originating Candidate and JobOrder. |
| Pipeline Stages | Mapping required | Bullhorn represents pipeline stages as a sequence from Application through Submittal, Interview, Offer, and Placement. The Job Reporting custom junction object tracks each transition. We preserve the full stage history and map stage names to the destination system's pipeline structure. |
| Opportunities | Mapping required | Opportunities track potential placements or client deals with revenue estimates. Standard fields export, but custom Opportunity fields vary by instance. We map standard Opportunity fields and flag any custom fields for manual review. |
| Custom Objects | Mapping required | Custom Objects extend Candidates, Contacts, Accounts, Jobs, and Placements with up to 55 fields each. Limits are 10 for Front Office Growth/Enterprise and 2 for Bullhorn ATS. We export Custom Object data via REST API and map fields to destination equivalents, but non-indexed fields may require additional handling. |
| Users (Owners/Recruiters) | Fully supported | User records represent recruiters, administrators, and managers. Owner assignment on Candidate, JobOrder, and Placement records links data to Users. We preserve owner assignments and map them to corresponding users in the destination system. |
| Attachments and Resumes | Mapping required | Resume parsing is native to Bullhorn and extracts structured data from uploaded files. File attachments export via the REST API but may require chunked handling for large volumes. We preserve parsed resume data and file associations, though file format conversion may be needed. |
| Job Reporting (Stage History) | Mapping required | Job Reporting is a custom junction object tracking candidate stage transitions with timestamps and associated User. Incomplete or inaccurate Job Reporting records can cause errors during Candidate stage moves. We export the full Job Reporting history and reconstruct stage timelines at the destination. |
| Tax Info and Compliance Data | Mapping required | Candidate Tax Info captures federal filing status and exemptions. Compliance-related custom fields vary by region and configuration. We map standard compliance fields and flag any GDPR consent records for explicit handling. |
| Activity and Notes | Mapping required | Bullhorn tracks activity feeds and notes on Candidate, Contact, JobOrder, and Placement records. Activity timestamps and note content export via API. We preserve note body text and timestamps; linked file attachments are handled separately. |
| Data Hub (External Data) | Mapping required | Bullhorn Data Hub accepts external data via API with a registered JSON schema. Schema definitions require Bullhorn support to set up via a support ticket. We work within these constraints and map external data to standard Bullhorn entities where applicable. |
Gotchas
What to watch for in Bullhorn Connexys ATS migrations
Issues we've hit on past Bullhorn Connexys ATS migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limits cap bulk migration throughput
Connexys edition tier governs Custom Object limits
Job Reporting stage history can be incomplete
Bullhorn does not publish pricing publicly
| Severity | Issue |
|---|---|
| High | API rate limits cap bulk migration throughput |
| Medium | Connexys edition tier governs Custom Object limits |
| Medium | Job Reporting stage history can be incomplete |
| Low | Bullhorn does not publish pricing publicly |
Leaving Bullhorn Connexys ATS?
Where Bullhorn Connexys ATS customers move next
5 destinations Bullhorn Connexys ATS can migrate to.
How a Bullhorn Connexys ATS migration works
Four steps, Bullhorn Connexys ATS-specific
Connect
OAuth 2.0 into Bullhorn Connexys ATS. Scopes limited to read-only on the data we move.
Map
We translate Bullhorn Connexys ATS-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Bullhorn Connexys ATS quirks before production.
Migrate
Full migration with Bullhorn Connexys ATS rate-limit handling. Rollback available throughout.
FAQ
Bullhorn Connexys ATS migration FAQ
Answers to the questions buyers ask most during Bullhorn Connexys ATS migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Bullhorn Connexys ATS 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 Bullhorn Connexys ATS.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Bullhorn Connexys ATS setup and destination — written quote back within a business day.