Migrate from SupportFinity to Recruit CRM & ATS

SupportFinity Jobs (title, description, department, location, status) map directly to Recruit CRM Job records. Stage pipeline configuration on the SupportFinity job maps to Recruit CRM's pipeline stage definitions. We preserve the job's open/closed status and original posting date. Growth plan's unlimited jobs means no volume cap on migration.

Candidate profiles map 1:1: name, email, phone, resume/CV, work history, education, and custom profile fields transfer directly. The SupportFinity global talent cloud enrichment (2.4B profiles) is read-only enrichment data that does not migrate as it is a SupportFinity-hosted asset, not tenant-owned data.

Application records linking a Candidate to a Job map to Recruit CRM Application records with timestamps, source channel, and current pipeline stage. Full application history including withdrawn or rejected states migrates. Stage status maps to the Recruit CRM pipeline stage ID, which we configure to match SupportFinity's stage names.

SupportFinity user accounts (email, name, role) map to Recruit CRM user records. We resolve by email match. The SupportFinity Growth plan 3-seat cap means candidate data is never constrained by seat limits, but user access may have been restricted—the migration preserves all user records for admin review in Recruit CRM.

DISC+ scores and custom AI-generated rubric results from the Atom agent transfer as custom numeric and text fields on the Candidate record. Rubric definitions themselves (question text, weightings, conditional logic) are SupportFinity-specific and do not map to Recruit CRM's assessment model; we deliver a written inventory of active assessments for the customer's admin to rebuild as Recruit CRM templates.

Interview records with scheduled time, interviewer assignment, and notes map to Recruit CRM Interview records or candidate activity entries. Sia interview recordings (video/audio binary files) require a separate file-transfer pass after structured data migration; we preserve filenames, interview linkage metadata, and timestamps during this pass.

Offer records (salary, start date, status) map to Recruit CRM offer or employment terms fields. We preserve salary details, offer status, and start date. Offer approval workflows are not migratable and are documented for admin rebuild.

Free-text notes attached to Candidates or Applications migrate as Note records linked to the candidate in Recruit CRM. Timestamps and author attribution (via user email resolution) are preserved. Notes created by different team members maintain their original author through the user mapping.

SupportFinity tenant-specific pipeline stage IDs and labels map to Recruit CRM pipeline stages. We create matching stage names and order in Recruit CRM before Applications are imported so that stage assignments resolve at insert time. Skip logic and conditional branching in stage progression is documented separately for manual rebuild.

AI-generated talent signals and ranking scores (proprietary Atom/Genie output) migrate as custom numeric fields on the Candidate record in Recruit CRM. These are informational labels in the destination; Recruit CRM's AI matching does not interpret them, but the raw scores preserve the historical ranking data for reporting and manual reference.

Job-specific screening questions and candidate answers migrate as custom fields at the application level. Question text and answer values map as text fields; conditional skip logic requires manual rebuild in Recruit CRM's form builder. We document all active screening question sets for the customer's admin.

The SupportFinity credits ledger (purchased credits, consumed credits, balance) has no equivalent in Recruit CRM's data model and is SupportFinity-specific billing metadata. We export it as a reference CSV for the customer's financial records but do not create a destination record. No destination platform replicates this object.