Migrate your Bullhorn ATS & CRM data

Bullhorn's primary ATS record storing parsed resume data, work history, skills, and status. Candidates have rich custom fields and associations to JobOrders via CandidateList entities. We migrate Candidates 1:1 including all standard fields, custom properties, and the CandidateJobManager associations. Original resume files require separate file-reference queries.

JobOrder is Bullhorn's job record containing requirements, status, location, and salary information. Jobs link to Clients and track assignments through Bullhorn's pipeline stages. We map JobOrder records including all standard fields, custom properties, and job-client associations. Job board posting configurations are environment-specific and typically require manual recreation at the destination.

Client (also called ClientCorporation) is Bullhorn's CRM company record representing the staffing agency's customer. It stores company details and primary contact. We migrate all Client fields and the client-contact association. Client-specific custom fields should be reviewed for naming conflicts at the destination.

Bullhorn Contacts represent both client-side business contacts and candidate references. They share a schema but serve different roles. We separate Contacts by their entity type during migration to avoid conflating client contacts with candidate-related contacts, and preserve type metadata as a custom field at the destination.

Bullhorn Opportunities are CRM-level pipeline deals tied to Clients, representing sales pipeline stages distinct from the ATS submission flow. They map to standard CRM opportunity objects. Recruitment-specific opportunity stages (Interview, Offer, etc.) require field-level mapping to match the destination's pipeline terminology.

Placement is Bullhorn's transactional record representing a hire, linking Candidate, JobOrder, and Client, with billing information including pay and charge rates. Contract placements carry overtime rules and start/end dates critical to billing accuracy. We preserve all placement fields including contract terms and billing details, which most destination systems store as placement or hire records.

Bullhorn Tasks store to-dos with type, due date, status, and owner assignment across entities. They map cleanly to standard CRM task objects. ATS Growth edition caps API subscriptions at 50, which may require phased migration for active task lists.

Bullhorn Custom Objects extend core entities with module-like data (up to 55 fields each). ATS editions are limited to 2 searchable custom objects, while Front Office Growth/Enterprise allow 10. We migrate custom object records and field definitions, but destination systems may require schema redesign due to object-count limits and naming differences.

Bullhorn stores resume files, parsed documents, and communications as separate attachment objects. We migrate attachments via Bullhorn's file reference URLs. Bullhorn's standard CSV export does not include attachments—only the API preserves them. We explicitly include attachment migration in the scope to avoid silent data loss.

CandidateList represents a candidate's submission to a specific job, storing status within the recruitment pipeline. CandidateLists map to destination submission or application records and carry the Candidate-to-JobOrder association. We preserve the full association chain including submission status.

Bullhorn Users are system accounts representing recruiters, sales staff, and administrators with assigned roles and permissions. User records include name, email, role, and department. We migrate Users 1:1 and map ownership references across all owned entities to maintain audit trails.