Migrate from Betterteam to Bullhorn ATS & CRM

Betterteam Jobs map to Bullhorn JobOrder records. Job title, description, requirements, location, department, employment type, and status migrate directly. Betterteam job status (active, closed, draft, expiring) maps to Bullhorn JobOrder status values (Open, Interviewing, Offered, Filled, Closed). The job's posting date and expiration date migrate to Bullhorn date fields. JobOrder RecordType and JobOwner are resolved during import, with the Bullhorn OwnerId assigned from the user mapping step.

Betterteam stores candidate data per-application rather than as unified profiles. A candidate who applied to three different jobs appears as three separate records in Betterteam. We deduplicate by email address, merging all applications into a single Bullhorn Candidate record. The Bullhorn Candidate record becomes the parent for all subsequent JobSubmission records. Name, email, phone, location, current employer, and linkedinUrl migrate from the best non-null field across duplicate source records. Skills, certifications, and employment history stored as structured fields in Betterteam map to Bullhorn Candidate custom fields where available.

Betterteam Applications map to Bullhorn JobSubmission records, which link a Candidate to a JobOrder. Each JobSubmission inherits the CandidateId from the merged candidate record and the JobOrderId from the mapped job. Application status in Betterteam (new, reviewed, liked, declined) maps to Bullhorn JobSubmission status values (New, Submitted, Interview, Offer, Hired, Rejected). Submission date and last-updated timestamp preserve on the JobSubmission record. The source job board attribution (Betterteam's board-level source only) migrates to a custom field on JobSubmission.

Betterteam star ratings (1-5 scale) applied to candidates migrate to Bullhorn's Candidate rating field. Each rating carries a reviewer user attribution and timestamp that we map to Bullhorn's rating metadata fields where supported. If the candidate received multiple ratings across applications, we record the aggregate average as the primary rating and note the count of reviews.

Betterteam reviewer notes attach to candidate records and include free-text content, author attribution, and timestamp. We import notes as Bullhorn Note records linked to the consolidated Candidate via ContentDocumentLink. Author attribution is preserved in the Note body and via a custom field mapping to the Bullhorn User who authored the original note, resolved by email match against the Bullhorn User table. Chronological ordering is preserved by the Note CreatedDate.

Resume and cover letter files attached to Betterteam applications are downloaded and re-uploaded to Bullhorn as ContentDocument records linked to the Candidate. Bullhorn's built-in resume parsing extracts candidate name, email, phone, skills, work history, and education from the uploaded resume and populates the corresponding Bullhorn Candidate fields automatically. We flag any file naming convention differences and any unsupported file formats for manual review.

Betterteam generates hosted careers pages as rendered HTML rather than exposing a structured API. We extract the visible job listing content, company branding text, and page URL from the rendered page and reconstruct this as Bullhorn JobOrder records with full description fields populated. Any content that cannot be parsed from HTML (hiring manager, compensation range, urgency flags) is flagged for manual verification before the Bullhorn career portal goes live.

Betterteam does not have a structured user management layer equivalent to Bullhorn's. Reviewers who liked, rated, or commented on candidates are treated as Owner candidates. We resolve Betterteam reviewer emails against the Bullhorn User table. Any reviewer without a matching Bullhorn User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Bullhorn requires every Candidate and JobOrder to have an OwnerId at insert time.

Betterteam's job board posting integrations (100+ boards including Indeed, ZipRecruiter, and LinkedIn) are managed server-side and are not exposed in exportable data or API fields. The mapping of which job was posted to which board, when, and with what content does not migrate. We flag this as an item for the customer's admin to reconfigure manually in Bullhorn's career portal distribution settings and Bullhorn's 350+ AppExchange partner integrations post-migration.

Betterteam plans do not include a structured custom field API, but teams sometimes store custom data in job description text, free-text notes, or third-party-integrated fields. We audit all Betterteam data for structured-looking content (key-value pairs in descriptions, formatted note sections) and map any identifiable custom properties to Bullhorn Custom Fields on the appropriate entity (Candidate, JobOrder, JobSubmission). Custom Fields on Bullhorn ATS require field mapping setup in Admin > Field Mappings before import.

Betterteam does not have a placement tracking module. Teams that need to track candidate placements, assignments, and start dates must configure Bullhorn Placements after migration. We do not create Placement records from Betterteam source data, but we document the Bullhorn Placement data model (Candidate, JobOrder, ClientCorporation, StartDate, EndDate, PayRate, BillRate) so the customer's Bullhorn admin can begin recording placements from the migration date forward.

Bullhorn treats Leads as a separate pipeline from Candidates for prospects who have not yet submitted a formal application. Betterteam does not have a Lead object; all applicant-trackable records are Jobs, Candidates, and Applications. We configure Bullhorn's Lead object for any pipeline records the customer creates after migration and document the Lead-to-Candidate conversion workflow for cases where a prospect contacts the team outside of a formal Betterteam-tracked application.