Migrate your flair.hr data

Employee records are standard Salesforce Contacts with flair-specific custom fields for employment details, start dates, manager relationships, and department assignments. We migrate all standard and custom Contact fields, including multi-select picklists for locations and org-unit membership.

Candidates are stored as Salesforce Leads or as custom JobApplication objects depending on the flair configuration. We inspect the org's object model during discovery to determine the candidate object and migrate all fields including custom stages, source tracking, and rating scores.

Positions are custom objects that represent job openings, linked to Departments and Locations. We preserve the position hierarchy, reporting relationships, and any custom fields used for headcount planning or cost-center assignment.

Departments map to Salesforce Departments or custom organizational unit objects. We preserve the full department hierarchy and link each employee record to its owning department.

Locations are custom objects representing physical or legal entity work sites. We preserve location metadata including address, country, timezone, and any associated cost-center assignments.

Absence records are custom objects tracking leave types, start/end dates, approval status, and linked employee lookups. We preserve the full absence history including pending and approved records.

Time entries can use either custom TimeEntry objects or the standard Salesforce Event/Task objects depending on the flair version. We detect the underlying model and map hours, project codes, cost-center assignments, and approval status accordingly. Date formatting and timezone handling require explicit alignment during import.

Document storage in flair uses Salesforce Files and ContentDocumentLink. We migrate the binary attachments and preserve the linking relationships to employees or positions, but large document volumes may require chunked migration with checksum validation.

flair Workflows are Salesforce Flow-based step sequences for onboarding, performance reviews, and approvals. We map the final step-completion state as a target record rather than preserving the workflow sequence itself, and document which tasks were completed at migration time.

Performance review cycles, goals, OKRs, and feedback records are custom objects linked to Employees. We preserve review templates, ratings, goal progress, and historical review cycles in full.

Survey questions, response sets, and aggregate eNPS scores are custom objects. Individual anonymous survey responses are migrated as aggregate records where direct attribution is not required, per the destination platform's anonymization rules.

flair's extensibility model uses Salesforce custom objects and fields for industry-specific or customer-defined data structures. We inspect the org's custom object definitions during discovery and migrate them field-by-field, applying value mapping for picklists and lookups that may not exist in the target system.

Payroll data is linked to Employees via custom payroll objects that may integrate with DATEV, Sage, or AFAS depending on configuration. We migrate the payroll summary records and effective-dated compensation history, but actual payroll runs are typically re-entered in the destination payroll system.

Active job postings are custom objects linked to Positions. We migrate posting content, location assignments, and segment associations, but the branded career portal pages themselves require flair support to migrate URLs.