Migrate from Adapt to Bullhorn ATS & CRM

Adapt Employees map to Bullhorn Candidate records. The employee's name, email, phone, job title, department, and hire date map to Bullhorn Candidate's name, email, phone, skills, category, and dateAdded fields. We resolve the hire date to candidateDateAvailable and use a custom field adapt_original_hire_date__c to preserve the full employment start date separately from the Bullhorn record creation timestamp. Custom employee properties from Adapt (e.g., emergency contact, benefit elections) map to Bullhorn Custom Object instances attached to the Candidate.

Adapt Contact records map to Bullhorn ClientContact. The contact's name, email, phone, company association, and custom fields migrate 1:1 to Bullhorn ClientContact fields. The Adapt browser extension's enrichment metadata (email-find history, confidence scores) migrates as custom fields on the ClientContact record to preserve the data's provenance. We flag any contact records exceeding the target Bullhorn edition's contact storage limit before production migration.

Adapt Company records map to Bullhorn ClientCorporation. Company name, domain, industry, address, and phone migrate directly. The Adapt company's billing address and annual revenue properties map to Bullhorn ClientCorporation billingAddress and annualRevenue fields. Custom company properties require field-level transformation during migration; we map text, date, number, and picklist types to their Bullhorn equivalents and flag any multi-select picklist values that exceed Bullhorn's allowed value list length.

Adapt Departments map to Bullhorn Category records. Bullhorn Category objects serve as the taxonomy for classifying Candidates (by skill set), JobOrders (by department), and Placements. We preserve the Adapt department hierarchy (parent and child departments) as a Category tree structure. If Adapt uses a flat department list, we create a single-level Category hierarchy in Bullhorn.

Adapt custom employee properties map to Bullhorn Custom Object instances attached to the Candidate record. Bullhorn Growth and Enterprise editions support up to 10 Custom Objects with 55 fields each per entity (Candidate, ClientContact, ClientCorporation). Bullhorn ATS edition supports 2 Custom Objects; ATS Growth supports none. We audit the Adapt custom property count during discovery and map to the appropriate Bullhorn edition's Custom Object limits. If the customer's Adapt plan uses more custom properties than the target Bullhorn edition supports, we flag the overflow fields for admin resolution before production migration.

Adapt PTO balances (current balance and accrual history) migrate to Bullhorn as a Candidate-attached Custom Object with accrual date, accrual type, and balance amount fields. Bullhorn's standard ATS objects do not have a native PTO accrual model, so we use a Custom Object to replicate the accrual structure. If the target Bullhorn edition does not support Custom Objects, we migrate the current balance snapshot as a Note on the Candidate record with a structured text format.

Adapt salary and compensation records migrate as a Custom Object attached to the Candidate with effective date, compensation type (salary, bonus, commission), amount, and currency fields. Bullhorn does not have a native compensation history object, so the Custom Object approach preserves the full compensation timeline. For customers on Bullhorn editions without Custom Object support, we migrate the most recent compensation record as custom fields on the Candidate and flag the historical records for manual entry.

Adapt job title and position records map to Bullhorn JobOrder. Job title, description, department, employment type (full-time, contract), and pay rate migrate to Bullhorn JobOrder's title, description, categories, employmentType, and payRate fields. The Adapt job's status (open, filled, closed) maps to Bullhorn JobOrder status. We preserve the Adapt job's custom fields on the JobOrder or in a Custom Object depending on the Bullhorn edition tier.

Adapt Owners map to Bullhorn User records by email match. We extract every distinct Adapt Owner referenced on Employee, Contact, Company, and Job records and match against the Bullhorn destination's User table. Any Adapt Owner without a matching Bullhorn User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references on Bullhorn records are required for JobOrder, Candidate, and ClientCorporation.

Adapt notes and file attachments migrate to Bullhorn Note records (for text notes) and ContentDocument records (for file attachments) linked via ContentDocumentLink to the parent Candidate, ClientContact, ClientCorporation, or JobOrder. We preserve the note body as rich text and map file attachments to Bullhorn's Document records with the original filename and MIME type retained.

Adapt engagement history (call logs, email records, meeting records) migrates to Bullhorn as Task records (calls with TaskSubtype=Call), Event records (meetings with start and end times), and EmailMessage records (emails linked to an Activity Task). The activity timestamp preserves the original Adapt date so the Bullhorn Activity timeline remains in chronological order. If Adapt stores engagement metadata as custom properties rather than native activity records, we map them to Bullhorn custom fields on the Candidate or ClientContact.

Adapt user roles and permissions do not migrate directly to Bullhorn's user permission model. Bullhorn uses a role-based access control (RBAC) system with Admin, Standard, and Limited user types. We deliver a written role and permission mapping document that describes each Adapt user's current permissions and a Bullhorn role equivalent. The customer's Bullhorn admin rebuilds the permission structure post-migration based on the documented mapping.