HRMS migration
Field-level mapping, validation, and rollback between Breezy HR and Recruit CRM & ATS. We move data and schema; workflows are rebuilt natively in Recruit CRM & ATS.
Breezy HR
Source
Recruit CRM & ATS
Destination
Compatibility
11 of 12
objects map 1:1 between Breezy HR and Recruit CRM & ATS.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Breezy HR and Recruit CRM serve different recruiting market segments, and that difference shapes every migration. Breezy HR is an ATS built for SMB hiring teams who want a drag-and-drop interface without enterprise complexity; Recruit CRM is an ATS-plus-CRM built for recruitment agencies and executive search firms who need to manage candidates, clients, and placements in one system. Breezy stores pipeline stage definitions per-position; Recruit CRM uses a Master Pipeline with optional secondary pipelines. We split Breezy's per-position pipelines into Recruit CRM equivalents during scoping, map custom candidate fields by type (Text, Date, Dropdown, Radio, Currency, Attachment), and preserve stage history as ordered activity entries. Breezy's Bootstrap plan 30-day candidate visibility cap is a known migration risk that we detect before scoping begins. Automated Stage Actions, career site pages, and job board distribution settings do not migrate; we deliver a written inventory of Stage Actions requiring rebuild in Recruit CRM's automation builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Breezy HR object lands in Recruit CRM & ATS, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Breezy HR
Candidate
Recruit CRM & ATS
Candidate
1:1Breezy HR Candidate records migrate directly to Recruit CRM Candidate records. We carry over all standard fields (full name, email, phone, social profiles, resume file, tags, source attribution) and preserve the original candidate ID as a custom field breezy_id__c for cross-system audit. Breezy's per-candidate stage history migrates as ordered Candidate Activity entries in Recruit CRM reflecting the pipeline progression with timestamps.
Breezy HR
Position (Job)
Recruit CRM & ATS
Job
1:1Breezy HR Positions map 1:1 to Recruit CRM Jobs. Job title, department, location, employment type (full-time, part-time, contract), and job description migrate directly. Breezy's Position state (Open, On Hold, Closed) maps to Recruit CRM's Job status field. If Breezy positions include internal job codes, these migrate as a custom field job_code__c.
Breezy HR
Pipeline (per-position stage definition)
Recruit CRM & ATS
Master Pipeline + Secondary Pipeline
1:manyBreezy HR allows pipeline stage names and ordering to vary per Position. Recruit CRM uses a Master Pipeline at the account level with optional secondary pipelines scoped to specific jobs. We consolidate Breezy's per-position stage names into the Recruit CRM Master Pipeline as the primary stage set, then create secondary pipelines for positions with unique stage sequences that cannot be absorbed into the Master. The customer chooses the Master pipeline during scoping.
Breezy HR
Custom Candidate Field (Text, Date)
Recruit CRM & ATS
Custom Candidate Field
1:1Breezy HR custom fields of type Text and Date map cleanly to Recruit CRM custom fields of the equivalent type. Date fields preserve the original date format and timezone. We validate date ranges during pre-flight to catch Breezy dates that fall outside Recruit CRM's supported range.
Breezy HR
Custom Candidate Field (Dropdown, Radio)
Recruit CRM & ATS
Custom Candidate Field (Dropdown)
1:1Breezy HR Dropdown and Radio button fields store explicit option lists. We map these to Recruit CRM Dropdown fields, but the option set values must be verified against Recruit CRM's allowed values before import. Any option in Breezy that does not have a matching Recruit CRM value is flagged in the pre-flight report and the customer decides whether to add the missing option or map it to an 'Other' value.
Breezy HR
Custom Candidate Field (Currency)
Recruit CRM & ATS
Custom Candidate Field (Number)
1:1Breezy HR Currency fields carry a numeric amount and a currency code (USD, EUR, GBP). We migrate the numeric value to Recruit CRM's Number field. The currency code is preserved in a parallel text field currency_code__c so the customer can configure a currency field type post-migration if needed.
Breezy HR
Custom Candidate Field (Attachment)
Recruit CRM & ATS
Candidate Document
1:1Breezy HR Attachment-type custom fields hold files attached to a candidate record outside the main resume. We migrate these as Candidate Documents in Recruit CRM, preserving the original filename and file type. The attachment is linked to the candidate record via Recruit CRM's document attachment relationship.
Breezy HR
Tag
Recruit CRM & ATS
Tag
1:1Breezy HR Tags (up to 250 per account) migrate as Recruit CRM Tags. Tags are stored as flat key-value lists in both systems, so the mapping is direct. We deduplicate tag names during the transform phase to avoid creating duplicate tags in Recruit CRM.
Breezy HR
Source
Recruit CRM & ATS
Source
1:1Breezy HR Candidate Sources (up to 250 per account) map directly to Recruit CRM Candidate Sources. Source attribution on each candidate record migrates as the Source field value. If a candidate has multiple sources in Breezy, we concatenate them into a single Source field value in Recruit CRM and flag the record for the customer to manually split if needed.
Breezy HR
Hiring Team Member (User)
Recruit CRM & ATS
User
1:1Breezy HR Users and hiring team members migrate to Recruit CRM Users. We match by email address. Breezy's Owner/User role assignment maps to Recruit CRM's user role model, but permission structures differ; we flag any role that cannot map 1:1 and the customer assigns the correct Recruit CRM role post-migration. Team members without a matching email in the destination are held in a reconciliation queue for manual provisioning.
Breezy HR
Candidate Note and Comment
Recruit CRM & ATS
Note
1:1Breezy HR internal comments and activity history tied to a candidate migrate as timestamped Note entries in Recruit CRM. We preserve the comment author, timestamp, and full text content. Formatting (bold, italic, links) is preserved where Breezy's export format supports it.
Breezy HR
Scorecard and Rating
Recruit CRM & ATS
Evaluation
1:1Breezy HR interview scorecards and stage-level ratings migrate as Recruit CRM Evaluation records attached to the candidate. The evaluation criteria from Breezy become Evaluation field labels in Recruit CRM, and rating scores migrate as numeric values. We preserve the evaluation author and the stage at which the evaluation was conducted.
| Breezy HR | Recruit CRM & ATS | Compatibility | |
|---|---|---|---|
| Candidate | Candidate1:1 | Fully supported | |
| Position (Job) | Job1:1 | Fully supported | |
| Pipeline (per-position stage definition) | Master Pipeline + Secondary Pipeline1:many | Fully supported | |
| Custom Candidate Field (Text, Date) | Custom Candidate Field1:1 | Fully supported | |
| Custom Candidate Field (Dropdown, Radio) | Custom Candidate Field (Dropdown)1:1 | Fully supported | |
| Custom Candidate Field (Currency) | Custom Candidate Field (Number)1:1 | Fully supported | |
| Custom Candidate Field (Attachment) | Candidate Document1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Source | Source1:1 | Fully supported | |
| Hiring Team Member (User) | User1:1 | Fully supported | |
| Candidate Note and Comment | Note1:1 | Fully supported | |
| Scorecard and Rating | Evaluation1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Breezy HR gotchas
Bootstrap 30-day candidate visibility cap causes silent data loss
Add-on pricing inflates the real subscription cost significantly
Custom fields require destination mapping per field type
Breezy's own free migration is competitor-locked
Recruit CRM & ATS gotchas
API rate limits are license-scaled and can throttle bulk migration
Custom field schemas vary per organization and require field-level mapping
Files and email attachments require separate extraction and re-upload
Email sequences and automation logic do not transfer between platforms
Pair-specific challenges
Migration approach
Account tier verification and candidate accessibility check
We inspect the Breezy HR account plan tier before any other work begins. If the account is on the Bootstrap free plan, we run a candidate count check against the 30-day visibility window. Any candidate record added more than 30 days before scoping is invisible and must be surfaced by upgrading to a paid plan or by requesting a full data export from Breezy HR support before we proceed. We do not begin mapping or extraction on a Bootstrap account until we have confirmed all historical candidates are accessible. This step prevents an irreversible incomplete migration.
Discovery, object inventory, and pipeline design
We extract a full object inventory from Breezy HR: all active and archived positions, candidate records, pipeline stage definitions per position, custom field definitions (field name, type, option list), tags, sources, and user accounts. We pair this with a scoping call where the customer confirms the target Recruit CRM tier, the desired Master Pipeline stage sequence, and any positions that require a secondary pipeline. The discovery output is a written migration scope document covering record counts, pipeline mapping decisions, custom field mapping table, and a list of any Breezy data that will not migrate.
Pre-flight custom field and option set verification
We run a pre-flight check on all Dropdown and Radio custom fields by querying the option values in Breezy HR against the target Recruit CRM field's allowed values. Any value present in Breezy but absent in Recruit CRM is listed in the pre-flight report with a recommendation to add the missing option or map it to an existing value. This check runs before any data extraction and must be resolved before the migration extraction phase begins. Currency field currency codes are also verified against Recruit CRM's supported currency list.
Sandbox migration and reconciliation
We run a full migration into Recruit CRM's sandbox or trial environment using production-like data volume. The customer's recruiting operations lead reviews record counts (Candidates in, Jobs in, Notes in, Evaluations in), spot-checks 20-30 random candidate records for field accuracy, verifies that pipeline stage history is ordered correctly, and confirms that custom field values match the source. The customer signs off the sandbox migration before we proceed to production. Any mapping corrections are made during this phase.
Production migration in dependency order
We run the production migration in record-dependency order: Users (provisioned manually by the customer, validated by email match), Jobs (from Breezy Positions), Master Pipeline and secondary pipelines configured in Recruit CRM before candidate import, Candidates with stage history (activity entries ordered by timestamp), Tags and Sources (deduplicated during transform), Custom Field values (after option set verification), Notes and Evaluations (linked to their parent Candidate record). Each phase emits a row-count reconciliation report before the next phase begins. Attachments and resume files are bundled by candidate and uploaded to Recruit CRM's document storage.
Cutover, delta sync, and Stage Action inventory handoff
We freeze Breezy HR write access during the cutover window, run a final delta migration of any records modified during the migration, then enable Recruit CRM as the system of record. We deliver the Stage Action inventory document listing every automated email, SMS, and alert that was active in Breezy HR, with a recommended Recruit CRM automation equivalent for each. We support a three-day hypercare window where we resolve any reconciliation issues. We do not rebuild Breezy Stage Actions as Recruit CRM automations inside the migration scope.
Platform deep dives
Breezy HR
Source
Strengths
Weaknesses
Recruit CRM & ATS
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Breezy HR and Recruit CRM & ATS.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Breezy HR: Not publicly documented in official API reference.
Data volume sensitivity
Breezy HR exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Breezy HR to Recruit CRM & ATS migration scoping. Not seeing yours? Book a call.
Walk through your Breezy HR to Recruit CRM & ATS migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Breezy HR
Other ways to arrive at Recruit CRM & ATS
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.