Migrate from hireful to Bullhorn ATS & CRM

hireful Vacancy records map to Bullhorn JobOrder. The hireful vacancy title, description, status (Open/Closed/On Hold), and internal job reference number transfer to JobOrder title, description, status, and externalRef. hireful's pipeline stages stored as custom properties require mapping to Bullhorn JobOrder status values and any applicable Record Type. JobOrder IsDeleted and IsOpen flags align with hireful's vacancy status enumeration.

hireful Candidate profiles map directly to Bullhorn Candidate records. We extract full candidate contact details (name, email, phone, address), work history, skills, and source attribution from the CSV export. The Bullhorn Candidate record becomes the primary entity that JobSubmissions attach to. We resolve duplicate candidates during migration using email as the dedupe key and flag matches for admin review rather than silently merging.

Each hireful Application record (a Candidate-to-Vacancy pairing) maps to a Bullhorn JobSubmission. Application status in hireful (Applied, Shortlisted, Interviewing, Offered, Rejected) maps to Bullhorn JobSubmission status values. The migration resolves CandidateId and JobOrderId references before inserting JobSubmission records so that the relationships are valid at import time.

Custom application form fields on hireful Pro and above tiers map to Bullhorn custom fields on JobSubmission (for form-wide fields) or to Bullhorn Custom Objects with up to 55 fields each on Growth and Enterprise editions. We pre-create Bullhorn Custom Objects via Bullhorn Support ticket before migration and map each bespoke form field to a typed field. Free-text fields map to Bullhorn textArea or textarea fields; multi-select fields map to multi-select picklist; date fields map to date fields.

CVs and uploaded documents attached to hireful Candidate profiles are extracted via hireful's bulk download interface and re-uploaded to Bullhorn as Candidate Resume (the parsed resume content linked to the Candidate record) and as Attachment records linked via ContentDocumentLink. Resume parsing in Bullhorn runs on upload to populate structured candidate fields from the CV text.

Interview events recorded in hireful on the Grow and Pro tiers map to Bullhorn Event records. StartDateTime, EndDateTime, location, and interview type transfer to Event subject, start, end, location, and eventType fields. Attendee resolution links EventRelation records to the corresponding Candidate and User (interviewer) records in Bullhorn.

Recruiter scoring values and structured evaluation data stored against hireful Application records migrate to Bullhorn JobSubmission custom fields (numeric scores to number fields, evaluation grades to picklist fields). Free-text evaluation notes migrate to Note records linked to the JobSubmission. If the customer uses hireful's applicant scoring module on Pro tier, we map each score criterion to a named Bullhorn custom field for reporting consistency.

hireful hiring manager portal users are mapped to Bullhorn User records. Unlimited hiring manager seats on hireful map to Bullhorn User licences with the hiring manager role, which restricts access to assigned JobOrders and Candidates only. The hireful portal user email becomes the Bullhorn User username for SSO consistency. We flag any hiring manager with a hireful account that has no corresponding email for Bullhorn User provisioning.

The record of which job boards a vacancy was posted to (Indeed, TotalJobs, Reed, CV Library) is preserved as a metadata field on the Bullhorn JobOrder (a text field listing active board integrations). Active posting credentials and API keys do not transfer; the customer configures Bullhorn's job board integrations post-migration using their existing board accounts. We document the full board roster from hireful so nothing is missed.

hireful GDPR deletion flags and candidate retention expiry timestamps do not appear in the standard CSV export. We extract these values from the hireful admin interface during scoping and carry them as custom fields on the Bullhorn Candidate record (hireful_deletion_requested__c, hireful_retention_expiry__c) so the destination system can honour the original retention schedule. The customer's Bullhorn admin sets up Bullhorn Automation rules post-migration to trigger deletion workflows based on these fields.

Active hireful recruiter licences map to Bullhorn User records with the appropriate Bullhorn role (Full Recruiter, Limited Recruiter, or Standard). We extract all licence tiers represented in the source data and align them to Bullhorn User roles during provisioning. Unlimited hiring manager seats on hireful map to Bullhorn hiring manager role accounts. The hireful Go tier single-recruiter licence maps to one Bullhorn User with full recruiter access.

hireful's vacancy approval workflow (Pro tier) has no direct Bullhorn equivalent as a native feature. Approval logic on JobOrder creation or status change migrates as Bullhorn Automation rules (available on Corporate and Enterprise tiers) configured post-migration. We deliver a written description of the hireful approval chain (approvers, conditions, escalation steps) as input for Bullhorn Automation setup.

hireful's free volunteer management module on charity and NFP tiers does not have a direct Bullhorn equivalent. Volunteer-specific data (volunteer profiles, availability, role preferences) migrates as Bullhorn Candidate records with a custom volunteer_type__c flag or as a Bullhorn Custom Object if the customer's Bullhorn edition supports it. The customer rebuilds volunteer shift scheduling and matching logic in Bullhorn manually or via Bullhorn Automation.