Migrate from flair.hr to BambooHR

flair Employees are Salesforce Contacts with flair-specific custom fields for employment details. We export via the Salesforce REST API using the connected app scoped to the flair namespace. Fields including hire date, job title, employment status, manager (as Contact lookup), department, and cost center map to BambooHR employee profile fields. We resolve the Salesforce manager Contact lookup to a BambooHR supervisor relationship during the transform step before import. Custom flair employment fields require schema discovery to enumerate and map to BambooHR custom fields.

Candidates in flair can be stored as Salesforce Leads or as custom JobApplication objects depending on the deployment configuration. We inspect the org schema during discovery to identify the active candidate object, then export accordingly. BambooHR's applicant record accepts name, contact info, job applied to, status, source, and custom fields. Application history and stage progression migrate as status records on the Applicant object. Active job postings from flair's Position objects link to BambooHR job openings by title and location match.

flair Positions are Salesforce custom objects representing job openings with fields for title, department, location, employment type, and headcount. We map Position title to BambooHR Job name, Position employment type to Job employment status, and Position location to a BambooHR location lookup. Open and closed position status migrates to BambooHR Job status (Open/Closed). Compensation details stored in custom Position fields map to BambooHR custom fields on the Job record if configured.

flair Departments map directly to BambooHR Departments. We preserve the full department hierarchy (parent department relationships) by resolving parent department IDs during the import. Each Employee record is linked to its owning department via the BambooHR department lookup. Departments with associated cost-center assignments in flair carry those as department-level custom fields in BambooHR.

flair Locations are custom objects representing physical or legal-entity work sites with address, country, timezone, and cost-center metadata. We create BambooHR Locations with address, country, and timezone preserved. Multi-country and multi-subsidiary configurations in flair require a separate BambooHR Location record per site.

flair Absence records are custom objects tracking leave type, start and end dates, approval status, and linked employee lookups. We migrate the full absence history including pending and approved records into BambooHR Time Off. Leave type names from flair map to BambooHR Time Off Type values (PTO, Sick, Personal, etc.), which the customer configures during BambooHR setup. Historical approved absences import with original dates and leave-type assignments.

flair uses either a custom TimeEntry object or standard Salesforce Event/Task records for time tracking depending on the deployment version. We detect the underlying model via schema describe during discovery and apply the appropriate field mapping. Hours, project codes, and cost-center assignments map to BambooHR time tracking entries. Custom time-tracking fields from flair's custom TimeEntry object require BambooHR custom field equivalents, which are limited to certain field types per the BambooHR API. Large time-entry datasets (over 100,000 rows) use batched import with API rate-limit handling.

flair document storage uses Salesforce Files (ContentDocument) and ContentDocumentLink relationships to employee or position records. We export the binary file content and metadata via the Salesforce API and attach them as BambooHR Employee Documents linked to the corresponding employee record. Large document volumes require volume-based scoping and may exceed typical migration timelines if not flagged during discovery.

Performance review cycles, goals, OKRs, and feedback records are custom objects in flair linked to Employees. BambooHR supports one review type per cycle (self-assessment, manager assessment, goals, 360). If the customer's flair instance uses multiple simultaneous review cycle templates, we consolidate into BambooHR's single review type, mapping cycle name, review period, and ratings. Rating scale values require cross-walking per the customer's configured flair scale before import. Historical completed reviews migrate as read-only records.

Survey questions, response sets, and aggregate eNPS scores migrate as BambooHR Employee Satisfaction records. Individual anonymous survey responses migrate as aggregate summary records because direct attribution is not available and BambooHR's satisfaction module does not store per-question employee-level responses. Survey metadata (survey name, date, participation rate) carries forward. If flair stores identifiable individual responses, those map to BambooHR custom fields if configured; anonymous-only surveys carry as aggregate.

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 enumerate all custom fields. Each custom flair field maps to a BambooHR custom field where field type compatibility is supported. BambooHR custom fields are type-restricted (text, date, number, dropdown, checkbox) and scoped per employee tab; they do not sync via BambooHR integrations. Fields that do not have a compatible BambooHR type are flagged in the scoping spreadsheet for customer decision before import.

Payroll summary records, effective-dated compensation history, and benefit enrollment data migrate as read-only historical records in BambooHR's employee compensation and benefits sections. Active payroll runs, DATEV, Sage, or AFAS integration configurations do not migrate because they are tightly coupled to the source system's payroll engine. We recommend involving the customer's payroll team during scoping to confirm which historical records are needed and to plan for re-entry of active payroll runs in BambooHR or its connected payroll provider.