Migrate from Breezy HR to BambooHR

Breezy Candidates migrate to BambooHR Applicants tied to a BambooHR Job. We carry all standard fields: name, email, phone, social profiles, resume file, tags, and source attribution. Stage history is preserved as a chronological list of stage transitions with timestamps. Resume and attachment files migrate as BambooHR file attachments on the applicant record. If the candidate's most recent pipeline stage has no equivalent in the destination Job's stage set, we map to the nearest stage and flag the discrepancy for admin review.

Breezy Positions map directly to BambooHR Jobs. Job title, description, department, location, employment type (full-time, part-time, contract), and job status (open, closed, draft) migrate as-is. Breezy's position-level job board distribution settings (LinkedIn, Indeed, Glassdoor posting toggles) are platform-native and cannot be transferred; we document each distribution setting for the customer to re-enable manually in BambooHR's job distribution panel.

Breezy allows fully customizable pipeline stages per Position. BambooHR uses a stage set defined per Job with a fixed structure (Applied, Reviewed, Phone Interview, On-site Interview, Offered, Hired, Rejected). If the Breezy account uses fewer than eight distinct stage names across all positions, we create a consolidated stage set that maps Breezy's stage names to the closest BambooHR equivalents. If the Breezy account uses highly specific or more than eight stages, we document the original stage names and recommend a consolidation approach that the customer validates before import.

Breezy Users and hiring managers (Owner, Admin, Member roles) map to BambooHR Employees with the hiring-manager role. We resolve Breezy owner assignments on candidate records by matching email against the BambooHR employee directory. Breezy's permission model (Owner can do everything, Members have scoped access) maps to BambooHR's employee-level permissions for the hiring context, though BambooHR's full HRIS permissions are broader. Any Breezy user without a matching BambooHR employee record is held in a reconciliation queue for the admin to provision.

Breezy interview scorecards and rating data migrate as timestamped notes attached to the BambooHR applicant record. The structured rating fields (criteria names, numeric or checkbox scores) are preserved in a formatted note block with the interviewer's name and stage. We do not create structured custom fields in BambooHR for scorecard criteria unless the customer confirms the destination field names and data types during scoping.

Breezy offer records on Business tier migrate as offer details preserved in a formatted note on the BambooHR applicant record. The offer letter template and eSignature status (DocuSign or equivalent) cannot transfer because BambooHR generates offer letters from its own template engine. We extract the offer amount, start date, and offer terms from Breezy and include them as structured fields in the import payload for the customer's BambooHR admin to re-enter in the offer letter workflow.

Breezy tags (up to 250 per account) migrate as flat key-value tags on the BambooHR applicant. BambooHR's applicant tagging uses a simple tag field. We do not apply any taxonomy transformation unless the customer's Breezy tags serve a purpose that maps to BambooHR's Employee Status, Department, or Location fields, in which case we map them to the appropriate system field during import and flag the tag as deprecated.

Breezy source attribution (referral, job board, direct, agency) migrates to BambooHR's applicant source field. If Breezy uses a custom source taxonomy with more values than BambooHR's standard source picklist allows, we flag the discrepancy and map the excess to an 'Other' source with the original value preserved in a note on the applicant record.

Breezy internal comments and activity history tied to a candidate record migrate as timestamped notes on the BambooHR applicant. Comment formatting is preserved where the target system supports it. The author name and timestamp are retained with each note entry. If the candidate record has more than 50 comment entries, we batch them in groups of 50 to stay within BambooHR's note creation API limits.

Breezy custom candidate fields (Text, Date, Currency, Dropdown, Radio, Attachment) on Pro and Business plans map to BambooHR custom applicant fields of equivalent type. Text and Date migrate cleanly. Currency fields carry currency codes that we validate against BambooHR's currency format. Dropdown and Radio button options in Breezy are checked against BambooHR's allowed values during the pre-flight field compatibility check — if a Breezy option value does not exist in BambooHR, we flag it and the customer must add it to the BambooHR picklist before import. Attachment fields migrate as file uploads on the applicant record.

Breezy custom position fields migrate to BambooHR custom job fields. The same type-mapping rules apply as for candidate fields. Custom fields used for position-level tracking (e.g., approved headcount, hiring manager cost center) are preserved on the BambooHR Job record.

Breezy's branded career site pages, employee referral portal configuration, and job board distribution settings are platform-native and cannot be exported in a portable format. We do not migrate this object. We deliver a written inventory of every active Breezy career site page and job board posting toggle so the customer's admin can manually re-create them in BambooHR's job distribution panel.