Migrate from flair.hr to Crelate

flair Employee records live on Salesforce Contact with custom flair fields for employment details, start dates, manager relationships, and department assignments. We migrate all standard Contact fields plus flair custom fields that map to Crelate Contact fields. Employment status, job title, department, and manager hierarchy transfer as Crelate custom fields on Contact. Flair's manager relationship (lookup to another Contact) maps to a custom Crelate Contact field rather than a native hierarchy, since Crelate does not enforce a Contact-to-Contact manager relationship model.

flair Candidates are stored as Salesforce Leads or custom JobApplication objects depending on the configuration. We inspect the org's object model during discovery to determine which object holds candidate data. Leads with a source of recruiting map to Crelate Contact. Any candidate records with an active application status on a Position map to Crelate Contact linked to the corresponding Job record in Crelate. The original flair candidate source, stage, and rating migrate as Crelate custom Contact fields.

flair Positions are custom objects representing job openings linked to Departments and Locations. We map each Position to a Crelate Job record, preserving the job title, description (as the Job description field), status (open/closed), department assignment, and location. Crelate's Job object does not enforce a department hierarchy the same way flair does, so we create a Crelate custom field for department provenance and link the Job to a Crelate Company representing the hiring organization.

flair Departments are Salesforce custom objects or the standard Department object, with a full organizational hierarchy. Crelate's object model does not have a native organizational unit object. We handle this as a lookup mapping: top-level departments migrate as Crelate Companies (representing internal cost centers if the organization uses Crelate for internal hiring), and sub-departments migrate as custom field values on the Job record. For organizations using Crelate primarily for external candidate tracking, we consolidate department data into a multi-select Crelate custom field on Contact.

flair Locations are custom objects with address, country, timezone, and cost-center assignments. Crelate has a location field on Job records but no dedicated Location object. We map flair Location address data to the Job's location field, country to a Crelate custom Contact field, and timezone to a custom field for reference. Cost-center assignments on Location do not have a Crelate equivalent and are preserved in a custom text field.

Crelate has no absence management module. Absence records from flair are out of scope for this migration. We document the absence types, entitlement balances, and pending absence requests in a written handoff report so that the customer's HR admin can re-enter balances in a dedicated absence management tool or a supplemental Crelate integration.

flair uses either a custom TimeEntry object or standard Salesforce Event/Task records for time tracking depending on the deployment version. Crelate does not have a native time tracking module. Time entry data is out of scope. We detect which flair time tracking model is active during schema inspection and document any hours, project codes, or cost-center assignments that the customer may need to re-enter in their payroll or timekeeping system.

Document storage in flair uses Salesforce Files (ContentDocument) attached to Employees, Candidates, or Positions via ContentDocumentLink. We migrate binary file attachments and preserve the linking relationships to the corresponding Crelate Contact or Job record. Large document volumes may require chunked migration to avoid API timeout. Resume files are linked to the Contact record as primary; any additional supporting documents are attached to the same Contact.

flair Performance Review cycles, goals, OKRs, and feedback records are custom objects linked to Employees. Crelate has no native performance management module. We do not migrate performance data. We deliver a written inventory of the review templates, historical ratings, goal progress, and review cycle records for the customer's HR admin to re-enter in a dedicated performance management tool.

flair Engagement Survey questions, response sets, and aggregate eNPS scores are custom objects. Crelate has no survey or engagement module. We do not migrate survey data. We document the survey structure, question sets, and aggregate response history in a written handoff for the customer's HR admin.

flair Workflows are Salesforce Flow-based step sequences for onboarding, performance reviews, and approvals. We do not migrate Flows as code. We inspect the active Flows in the flair Salesforce org during discovery, document the step sequence, trigger conditions, approval logic, and expected outcomes, and deliver this as a written rebuild guide. The customer's admin or a Crelate implementation partner rebuilds these in Crelate's automation model (activity templates and pipeline automation) post-migration.

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 via Salesforce schema describe. Any custom object linked to an Employee or Candidate migrates to Crelate custom fields on the Contact or Job record. Any custom object representing a standalone entity without a Crelate equivalent is documented as a written schema map for manual re-creation in Crelate.

flair payroll data is linked to Employees via custom payroll objects that may integrate with DATEV, Sage, or AFAS. Crelate has no payroll module. We do not migrate active payroll runs, payroll summary records, or effective-dated compensation history. We deliver a written handoff of historical payroll summary records as read-only reference data for the customer's payroll team to re-enter in the destination payroll system.

Active job postings are custom flair objects linked to Positions. We migrate posting content, location assignments, and segment associations to Crelate Job records with the job description, requirements, and location preserved. The branded career portal pages themselves do not migrate; Crelate's career page and job board distribution tools (Indeed, LinkedIn, Glassdoor, and others via Crelate's integrations) replace the flair career portal. URL preservation requires manual reconfiguration in Crelate's job board settings.