Migrate from SupportFinity to Zoho Recruit

SupportFinity Jobs map to Zoho Recruit Job Openings. We map job title, description, department, location, and status directly. SupportFinity Growth offers unlimited job postings; Zoho Recruit Standard limits active jobs to 10 per recruiter, Professional to 250, and Enterprise to 750. We flag active job count against the target Zoho tier before migration and recommend Enterprise if the customer's job volume exceeds the Standard cap.

Candidate profiles migrate 1:1 for name, email, phone, resume/CV, work history, and education. SupportFinity's 2.4 billion profile global talent cloud enrichment is a read-only source layer and does not transfer as data. The mandatory Last Name field in Zoho Recruit requires that any SupportFinity candidate record without a last name be assigned 'not provided' or a similar placeholder before import, otherwise the record is ignored per Zoho's import rules. We pre-process all candidates for this constraint before loading.

Application records link a Candidate to a Job with timestamps, source channel, and current pipeline stage. In Zoho Recruit, this association is represented by a Candidate record linked to a Job Opening via the Candidate subform or a junction module. We preserve the full application history including withdrawn and rejected states, mapping source channel and stage to Zoho Recruit's candidate status and source tracking fields.

SupportFinity DISC+ scores and custom AI-generated rubric results map to Zoho Recruit custom fields on the Candidate module. We create custom Number or Picklist fields named with the assessment identifier (e.g., DISC_D_score, Atom_rubric_score) and populate the values. Custom rubric definitions themselves (the scoring rubric structure) do not transfer as Zoho configuration objects; they are documented in the migration inventory for manual rebuild if needed.

Interview records (scheduled time, interviewer assignment, notes) map to Zoho Recruit's Interview module with interviewer, candidate, job, scheduled time, and status preserved. Interview notes migrate as free-text fields. Sia interview recordings are binary files attached to SupportFinity interview records and require a separate file transfer pass: we download recordings by filename reference and upload as Zoho Recruit file attachments linked to the corresponding Interview record.

SupportFinity's configurable pipeline stages (Screening, Interview, Offer, Hired, etc.) map to Zoho Recruit's candidate status workflow per Job Opening. Stage IDs and labels are tenant-specific in SupportFinity; we map them to Zoho Recruit's candidate status picklist values, flagging any stages that require custom status creation in the destination. Stage probability percentages have no Zoho Recruit equivalent and are documented for the customer's admin.

SupportFinity user accounts (Recruiter, Hiring Manager, Admin roles) map to Zoho Recruit Users by email address match. The Growth plan's 3-seat cap means larger teams will have fewer SupportFinity users than candidates. A Zoho Recruit constraint applies: any User who already has a separate personal Zoho Recruit account must close that account before they can be imported into the organization's Zoho Recruit tenant. We reconcile the user list during scoping and flag any email conflicts.

Free-text notes attached to candidates or applications migrate as Zoho Recruit Notes linked to the corresponding Candidate record. Timestamps and author attribution are preserved. We map the note body and set the associated record reference (Candidate or Job Opening ID) during import.

SupportFinity's unlimited candidate mailboxes map to Zoho Recruit's candidate communication threads. Email body and SMS content transfer as Activity records or Notes on the Candidate. Thread structure and attachment handling requires mapping to Zoho Recruit's conversation model; we document any threads that cannot map cleanly for manual reconciliation.

Job-specific screening questions and candidate answers are custom fields at the application level in SupportFinity. We map question text and answer values to Zoho Recruit custom fields on the Job Opening or Candidate module. Skip logic and conditional branching in SupportFinity's screening flows have no Zoho Recruit equivalent and are documented in the automation inventory for the customer's admin to rebuild manually.

SupportFinity's AI-generated talent signals and ranking scores are proprietary metadata. We export raw scores and signal labels as custom numeric or text fields in Zoho Recruit (e.g., talent_signal_score, atom_ranking_position). Zoho Recruit treats these as informational custom fields; they do not drive automation or ranking in the destination. We flag this in the migration report so the customer's team does not expect AI ranking behavior post-migration.

Offer records including salary, start date, and status map to Zoho Recruit's Offer module. Compensation details, offer status (extended, accepted, declined, withdrawn), and start date transfer directly. Zoho Recruit's offer letter templates are separate from the offer record data; we do not migrate template files but document them in the migration inventory for the customer's admin to reconfigure.