Migrate from Breezy HR to Zoho Recruit

Breezy HR Candidate records map 1:1 to Zoho Recruit Candidate records. Standard fields (name, email, phone, social profiles, tags, source) migrate directly. We enforce Zoho's mandatory Last Name field: any Breezy candidate with a blank last name is flagged and defaulted to 'not provided' per Zoho's import requirements, then reconciled with the customer before final import. Resume files and attachments migrate as Zoho Recruit attachments linked to the candidate record with original filenames preserved.

Breezy HR Position records map to Zoho Recruit Job Opening. We carry over job title, description, department, location, state, and job type. Position status (open, closed, archived, draft) maps to Zoho Job Opening status. The Breezy Position owner maps to the Zoho Recruit recruiter assignment.

Breezy HR allows different pipeline stage definitions per position. Zoho Recruit uses global or group-level pipelines with shared stage names and probabilities. When migrating positions with distinct stage sets, we split them into the closest matching Zoho pipeline configuration and preserve the original per-position stage order as a custom text field on the Job Opening for audit. The customer's admin selects the target Zoho pipeline during scoping.

Breezy HR stores the complete stage history for each candidate in a position, including entry timestamps and optional stage-leave reasons. We migrate this as a structured comment or activity entry on the candidate's Job Opening association in Zoho Recruit, preserving the chronological stage progression. Stage probability percentages do not transfer as live pipeline metrics but are stored as reference notes.

Breezy HR allows up to 250 tags per account. We migrate tags as Zoho Recruit tags (flat key-value) or as a multi-select picklist custom field depending on how the customer intends to use them post-migration. Tags used for candidate classification map to picklist; tags used for filtering or workflow triggers map to Zoho tags. The customer chooses during scoping.

Breezy HR candidate sources (LinkedIn, Indeed, Referral, etc.) map to Zoho Recruit Source picklist values. If Zoho's destination account lacks a matching source value, we flag it for option-set creation before candidate import. Sources with zero candidates are excluded from migration.

Breezy HR Text and Date custom fields map cleanly to Zoho Recruit Text and Date custom fields. We create the destination custom fields in Zoho via the Layout Editor during schema setup, preserving field labels and data types. Date formats are normalized to ISO 8601 (YYYY-MM-DD) during transform to match Zoho's expected import format.

Breezy HR Dropdown and Radio button fields map to Zoho Recruit Picklist or Multi-select Picklist fields. Option values must match exactly. We run a pre-flight check comparing Breezy's option sets against Zoho's defined picklist values and flag any discrepancy as a cleanup task for the customer's admin to resolve before candidate import, because mismatched picklist values block record insert in Zoho.

Breezy HR Currency fields carry currency codes (USD, EUR, etc.). Zoho Recruit does not have a native currency field type for custom fields. We migrate currency values as formatted text (e.g., '1500 USD') into a Zoho Text field and flag this for the customer's admin to determine whether a custom numeric field without currency symbol is preferred for calculations.

Breezy HR Owner, User, and team member assignments per position map to Zoho Recruit Users. We match by email address. Any Breezy team member without a matching Zoho Recruit User goes to a reconciliation queue; the customer's admin must provision the missing Zoho users before the Hiring Team phase of migration runs. Breezy role names (Owner, Admin, Recruiter, Interviewer) map to Zoho Recruit role names, which the admin configures in Setup > Users & Control.

Breezy HR internal comments and activity history tied to a candidate migrate as timestamped comment entries in Zoho Recruit attached to the candidate record. Formatting is preserved where possible; rich text notes convert to plain text with line breaks maintained. The comment author maps to the Zoho Recruit User by email match.

Breezy HR interview scorecards and per-stage rating data migrate as structured feedback entries on the candidate record in Zoho Recruit. Stage-level feedback is attached to the relevant Job Opening association with the interviewer's name and timestamp preserved. If Breezy's scorecard uses a numeric rating scale, we migrate it as a custom field on the candidate; the customer's admin maps the scale to Zoho's feedback format post-migration.

Breezy HR offer records (Business tier and above) migrate to Zoho Recruit Job Offer if the destination Zoho edition supports it. Offer letter templates and eSignature status cannot be transferred; these are noted as items for manual recreation. Offer metadata (salary, start date, position title, candidate name) migrates as structured fields.

Resume files, cover letters, portfolio uploads, and candidate attachments bundle with the candidate record. We preserve original filenames and MIME types and reconstruct the attachment hierarchy in Zoho Recruit. Files are uploaded via Zoho's attachment API after the parent candidate record exists in the destination.

Breezy HR Candidate Pools are named collections of candidates not tied to a specific position. We map them to Zoho Recruit Candidate Groups or to a tag-based organization, depending on the destination account's existing structure. If Zoho Groups do not exist, we create them during schema setup. Candidates in multiple pools receive multiple group assignments in Zoho.