Migrate from PeopleStrong to Bullhorn ATS & CRM

PeopleStrong Employee records do not map directly to a single Bullhorn entity. Active candidates with open applications migrate to Bullhorn Candidate. Historical employees with no active job order relationship migrate to Bullhorn Contact or are excluded based on the customer's scope decision during scoping. We separate the Employee export into candidate pool and contact pool using the employee's last application status and department assignment. Personal details, employment dates, and manager assignment migrate as standard fields on the target entity; full HR details without Bullhorn equivalents (probation status, compensation band, grade) are flagged as out-of-scope.

PeopleStrong Candidate records (from the Talent Acquisition module) map directly to Bullhorn Candidate. We extract resume data, stage history, interview scores, offer letter metadata, and recruiter assignments. Resume files retrieve separately via PeopleStrong's file API and attach to Bullhorn Candidate records via the Bullhorn resume upload endpoint. Candidate ID from PeopleStrong is preserved in a custom field ps_candidate_id__c for audit and reconciliation.

PeopleStrong job applications with stage, submission date, and status map to Bullhorn JobSubmission. For staffing agencies with placement records, the application converts to a Bullhorn Opportunity with the Candidate linked. We preserve stage history, submission timestamps, and rejection reasons where available.

PeopleStrong job requisitions map to Bullhorn JobOrder. Job title, description, location, employment type (full-time, contract, part-time), and salary fields map to standard Bullhorn JobOrder fields. Custom requisition fields from PeopleStrong migrate to Bullhorn Custom Fields on JobOrder or to a Custom Object if the volume requires structured storage. Active job status maps to Bullhorn JobOrder status values.

PeopleStrong departments and cost center hierarchies migrate to Bullhorn BusinessSector on JobOrder for placement categorization. Multi-office organizations can use Bullhorn Corporate entities for location-level reporting. We preserve the full department hierarchy as a string value for display and reporting.

PeopleStrong job title and grade structures migrate as Bullhorn Category values on JobOrder. We create Category records from the PeopleStrong title list and map each JobOrder to the corresponding Category during import. Grade band information without a Bullhorn equivalent is stored as a custom text field or excluded based on scope decision.

PeopleStrong system users with active Bullhorn role equivalents migrate as Bullhorn User records. We match by email address. Any PeopleStrong user without a corresponding Bullhorn license is held in a reconciliation queue; the customer's Bullhorn admin provisions the license before migration continues. Role assignments (recruiter, hiring manager, approver) map to Bullhorn User permissions and team assignments.

PeopleStrong employee documents (offer letters, contracts, ID proofs) attached to candidate records migrate as Bullhorn ContentDocument linked via ContentDocumentLink to the corresponding Candidate. Document migration runs as a secondary batch after the primary record phase to avoid API timeout errors on large file volumes. We preserve original filenames and MIME types.

Payroll records in PeopleStrong (salary components, pay periods, deductions, payslips) have no Bullhorn equivalent. Bullhorn is a recruitment ATS and CRM, not a payroll platform. We flag payroll history as out-of-scope during scoping, document the PeopleStrong payroll data structure, and recommend a separate payroll migration to a dedicated payroll platform (Rippling, Gusto, ADP, or the customer's existing payroll system) as a parallel engagement.

Clock-in/out timestamps, regularization requests, and shift assignments stored in PeopleStrong have no Bullhorn equivalent. Bullhorn's data model does not include attendance or time-tracking objects. We exclude attendance records from the migration scope and document the PeopleStrong attendance schema for the customer's HR admin to assess against a standalone time-tracking solution post-migration.

Leave accrual balances, request records, and approval history in PeopleStrong have no Bullhorn equivalent. Bullhorn does not store HR leave management data. We flag leave management as out-of-scope and document the leave type structure and balance schema from PeopleStrong so the customer's HR admin can configure leave tracking in a dedicated HR platform post-migration.

Review cycles, ratings, and goals from PeopleStrong's Performance Management module do not map to Bullhorn. Bullhorn's standard ATS data model includes placement feedback fields but not structured performance review workflows. If the customer requires performance tracking in Bullhorn, we scope this as a custom object with fields configured per Bullhorn Growth or Enterprise edition limits (10 custom objects per entity, 55 fields each). The Performance Management module must be active in the customer's PeopleStrong subscription for these records to exist.

Expense claims with line-item details, approval status, and settlement records are PeopleStrong HR data with no Bullhorn equivalent. Bullhorn does not handle expense management or employee reimbursements. We exclude these records from migration scope and document the claim structure for the customer's HR admin to assess against a dedicated expense management tool.

PeopleStrong organization-level custom fields on employee and candidate records vary by tenant and are not consistently exposed via the public API. We perform a schema discovery phase during scoping to enumerate all active custom fields and their data types, then map each to either Bullhorn standard custom fields or Bullhorn Custom Objects based on volume and complexity. Bullhorn Growth and Enterprise editions support up to 10 Custom Objects per entity with 55 fields each; Bullhorn ATS supports 2 Custom Objects per entity.