Migrate from SupportFinity to Bullhorn ATS & CRM

SupportFinity Jobs map directly to Bullhorn JobOrder. We extract job title, description, department, location, status, and salary fields and map them to Bullhorn JobOrder standard fields. Bullhorn's JobOrder includes a JobBoardList field for job board distribution settings that has no SupportFinity equivalent; we leave this blank for the customer's admin to configure post-migration. The job's current status (Open, Paused, Closed) maps to JobOrder's status field using Bullhorn's status enumeration (Open, Interview, Offer, etc.). Tenant-specific job categories from SupportFinity map to Bullhorn JobOrder's category field or a custom object if the category list exceeds the standard picklist.

SupportFinity Candidate profiles map to Bullhorn Candidate records with name, email, phone, and contact information preserved. SupportFinity custom profile fields (beyond the standard fields) map to Bullhorn custom fields on the Candidate entity, which we pre-create via Bullhorn's Admin Field Mappings before migration. SupportFinity's global talent cloud enrichment (2.4 billion profiles) is read-only enrichment data and does not transfer; we export the enrichment fields as custom text fields so the customer's Bullhorn admin can review which candidates had talent cloud matches. Resume and CV files migrate as ContentDocument records attached via ContentDocumentLink to the Candidate record.

SupportFinity Application records link a Candidate to a Job and map to Bullhorn JobSubmission. We preserve application ID, submission date, current stage, source channel, and full application history including withdrawn or rejected states. The JobSubmission record resolves the Candidate and JobOrder references at migration time. SupportFinity's application source tracking (referral, job board, direct) maps to JobSubmission's source field.

SupportFinity uses tenant-specific configurable pipeline stages (Screening, Interview, Offer, Hired, etc.) with custom stage names and counts. Bullhorn controls pipeline stage values through Record Types and Sales Processes on JobOrder. We extract every distinct stage label and probability from SupportFinity and configure a Bullhorn Sales Process with matching stage names and percentages. Each SupportFinity stage ID is stored as a custom field on JobSubmission for audit trail purposes.

SupportFinity DISC+ assessment scores and custom AI-generated assessment results from the Atom agent map to Bullhorn custom fields or a custom object on the Candidate record. We extract raw score values, percentile rankings, and AI-generated rubric data as numeric and text custom fields. Bullhorn's Front Office Growth and Enterprise editions allow up to 10 custom objects with 55 fields each; Bullhorn ATS Growth does not support custom objects and we flag this constraint during scoping so the customer can upgrade or accept that assessment data lands in a single large custom text field. The assessment rubric definition itself (the structure of the rubric, not just the scores) does not transfer and is flagged for manual rebuild if needed.

SupportFinity Interview records (scheduled time, interviewer assignment, notes) map to a combination of Bullhorn Note records and Event records for scheduling. We preserve interviewer assignment by resolving SupportFinity user IDs to Bullhorn User IDs via email match. Interview status (Scheduled, Completed, Cancelled) migrates as a custom picklist field on the Note. Sia interview recordings are binary attachments and do not migrate via the standard API; we schedule a separate media transfer pass after structured data migration completes, preserving filenames and interview linkage metadata.

SupportFinity User accounts with role assignments (Recruiter, Hiring Manager, Admin) map to Bullhorn User records. We resolve users by email address as the dedupe key. SupportFinity's Growth plan 3-seat limit means candidate records often outnumber active users; Bullhorn supports unlimited user seats on growth and enterprise tiers, allowing the full recruiting team to access the system post-migration. Any SupportFinity user without a matching Bullhorn User is held in a reconciliation queue for the customer's Bullhorn admin to provision before record import proceeds.

SupportFinity free-text notes attached to candidates or applications map to Bullhorn Note records linked via ContentDocumentLink to the parent Candidate or JobSubmission record. Timestamps and author attribution (resolved via user email mapping) are preserved as Note fields. Bullhorn Note supports 131,072 characters of body text, which accommodates all standard SupportFinity note lengths. Notes with embedded media references are flagged for manual follow-up if the referenced media file is not resolvable.

SupportFinity candidate email and SMS conversations via unlimited mailboxes map to Bullhorn Note records for thread-level preservation. Bullhorn does not natively replicate full email threading as a standalone CRM object without Bullhorn Messaging add-on; we map thread content, timestamps, and direction (inbound/outbound) as structured fields on the Note. Attachment handling requires a separate pass for binary files. Bullhorn Messaging (optional module) would provide native conversation tracking but is outside standard migration scope.

SupportFinity job-specific screening questions and candidate answers are custom fields at the application level. We map question text and answer values to Bullhorn JobSubmission custom fields, creating the custom fields during schema deployment. Skip logic and conditional branching from SupportFinity is not transferable and is flagged in the handoff documentation for manual rebuild as Bullhorn forms or questionnaire tools.

SupportFinity AI-generated talent signals and ranking scores are proprietary metadata produced by the Genie and Revo agents. We export raw scores and signal labels as custom numeric and text fields on the Bullhorn Candidate record. Bullhorn does not have a native equivalent to these AI signals; the data migrates as informational fields that the customer's Bullhorn admin can review in candidate list views or reports. The AI signal generation logic itself (the model and rules that produced the scores) does not transfer.

SupportFinity Offer records (salary, start date, status) map to Bullhorn Placement records. A single SupportFinity Offer may generate a Placement in Bullhorn; if the same candidate has multiple offers outstanding across roles, we split each into a separate Placement record. Placement in Bullhorn is the canonical employment record tied to the candidate (Candidate), the job (JobOrder), the client (ClientCorporation), and the user's billing terms. We map SupportFinity offer salary to Placement payRate and billRate, start date to startDate, and offer status to Placement's status field.

SupportFinity does not have a dedicated Company object but job and application records reference client entities. We extract these references and map them to Bullhorn ClientCorporation records, creating the corporate record if it does not exist. Client name, address, and contact details migrate as standard ClientCorporation fields. Bullhorn's ClientCorporation includes a markupPercentage field for staffing margin management that we leave blank for admin configuration.

SupportFinity's credits ledger (credits purchased, credits consumed, balance) is specific to SupportFinity's billing model and has no Bullhorn equivalent. We export the credits consumption history as a CSV file delivered alongside the migration, so the customer's finance team retains a record of historical AI feature usage. This data is for audit and reporting purposes only; it does not create Bullhorn records.