Migrate from flair.hr to Zoho Recruit

flair Candidates are stored on Salesforce Lead or a custom JobApplication object depending on the deployment configuration. We inspect the org's object model during discovery to determine which object holds candidate records, extract all standard fields (name, email, phone, source, status) plus any custom fields, and import into Zoho Recruit's Candidate module. Zoho requires Last Name as a mandatory field; any flair Candidate without a last name value is written as 'Not Provided' with a note in the reconciliation report.

flair Positions are custom Salesforce objects representing job openings, linked to Departments and Locations. We preserve the position title, department assignment, location, employment type, and salary range fields. Position status (Open, On Hold, Closed) maps to Zoho Job Opening status. The position hierarchy and reporting relationships used for headcount forecasting in flair have no direct Zoho Recruit equivalent; we document these as custom fields or note them as requiring a rebuild in Zoho's custom fields section.

flair JobApplication records link a Candidate to a Position with stage timestamps and application source. We map each application to a Candidate record in Zoho Recruit associated with the corresponding Job Opening, preserving the application date, current stage, and source channel. Application stage history (applied, screening, interview, offer, hired, rejected) migrates as stage timestamps on the Zoho Candidate record.

flair Departments map to Salesforce Departments or custom organizational unit objects with a full hierarchy. Zoho Recruit has no native department object. We create a Department custom field on both Job Opening and Candidate modules and populate it with the department name from flair. If the flair org uses a multi-level department hierarchy (e.g., Engineering > Frontend), we flatten it to a single text field with a slash separator (Engineering / Frontend) to preserve the full path.

flair Locations are custom objects representing physical or legal entity work sites with address, country, timezone, and cost-center data. We extract the primary location name and address and populate Zoho's standard Job Location field. For multi-location organizations, we add a secondary locations custom field. Cost-center assignments and timezone metadata have no Zoho Recruit equivalent and are documented as requiring a custom field configuration post-migration.

flair Absence records track leave types, start/end dates, approval status, and employee lookups. Zoho Recruit is an ATS, not an absence management system. Absence records do not have a destination object in Zoho Recruit. We do not migrate absence data. If the customer needs absence tracking in the Zoho ecosystem, we recommend Zoho People as a parallel or follow-on implementation and flag which employees have open absence balances for manual re-entry.

flair Time Entries use either custom TimeEntry objects or standard Salesforce Event/Task records depending on the deployed version. We detect the underlying model during schema inspection and document which model is active, but time tracking records are out of scope for Zoho Recruit's data model. Time entries are flagged as requiring a separate time-tracking solution if the customer needs them post-migration.

flair Document storage uses Salesforce Files and ContentDocumentLink linked to employees or positions. We migrate binary attachments (resumes, cover letters, certifications) linked to Candidate records as Zoho Recruit attachments. Large document volumes may require batch processing due to Zoho's file size limits. Documents linked to non-recruiting objects (employees, payroll records) are out of scope for Zoho Recruit migration and are flagged for the customer's admin.

flair Performance Review cycles, goals, OKRs, and feedback records are custom objects linked to Employees. Zoho Recruit does not have a performance management module. We do not migrate performance data. For customers who need performance tracking in Zoho, we recommend Zoho People as the performance management layer and note that flair performance history requires a separate export and import process.

flair Engagement Surveys (questions, response sets, aggregate eNPS scores) are custom objects. Zoho Recruit has no survey or engagement module. We do not migrate survey data. Aggregate eNPS scores and survey questions are documented in a written handoff note for the customer's admin if they plan to run surveys through a separate tool post-migration.

flair Employees are Salesforce Contacts with flair-specific custom fields for employment details, start dates, manager relationships, and department assignments. We extract current employees as Contacts in Zoho Recruit (if the customer uses Zoho Recruit's staffing agency mode with an internal hiring function) or as Candidates for any employees who are also hiring managers or referral sources. Employment-specific fields (start date, manager, compensation, employment type) that have no Zoho Recruit equivalent are documented as requiring a custom field configuration.

flair Workflows are Salesforce Flow-based step sequences for onboarding, performance reviews, and approvals. We do not migrate workflow definitions as code. We deliver a written inventory of every active flair Workflow with its trigger, conditions, step sequence, and approval chain, plus a recommended Zoho Recruit Blueprint equivalent. The customer's admin or a Zoho partner rebuilds the hiring pipeline Blueprint in Zoho Recruit 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 a Salesforce schema describe call, enumerate all custom fields, and map them to Zoho Recruit custom fields on the appropriate standard module. Any custom objects that have no Zoho Recruit module equivalent are documented with their field list for manual rebuild as custom fields or as part of a Zoho Creator application if the customer requires a standalone custom app.

flair Payroll summary records, effective-dated compensation history, and benefit enrollment data are linked to Employees via custom payroll objects that integrate with DATEV, Sage, or AFAS. Zoho Recruit has no payroll module. We do not migrate payroll data. Payroll summary records are flagged as requiring manual re-entry in the destination payroll system or a separate payroll migration engagement.