Migrate from SeamlessHR to Bullhorn ATS & CRM

Active SeamlessHR Employee records map to Bullhorn Candidate records. We extract the full profile including name fields, contact information, employment dates, department, job title, and reporting manager. The employee's manager reference resolves to a Bullhorn User lookup if the manager exists in the destination as a recruiter; otherwise it is stored as a text field candidate_manager_name__c. Custom employee properties migrate to Bullhorn custom fields on Candidate that the admin pre-creates in Admin > Field Mappings before migration runs.

Exited employees in SeamlessHR use a separate export path from active employees. We pull terminated records with exit_date, final compensation, and reason for departure. Bullhorn does not have a native terminated-employee record state; exited candidates are imported as Candidate records with a custom field exit_date__c, exit_reason__c, and status set to 'Archived' or 'Inactive' to distinguish them from active candidates. Historical payroll records attached to exited profiles are exported separately and preserved as a compensation_history__c long-text custom field for the admin's reference reconstruction.

SeamlessHR exposes the org chart and hierarchy as a distinct object with parent-child reporting relationships. Bullhorn has no native org chart entity. We store the full reporting tree as three custom fields on Candidate: reporting_manager_id__c (text, sourced from SeamlessHR manager reference), department__c (text), and division__c (text). If the organization requires a visual org chart in Bullhorn, Bullhorn recommends an AppExchange org chart app; this is outside migration scope and documented as a post-migration recommendation.

SeamlessHR job requisitions with custom fields map to Bullhorn Job records. The requisition title becomes JobTitle, the job description maps to Description, and the status field maps to JobStatus (Open, Closed, On Hold). Custom fields on the SeamlessHR Requisition object require pre-creation in Bullhorn Admin before migration; any custom field not pre-created is skipped and flagged in the migration report. Workflow stage history from SeamlessHiring migrates as a custom text field stage_history__c preserving the ordered sequence of stages each requisition passed through.

SeamlessHR leave balances, entitlement policies, and request history are not natively represented in Bullhorn's ATS data model. We extract leave type balances (annual, sick, maternity) as-of the migration date and store them as custom fields on the Candidate record (leave_annual_balance__c, leave_sick_balance__c). Pending leave requests are flagged in a custom field pending_leave_request__c with the request date and type for the admin to process post-migration. Leave management is not a Bullhorn core feature; organizations requiring automated leave tracking should consider a separate leave management tool or Bullhorn's HRIS connectors.

Historical payslips and payroll runs are tied to Employee records in SeamlessHR. Bullhorn ATS/CRM has no native payroll module for historical payslip storage. We export the most recent 12 months of payroll summary (gross pay, deductions, net pay, pay period end date) as a custom object PayrollSummary in Bullhorn with a lookup to the Candidate record, and store the full compensation history as a long-text field compensation_history__c. Bullhorn Middle Office, a separate product, handles ongoing payroll processing for staffing firms and is not part of this migration scope.

SeamlessHR performance ratings, review cycles, and goal data (available on Core tier and above) are not natively supported in Bullhorn. We map review period dates, overall rating scores, and review status to Bullhorn custom fields on the Candidate record (last_review_date__c, performance_rating__c, review_status__c). If the organization maintains detailed goal or competency data, we recommend a Bullhorn custom object PerformanceReview with a lookup to Candidate, requiring the admin to pre-create the schema before migration runs.

SeamlessHR custom fields on Employee profiles require separate schema extraction before data export. We retrieve the field definition list first to identify all custom field names and types, then pull values per record. Bullhorn custom fields on Candidate must be pre-created in Admin > Field Mappings by the customer's admin before migration; the migration run skips any custom field that does not exist in Bullhorn and logs it in the pre-migration field coverage report. This is the most common source of data loss in SeamlessHR migrations and is addressed by requiring the admin to create fields during the scoping phase.

SeamlessHR custom fields on Requisitions require pre-creation in Bullhorn Job custom fields before migration. We extract the requisition-specific custom field schema during discovery and produce a pre-migration field creation checklist. Custom Component Fields in Bullhorn are reserved for integrations and are not the correct field type for general use; the admin must use standard custom fields on the Job entity. Custom field data for any field not pre-created is skipped and listed in the migration exception report.

Employee documents (contracts, ID copies, certifications) attached to SeamlessHR Employee profiles are exported as binary blobs with metadata. We map these to Bullhorn Candidate document attachments using Bullhorn's document management on the Candidate entity. Document naming follows the pattern [EmployeeID]_[DocumentType]_[Date]. CVs and resumes are parsed and mapped to Bullhorn's Candidate name and primary skill fields rather than stored as attachments alone.

SeamlessHR recruitment workflow stages are exported as an ordered sequence with stage names, order positions, and which stages each applicant passed through. Bullhorn's candidate pipeline uses a status-based model rather than ordered stages with gating. We store the full stage history as a custom text field candidate_stage_history__c on the Candidate record in JSON format (stage_name, entered_date, exited_date) and document the stage mapping for the admin to configure Bullhorn pipeline stages post-migration. Candidate record status (New, Active, Placed,Archived) is set based on the most recent SeamlessHR application status.

Applicant records from SeamlessHR's recruitment module map to Bullhorn Candidate records. Each applicant's name, email, phone, skills, work history, education, and source channel transfer directly. The SeamlessHR source channel (where_applicant_found) maps to Bullhorn's source field on Candidate. Assessment scores and interview ratings are stored as custom fields on the Candidate record. Active applications linked to open requisitions are mapped to the corresponding Bullhorn Job record at migration time.

Approval workflows in SeamlessHR define the routing chains for leave requests, requisition approvals, and expense approvals. Bullhorn's workflow model is built around candidate pipeline automations and task assignment rather than HR approval routing. We do not migrate workflow configurations as code. We deliver a written inventory of every configured SeamlessHR approval chain (workflow name, approver chain, conditions, escalation rules) for the customer's admin to recreate in Bullhorn or document for internal process manual.

SeamlessHR Employee records that are users (not just employees) are matched to Bullhorn User records by email address. Active SeamlessHR users without a corresponding Bullhorn User are held in a reconciliation queue; the customer provisions the missing Bullhorn User accounts before the User-phase migration begins. Inactive SeamlessHR users are imported as Bullhorn Users with IsActive=false for historical record ownership integrity.