Migrate your Breezy HR data

Candidates are the primary object in Breezy. We migrate all standard fields (name, email, phone, social profiles, resume, tags, sources) and preserve stage history per pipeline. Custom candidate fields require destination mapping as field types (text, date, currency, dropdown, radio) must be matched to the target system's equivalents.

Positions map 1:1 to destination job/posting objects. We carry over job title, description, department, location, state, and job type. Pipeline stage definitions per position are migrated as ordered stage arrays, with stage names preserved to maintain the candidate journey context.

Pipelines are customizable per position in Breezy. When migrating to a destination with a global or account-level pipeline model, we split Breezy's per-position pipelines into the destination's equivalent structure and flag any stage name mismatches for review.

Custom candidate fields and custom position fields are supported on Pro plans. We map them field-by-field, but dropdown and radio button options must be verified against the destination's allowed values — mismatched option sets require manual cleanup after migration.

Breezy allows up to 250 tags and 250 sources per account. We migrate them as flat key-value lists. If the destination uses a different taxonomy (e.g., labels, segments), we map them accordingly and flag any that exceed the destination's character limits.

Users, hiring managers, and team members are migrated with their roles and permissions. Breezy's Owner/User assignment must be mapped to the destination's equivalent role model, as permission structures differ significantly between ATS platforms.

We preserve all internal comments and activity history tied to a candidate record. These are migrated as timestamped entries attached to the candidate object. The formatting is preserved where possible; HTML-formatted notes may require re-rendering on the destination platform.

Interview scorecards and rating data are migrated as structured fields on the candidate record. Stage-level feedback is preserved in the same order as Breezy's pipeline stages, maintaining the interview evaluation timeline.

Offer management is available on Business tier and above. We migrate offer records where they exist, but offer letter templates and eSignature status cannot be transferred — these are recreated at the destination using the source offer data as reference.

Breezy's branded career site pages, job board distribution settings, and employee referral site configurations are platform-native and cannot be exported in a portable format. We do not migrate this object; the destination's career site must be rebuilt.

Resume files, cover letters, and uploaded candidate attachments are bundled with the candidate record during migration. We preserve original filenames and file types and reconstruct the attachment hierarchy at the destination.

Breezy's Stage Actions (automated emails, SMS, alerts triggered on pipeline stage changes) are tied to Breezy's internal messaging and integration infrastructure and cannot be replicated in a portable format. Workflow logic must be rebuilt at the destination using the source workflow definitions as a reference guide.