Migrate from Breathe to Crelate

Breathe Employee records map to Crelate Candidate records. We extract name, contact details, job role, department, start date, employment status, and custom fields from the People Data Export and map them to Crelate's Candidate standard fields (FirstName, LastName, Email, Phone, Address) and custom Candidate fields for role-specific data. The candidate record in Crelate becomes the primary HR record in the destination system. Note that Crelate's Candidate object is optimised for talent acquisition workflows (sourcing, submissions, placements) rather than ongoing employment management; HR administrators should plan for this scope difference.

Breathe custom fields on Employee records migrate to Crelate Candidate custom fields. We extract the field name, data type, and value from the People Data Export and create equivalent Crelate custom fields of matching type (text, number, date, picklist, checkbox) during the pre-migration schema build. Any custom fields referencing non-standard modules or bespoke configurations are flagged during the data audit and documented separately for manual migration if the data is recoverable from the export.

Breathe absence records (annual leave, sick leave, other absence types) with dates, types, balances, and approval status merge into the Candidate record as custom fields and dated notes. Leave balances at migration date are stored as custom numeric fields (e.g., annual_leave_remaining__c, sick_leave_taken_ytd__c). Full absence history is preserved as dated notes on the Candidate record with type, date range, and status so that the HR continuity is visible without relying on a native absence management module that Crelate does not provide.

Breathe sickness entries — distinct from standard absence records — migrate as dated notes on the Crelate Candidate record. We preserve dates, reason (where provided), and Fit Note references as note content. Sickness history is not a native Crelate object; the data is preserved as structured notes rather than a typed record, which limits future reporting within Crelate to note content searches rather than sickness-specific dashboards.

Breathe performance review records (review cycle, ratings, comments) migrate as notes attached to the Candidate record with the review period and overall rating captured in custom fields. Review templates and the structured rating schema from Breathe are documented in the handoff deliverable so that the customer can recreate review cycles in Crelate's workflow system or a separate HR tool. Crelate does not have a native performance review module; this is an inherent gap for HR-centric use cases.

Breathe's Remuneration Report (salary, additional payments, benefits, auto-enrolment status) migrates as custom fields on the Crelate Candidate record. Fields include current_salary__c, additional_payments__c, benefit_details__c, and auto_enrolment_status__c. Payroll export data from Reports > Payroll exports is extracted as a structured record and mapped accordingly. Note that Crelate does not have a native payroll object; this data serves as candidate compensation history rather than an active payroll record.

Breathe onboarding task lists, document checklists, and workflow step completion status migrate as notes on the Candidate record with a summary of completed and pending items. The onboarding workflow definition itself is a configuration object in Breathe that does not migrate; we deliver a written inventory of the onboarding tasks and their completion status for the customer's admin to rebuild as Crelate workflow tasks or to manage manually. Candidates at the offer or onboarding stage in Breathe become Candidates with onboarding notes in Crelate.

Breathe stores documents in two silos — Company documents (policies, handbooks, templates) and Employee documents (contracts, certifications, ID records) — with no bulk export API. Documents must be downloaded individually from the UI. We do not migrate documents as part of standard scope because Crelate's attachment model (linked to a specific record) does not support Breathe's dual-silo document structure. We deliver a guided checklist for manual document archiving, prioritising Employee documents (contracts, certifications) that are most critical for HR continuity. Company documents are documented as a separate manual step.

Breathe employment history records (job role changes, department transfers, promotions) attach to the Employee record and migrate as dated notes on the Crelate Candidate record. We preserve role title, department, effective date, and any notes from the employment history entry. This preserves the continuity of the employee's internal career record within the candidate timeline.

Breathe users (HR administrators, managers) referenced on Employee records are mapped to Crelate User records by email match. We extract distinct owner references from the People Data Export and reconcile against the destination Crelate tenant's user list. Any Breathe user without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before migration resumes. Owner assignments on absence records and onboarding tasks resolve through this user mapping.

Breathe Learn completion records (GDPR awareness, health and safety compliance training) may not be included in the standard People Data Export if the customer is on a lower Breathe tier. We audit the export during scoping and flag any missing training modules. Where data is available, completion records migrate as notes on the Candidate record with course name, completion date, and status. Compliance training documentation that requires audit evidence should be archived separately from the Crelate migration as part of the manual document step.

Organisations on Breathe lower tiers may have advanced reporting, Insights dashboards, and API access points restricted or unavailable. We review the customer's current Breathe tier during scoping and request exports from the appropriate licensed module. Any data that is tier-gated and unavailable for export is documented as a gap in the migration scope and listed in the handoff deliverable so that the customer can evaluate whether the equivalent functionality is available in Crelate or requires a separate tool.