Migrate from StaffingSoft to Bullhorn ATS & CRM

StaffingSoft candidate records (name, contact details, employment history, skills, status) map directly to Bullhorn Candidate. StaffingSoft's multi-state location fields map to Bullhorn Candidate address fields and a custom CandidateState__c field if the deployment requires region-level segmentation. Resume files export as binary from StaffingSoft's document module and re-attach to Bullhorn Candidate as file entities. Any StaffingSoft candidate status value (active, passive, placed, archived) maps to the corresponding Bullhorn Candidate status with a migration audit flag preserved in a custom field ss_original_status__c.

StaffingSoft job postings (title, requirements, qualifications, opening dates, pipeline stages) map to Bullhorn JobOrder. StaffingSoft's per-job-order stage configuration maps to Bullhorn's JobOrder stage values, with a custom field ss_original_stage__c holding the StaffingSoft stage name for reconciliation. JobOrder type (direct hire, contract, temp-to-perm) maps to Bullhorn JobOrder employmentType and a custom JobOrderType__c field. Any StaffingSoft job order with multiple assigned recruiters maps to Bullhorn JobOrder users via a JobSubmission or JobOrderUserAssociation record created at migration time.

The StaffingSoft Assignment is the core entity linking Candidate to Job Order with bill rate, pay rate, start date, and end date. Bullhorn's Placement object serves the same linking function with fields for billRate, payRate, dateBegin, and dateEnd. We map each StaffingSoft Assignment to a Bullhorn Placement, setting the CandidateID and JobOrderID references and preserving the bill-to-client and pay-to-candidate rates as Placement properties. Any assignment-level custom fields map to Bullhorn Placement custom fields, subject to the Bullhorn edition's custom object limits. Placement status (active, completed, terminated) migrates from StaffingSoft assignment status.

StaffingSoft client records contain both company information (name, address, billing preferences) and primary contact details. We split this into Bullhorn ClientCorporation (the employing organization or client company) and ClientContact (the hiring manager or client-side recruiter). StaffingSoft's client billing preferences map to Bullhorn ClientCorporation fields. Multiple StaffingSoft client contacts map to separate ClientContact records linked to the ClientCorporation.

StaffingSoft user accounts (recruiter name, email, team structure, permission roles) map to Bullhorn User records. We resolve StaffingSoft owner IDs referenced on candidate, job order, and assignment records to corresponding Bullhorn User IDs by email match. Any StaffingSoft owner without a matching Bullhorn User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds, because OwnerId references are required on most Bullhorn standard objects.

StaffingSoft pipeline stages are configurable per job order or globally. We export the stage names and ordering and configure Bullhorn JobOrder stages to match. Custom stage-specific automation (which StaffingSoft allows per-stage) does not migrate; we document the stage transition matrix as a written handoff so the customer's Bullhorn admin can rebuild any required workflow logic in Bullhorn.

StaffingSoft resume files stored in its document management module export as binary files. We re-attach each file to the corresponding Bullhorn Candidate record. File naming conventions vary across StaffingSoft deployments, so we audit the file-to-candidate linkage during discovery and create a mapping table before migration. PDF and Word resume content does not parse into Bullhorn custom fields unless the customer licenses Bullhorn's Resume Parser or Textkernel integration separately.

StaffingSoft interview feedback, scorecards, and scheduling notes are stored as activities against the candidate record. We extract the content and attach it to Bullhorn Candidate as Note records or Task records with a TaskSubtype of Meeting, depending on the StaffingSoft activity type. Rating scores migrate to a custom CandidateRating__c field if the rating scale maps cleanly; otherwise the scorecard content migrates as a Note.

StaffingSoft custom fields on candidates, job orders, and assignments require field-level mapping during scoping. Text, number, date, and dropdown field types map to Bullhorn equivalents. Bullhorn edition limits apply: ATS Growth allows no custom objects, ATS Standard allows two, and Front Office Growth and Enterprise allow ten with up to 55 fields each. We pre-create the destination schema before data import, deploying custom fields and custom objects via Bullhorn's API or admin interface into a Sandbox first for validation. Any custom field that references a StaffingSoft ID as a lookup is resolved to the corresponding Bullhorn record ID at migration time.

StaffingSoft stores cross-posting site associations (Indeed, LinkedIn, ZipRecruiter) as properties on the job order. We export the posting URLs and dates as a written document, but the active posting credentials (username, password, API key per job board) do not export from StaffingSoft and must be re-entered in Bullhorn's job board integration settings. We flag this as a manual step in the handoff document and provide a per-job-board re-entry checklist.

StaffingSoft report definitions and saved filters are not exportable as portable artifacts. We export report data as CSV where feasible before migration, but the report definition itself — including filter logic, grouping, and column ordering — must be rebuilt in Bullhorn. We deliver a written inventory of every StaffingSoft report with its data scope, filter criteria, and recommended Bullhorn Report equivalent.

StaffingSoft onboarding task checklists and document collection status transfer as candidate properties in Bullhorn. Any e-signature configuration or I-9 integration linked to onboarding does not migrate; we document these as reconfiguration tasks for the customer's Bullhorn admin to address post-migration. The onboarding task list itself migrates as Bullhorn Task records linked to the Candidate Placement.