Migrate from SupportFinity to BambooHR

SupportFinity Job records map to BambooHR Job Opening objects. We map job title, description, department, location, and status fields directly. Note that BambooHR caps active job openings by plan tier: 5 on Core, 25 on Pro, 50 on Elite. If the SupportFinity instance has more open jobs than the destination plan allows, we scope the overflow to a written inventory for admin to either close archived jobs or upgrade the BambooHR plan before migration proceeds.

SupportFinity Candidates are the core record and may span the entire hiring lifecycle. We split at migration time based on the Candidate's most recent pipeline status: Candidates in an active or rejected pipeline stage become BambooHR Applicants; Candidates with an accepted offer and a hired status become BambooHR Employee records. We preserve all SupportFinity profile fields (name, email, phone, resume, work history, education, custom profile fields) as mapped Applicant or Employee fields, with the original SupportFinity Candidate ID stored in a custom field sf_candidate_id__c for cross-system audit.

SupportFinity Application records link a Candidate to a Job with timestamps, source channel, and current stage. We map these to BambooHR Applications as the join record between Applicant and Job Opening. Application history including withdrawn, rejected, and hired states migrates as the application status field. The original application submission date migrates as Created Date; the last status change date migrates as Modified Date.

SupportFinity uses configurable pipeline stages (Screening, Interview, Offer, Hired, and any custom stages). Stage names and count are tenant-specific. We map SupportFinity stage IDs and labels to BambooHR's hiring pipeline stages, preserving probability percentages where defined. Skip logic and conditional stage routing in SupportFinity requires manual review post-migration since BambooHR's pipeline model is linear rather than branching.

SupportFinity DISC+ scores and Atom-agent-generated custom assessments have no native equivalent in BambooHR. We export assessment results as structured scores and map them to custom Applicant or Employee fields (e.g., disc_d_score__c, disc_i_score__c, atom_domain_score__c). Custom rubric definitions and AI-generated assessment logic require rebuild in BambooHR or an external assessment vendor; we document the full assessment inventory as part of the migration scope for the customer's admin to address.

SupportFinity Interview records include scheduled time, interviewer assignment, and interviewer notes. Sia interview recordings are binary video/audio files that do not export via JSON API and require a separate file-transfer pass (see Gotchas). We migrate interview date, interviewer name, duration, and notes as structured fields on the corresponding BambooHR Application record. Scheduling data maps to a custom date field on the Application.

SupportFinity User accounts (Recruiter, Hiring Manager, Admin roles) map to BambooHR User records. We resolve users by email match and map the role designation. Note that SupportFinity Growth plan caps at 3 seats while BambooHR's per-employee pricing scales with headcount; we flag any user above the 3-seat cap during scoping so the customer can provision the appropriate BambooHR plan before migration.

SupportFinity Offer records include salary, start date, offer status, and any conditional terms. We map offer details to BambooHR Employee records as compensation fields (pay rate, pay frequency, start date, employment status). If the customer uses BambooHR Onboarding, the offer data feeds the New Hire Packet. Conditional offer terms and custom offer letter content are preserved as document attachments in BambooHR's file storage for the Employee record.

Free-text notes attached to Candidates or Applications in SupportFinity migrate as Notes on the corresponding BambooHR Applicant or Employee record. We preserve timestamps and author attribution (resolved via User email mapping). If the author is a SupportFinity user who will not be provisioned in BambooHR, the note is attributed to a system-admin placeholder for the customer to reassign manually.

Job-specific screening questions and candidate answers in SupportFinity are custom fields at the Application level. We map question text and answer values to custom fields on the BambooHR Application record (e.g., screening_answer_1__c, screening_answer_2__c). Skip logic and conditional branching on screening questions requires manual review post-migration since BambooHR does not have native conditional question routing in its ATS module.

SupportFinity unlimited mailboxes and candidate communication threads map to BambooHR Applicant activity. Email thread structure migrates as sequential comment entries on the Applicant record with timestamps preserved. SMS message history migrates as a custom field block if the BambooHR ATS supports it at the destination plan tier. The thread metadata (send date, recipient, direction) is preserved as structured comment fields.

AI-generated talent signals and ranking scores from SupportFinity (Revo, Genie ranking outputs) are proprietary metadata that have no native equivalent in BambooHR. We export raw scores and signal labels as custom numeric and text fields on the Applicant record (e.g., ai_talent_rank__c, ai_signal_label__c). These are informational in BambooHR and do not drive any native workflow; we flag them as requiring admin review post-migration to determine whether they remain useful or should be deprecated.