Migrate from Breezy HR to Bullhorn ATS & CRM

Breezy Candidate records map directly to Bullhorn Candidate. All standard fields (name, email, phone, social profiles) transfer as-is. The Breezy candidate identifier is preserved in a custom Bullhorn field for reconciliation. Stage history (the ordered list of pipeline stages the candidate passed through) migrates as a structured array attached to the Candidate record, with timestamps. Resume files and attachments bundle with the candidate record during transfer.

Breezy Position records map to Bullhorn Job. Job title, description, department, location, state, and job type transfer directly. Breezy's position-level status (open, closed, archived, draft) maps to Bullhorn Job status. The Job is the parent record for candidate submissions in Bullhorn, so Job records are created before any Candidate-to-Job associations are established during migration.

This is the primary architectural difference in this migration. Breezy supports unique pipeline configurations per position, with different stage names, stage counts, and stage actions per job. Bullhorn uses a global stage model with JobOrder-level overrides. We split Breezy's per-position pipelines into Bullhorn JobOrder records with stage values configured per Job. If the destination is Bullhorn ATS (limited to 2 custom objects), we use standard Bullhorn stages and document the per-position stage differences for manual configuration post-migration. If the destination is Front Office Growth or Enterprise, we create a WorkFlow per original Breezy pipeline to replicate stage-action logic.

Breezy users, hiring managers, and team members migrate to BullhornUser. We resolve by email match against the Bullhorn destination tenant. Breezy's Owner/User role assignments (Admin, Hiring Manager, Recruiter, Interviewer) map to Bullhorn role categories, but Bullhorn's role model is more granular for agencies (Business Administrator, Recruiter, Placement Manager, etc.). We preserve the original role name in a custom field and the customer maps to the correct Bullhorn role during the sandbox validation phase.

Breezy custom fields (Text, Date, Currency, Dropdown, Radio) require per-type mapping. Text and Date fields map cleanly to Bullhorn equivalent fields. Currency fields carry the currency code and must be validated against Bullhorn's allowed currency configuration. Dropdown and Radio options are stored as explicit value lists in Breezy; if the Bullhorn equivalent field does not include matching options, we flag the discrepancy and the customer must pre-configure option sets in Bullhorn before migration. If the customer has more custom fields than Bullhorn ATS edition supports (2 in Bullhorn ATS), we provision a Custom Object to hold overflow fields.

Breezy tags (up to 250 per account) and sources (up to 250 per account) migrate as Bullhorn Candidate tags. Tags used for candidate classification (skills, seniority, source channel) map to Bullhorn's tag taxonomy. If the customer uses Breezy sources as a structured taxonomy (LinkedIn, Referral, Job Board), we map these to Bullhorn Candidate source fields or tags depending on the customer's reporting requirements.

Interview scorecards and structured ratings from Breezy migrate as fields on the Bullhorn Candidate record. Stage-level feedback (which interviewer rated which stage and with what score) preserves ordering against the original pipeline stage. Bullhorn's native rating model uses a 1-5 star system; Breezy's numeric or letter-grade scores are mapped to the nearest Bullhorn-compatible rating.

Internal comments and activity history tied to a Breezy candidate record migrate as timestamped Note entries attached to the Bullhorn Candidate. Formatting is preserved where possible. Note authorship and timestamp migrate to preserve the audit trail of who added what comment at what stage of the pipeline.

Resume files, cover letters, and uploaded candidate attachments are bundled with the candidate record. We preserve original filenames and file MIME types and reconstruct the attachment hierarchy in Bullhorn. Bullhorn supports file attachments on Candidate records via the Bullhorn REST API. Attachments are uploaded after candidate records are created, referencing the candidate by BullhornCandidateID.

Breezy offer records (available on Business tier and above) migrate to Bullhorn JobSubmission with offer status fields. The offer letter template and eSignature status cannot be transferred; these are platform-native features that require recreation in Bullhorn. We flag every offer record with missing templates in the migration inventory for the customer to address post-migration.

Breezy does not have a dedicated Company object for employer-of-record or client tracking, but candidate companies referenced in position records migrate as Bullhorn ClientCorporation. If the customer uses Breezy's company association on candidates, we create the ClientCorporation record before the candidate association. ClientCorporation address, industry, and billing contact fields populate from Breezy position and candidate company data where available.

Breezy branded career site pages, job board distribution settings, and employee referral portal configurations are platform-native and cannot be exported in a portable format. We do not migrate this object. We deliver a written inventory of active career site pages, active job board distributions, and referral portal settings for the customer's marketing team to rebuild in Bullhorn or a separate careers hosting tool.

Breezy Stage Actions (automated emails, SMS alerts, and task triggers that fire on pipeline stage changes) are tied to Breezy's internal messaging and integration infrastructure. Bullhorn WorkFlow automation handles similar triggers differently using Bullhorn's own action library. We do not migrate Stage Actions as executable code. We deliver a written inventory of every active Stage Action with its trigger condition, action type, and template content, mapped to the equivalent Bullhorn WorkFlow configuration for the customer's admin to rebuild.