Migrate from JobAdder to Bullhorn ATS & CRM

JobAdder Candidate records map directly to Bullhorn Candidate. All standard fields (name, email, phone, skills, work history, education) transfer with direct type mapping. JobAdder custom fields on Candidate migrate to Bullhorn custom fields on the Candidate record; we pre-create these in Bullhorn Admin before migration begins. The Candidate record is created before any child records (Tasks, Notes, Attachments) so that parent-lookup resolution succeeds at insert time.

JobAdder Job Order records map to Bullhorn JobOrder. The Job status maps to a Bullhorn JobStatus value, and the pipeline stage maps to a Bullhorn Pipeline configuration with corresponding status values. Job description, requirements, and assigned consultant fields migrate as direct text fields. The job board posting history attached to each Job Order migrates as metadata on the Bullhorn JobOrder record; the actual posting configuration requires manual rebuild in Bullhorn's job board settings.

JobAdder Client records map to Bullhorn Corporation. Company name, address, industry, website, and business type fields migrate directly. The Client's primary contact migrates to Bullhorn Contact with the lookup to the parent Corporation established at insert time. Any Client Portal association is preserved as a text note on the Corporation record; Bullhorn's Client Portal or Client VMS must be configured separately post-migration.

JobAdder Contact records (client-side contacts distinct from Candidates) map to Bullhorn Contact with the Corporation lookup resolved by company name match. Email, phone, title, role, and owning consultant fields migrate directly. Where a Contact shares an email with a migrated Candidate, we flag the record for the customer admin to deduplicate in Bullhorn rather than silently merging, to avoid unintended data loss.

JobAdder Placement records map to Bullhorn Placement, linked to the migrated Candidate and JobOrder records via Lookups resolved at migration time. Start date, end date, employment type, and status migrate directly. Bullhorn's base ATS tier does not include a native temp billing module; we preserve JobAdder's bill rate, pay rate, markup percentage, and timesheet period fields as Bullhorn custom fields on the Placement record so the data is accessible without requiring Bullhorn Middle Office licensing.

JobAdder Opportunity records map to Bullhorn Opportunity, which represents the business development pipeline for new client work. JobAdder's Opportunity Pipeline is a distinct object managing BD activity; Bullhorn's Opportunity is also a standard object but requires Front Office Growth or Enterprise editions at the ATS tier. We confirm the customer's Bullhorn edition during scoping and flag any Opportunity records that cannot be created if the edition does not support the Opportunity object. Status, estimated value, and close date migrate directly.

JobAdder User accounts (consultants and recruiters) map to Bullhorn User records for active accounts, resolved by email match. JobAdder users who are no longer active are migrated as inactive Bullhorn placeholders to preserve assignment history on Candidate, Job, and Placement records. Bullhorn requires that the migration user has API and Bulk API permissions; we provision a dedicated migration user in Bullhorn Admin with the required object permissions before production migration begins.

Task records linked to Candidates, Jobs, or Clients in JobAdder map to Bullhorn Task with Status, Priority, and ActivityDate preserved. Completed and open task status transfers as-is. Task assignment resolves by matching the JobAdder owner ID to the corresponding Bullhorn User record via the User mapping. Tasks with no assigned owner are held in a reconciliation queue and flagged in the migration report for admin resolution before the next phase.

JobAdder Notes on Candidates, Jobs, or Clients map to Bullhorn Note records linked via ContentDocumentLink to the parent record. Note body migrates as rich text with creation and modification timestamps preserved from the JobAdder source. Bullhorn Note is the standard engagement object for recruiter annotations; we use it rather than ContentNote to preserve the simpler timeline view on the record layout without requiring additional navigation.

File attachments on JobAdder Candidate profiles (CVs, cover letters, certifications) migrate as Bullhorn Attachment blobs associated with the Candidate record. Original filenames and MIME types are preserved. We chunk large binary transfers to stay within Bullhorn API size limits and resume any interrupted transfers on retry. Attachment migration runs after the parent Candidate record has been created to satisfy the ParentId reference.

JobAdder custom fields on Candidates, Jobs, and Clients require pre-creation in Bullhorn Admin before any data import. Bullhorn editions limit the number of available custom fields and custom objects per entity: Bullhorn ATS Growth has no custom objects, Bullhorn ATS supports 2 custom objects with 55 fields each, and Front Office Growth and Enterprise support 10 with 55 fields each. We discover the full JobAdder custom field list from the customer export, design the Bullhorn custom field schema, and deploy it via Bullhorn Admin before migration begins.

JobAdder tags applied to Candidates and Jobs migrate as Bullhorn Label entries on the record. Tags stored as flat label arrays transfer directly; the semantic meaning of tags (sourcing channel, vetting status, sourcing pool classification) is preserved in the label value itself. Bullhorn does not have a tag taxonomy equivalent, so the original JobAdder tag taxonomy must be recreated as a Bullhorn label naming convention in the Bullhorn Admin label management section post-migration.

Temp placements in JobAdder carry bill rate, pay rate, markup percentage, timesheet period, and invoice reference fields that do not exist as standard Bullhorn Placement fields. Bullhorn's native temp billing is handled by the Bullhorn Middle Office module, which is a separate licensed product. We preserve these fields as Bullhorn custom fields on the Placement record so the data is accessible at the customer's current Bullhorn edition tier. If the customer subsequently licenses Bullhorn Middle Office, the same Placement record can be used with the native payroll module.

The JobAdder Client Portal stores submission history, interview feedback threads, and client comments visible only within the portal interface. This activity log is not exported via standard JobAdder data exports. We migrate the underlying Submission, Candidate, and Job Order records, but the portal-visible feedback thread must be manually captured or reconstructed by the customer. We include this as a pre-migration data-capture task in the project plan and recommend setting up Bullhorn's Client Portal or Client VMS post-migration as the replacement for this workflow.