Migrate from Breezy HR to Crelate

Breezy Candidate records map to Crelate Person records. Standard fields (name, email, phone, social profiles, address) transfer directly. We preserve stage history as Crelate activity entries ordered by timestamp. Breezy's resume files transfer as attachments to the Person record. If the source Breezy account is on a Bootstrap plan and candidates older than 30 days exist, we flag this before migration begins and advise upgrading to a paid plan so all records are accessible via export. Tags and sources from Breezy map to Crelate Tags and Source tracking respectively.

Breezy Position records map directly to Crelate Job records. Job title, description, department, location, employment type, and salary fields transfer as typed fields. Breezy's position-level pipeline stage definitions (stage name, order, and probability) map to Crelate's job-level pipeline stage configuration. Active vs archived status transfers so that archived positions can be flagged for the customer to handle in Crelate post-migration.

Breezy allows multiple named pipelines per position on Growth and Business plans. Crelate uses an account-level pipeline model with job-level stage customization. We split Breezy's per-position pipeline definitions and map them to Crelate's pipeline configuration per job. If a Breezy account has created custom stage names across multiple positions, we consolidate stage naming to avoid proliferation in Crelate and flag discrepancies for the customer to resolve. Stage probability percentages transfer from Breezy to Crelate's stage-level probability values.

Breezy custom candidate fields (Text, Date, Currency, Dropdown, Radio button) map to Crelate custom fields on the Person record. Text and Date types map cleanly. Currency fields carry currency codes that we validate against Crelate's currency configuration. Dropdown and Radio button options require verification: if the destination Crelate field does not include matching options, we flag the discrepancy in the scoping report and the customer must clean up option sets in Crelate before we proceed with import. Custom Position fields map to custom fields on the Job record with equivalent verification.

Breezy tags (up to 250 per account) transfer as flat key-value lists to Crelate Tags. Tag names preserve case-sensitive spelling. If the customer uses tags for categorization beyond simple keyword labels, we document the tag taxonomy in the scoping report for the customer's team to validate against Crelate's tagging model. Tags used for candidate classification migrate as-is; Crelate supports tag-based filtering in search and list views.

Breezy candidate sources (up to 250 per account) transfer to Crelate Source tracking on Person records. Source names preserve and are available as filterable attributes in Crelate reporting. Source attribution is tied to the candidate record at import time, preserving the original source for each candidate for reporting on sourcing effectiveness.

Breezy Owner and User assignments map to Crelate Users. Role names (Owner, Admin, User) from Breezy map to Crelate's permission levels. We resolve by email match. Any Breezy User without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before the final migration phase runs. Breezy's hiring manager role assignments on individual positions map to Crelate's hiring team access on the corresponding Job.

Internal comments and activity history tied to a Breezy candidate record transfer as timestamped activity notes on the Crelate Person record. Formatting is preserved where the destination supports rich text. Activity ordering is maintained by setting the activity timestamp to the original Breezy creation date, preserving the chronological context of the hiring conversation.

Interview scorecards and rating data migrate as structured entries attached to the Person record in Crelate. Stage-level feedback is preserved in the same order as Breezy's pipeline stages, maintaining the interview evaluation timeline. Rating values transfer as numeric or text fields depending on the rating scale used in Breezy. Custom scorecard templates are documented in the scoping report for the customer's team to recreate in Crelate's scorecard builder.

Offer records migrate from Breezy (available on Business tier and above) to Crelate's offer tracking where available. Offer letter templates and eSignature status do not transfer; these are platform-native and must be recreated in Crelate. We migrate the offer record metadata (candidate, job, salary, start date, status) and flag the template gap in the scoping report.

Resume files, cover letters, and uploaded candidate attachments transfer as documents on the Crelate Person record. We preserve original filenames and file types. The attachment hierarchy (which file is the primary resume vs secondary attachment) is reconstructed during import. File size and format limits are validated against Crelate's upload constraints during scoping.

Breezy's 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 list of every active career site page and job board connection in Breezy so the customer's team can recreate them in Crelate's career site builder or reconfigure job board integrations post-migration.

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. We do not migrate them. We deliver a written inventory of every active Breezy Stage Action with its trigger, conditions, and actions for the customer's team to rebuild in Crelate's workflow builder or a connected tool like Zapier or Make.