Migrate from AgileATS to Bullhorn ATS & CRM

AgileATS Candidate records map directly to Bullhorn Candidate. We map firstName, lastName, email, phone, address, status, and clearanceLevel to Bullhorn standard fields and Bullhorn custom fields respectively. Custom fields on AgileATS candidates (clearance types, partner assignments, EEO flags) map to Bullhorn custom fields on the Candidate entity, subject to Bullhorn's custom field cap per entity per edition. Candidate ownership from AgileATS maps to Bullhorn Candidate ownerId by email-matched User lookup. Attachments (resumes, certifications, background forms) export from AgileATS alongside record data and re-attach to the Bullhorn Candidate record using Bullhorn's ContentDocumentLink structure.

AgileATS Job records (title, location, clearance requirements, description, status) map to Bullhorn JobOrder. Job title maps to title, location maps to address, and any clearance requirement flags on the AgileATS job map to Bullhorn custom fields on the JobOrder. Job-to-Candidate associations (which candidates are pipeline-assigned to which jobs) map to Bullhorn JobSubmission records created during the candidate import phase, preserving the candidate-to-job relationship. We flag any jobs with status set to Closed or On Hold in AgileATS for Bullhorn status mapping review.

AgileATS uses a structured Agile Recruiting framework with configurable pipeline stage names and counts that vary by customer configuration. Bullhorn maps recruiting pipelines to Opportunity record types and Sales Processes. We map each AgileATS stage name to a Bullhorn Opportunity stage value and create new stages as needed within the Bullhorn Sales Process. Stage ordering and probability percentages transfer from AgileATS to Bullhorn StageProbability values. If the customer uses multiple AgileATS pipelines, each maps to a separate Bullhorn Record Type on Opportunity.

AgileATS Offer records carry compensation details, start date, and offer status. Bullhorn represents an accepted offer as a Placement record. We map AgileATS offer compensation to Bullhorn Placement's payRate or billRate custom fields (depending on whether the offer is candidate-facing or client-facing), map startDate to dateBegin, and preserve offer status as a Placement custom field. The offer-to-candidate relationship maps through the JobSubmission created during the candidate and job import phase.

AgileATS uses custom fields heavily for clearance types (e.g., Secret, Top Secret, SCI), partner assignments, and EEO flagging. We extract all custom field definitions during scoping, map each to a Bullhorn custom field on the appropriate entity (Candidate or JobOrder), and flag any that exceed Bullhorn's field cap per entity per edition (Front Office Growth/Enterprise: 55 fields per custom object, capped at 10 custom objects per entity). Bullhorn ATS tier allows 2 custom objects; ATS Growth allows 0. Clearance type values migrate as picklist values in the Bullhorn custom field.

AgileATS OFCCP, DoL, and EEO reports are generated exports rather than structured data objects. We migrate the underlying candidate fields (EEO flags, hire dates, job categories, pay ranges, clearance levels) to Bullhorn custom fields on the Candidate record. Compliance reports themselves do not migrate because they are report definitions, not record data. We deliver a written field inventory mapping each AgileATS compliance field to the corresponding Bullhorn custom field and specifying which Bullhorn field feeds each compliance report line item, so the customer's compliance team can validate output post-migration.

AgileATS full Recruiter seats map to Bullhorn standard User records by email match. We extract every distinct user referenced on candidate, job, and offer records, match by email against the Bullhorn destination User table, and provision any missing Users in the reconciliation queue before the production migration begins. AgileATS Partner Users are a distinct user class with limited permissions; they map to Bullhorn Client User or standard User with restricted access, and we flag any partner assignments on candidate records for the customer's Bullhorn admin to review and configure post-migration.

AgileATS Partner Users are tracked as a separate user class with distinct permissions and billing ($20/month each). Bullhorn does not have a direct partner-tier user equivalent. We preserve partner assignments as a custom flag field (e.g., isPartnerUser__c) on the candidate record and flag the candidate records where a Partner User is the assigned owner for review in Bullhorn. We also flag any active partners that may lose access granularity if remapped to a standard Bullhorn User role, so the customer's admin can configure appropriate permissions before cutover.

Security clearance level (e.g., NACI, MBI, CI, Polygraph) and clearance status (Active, Expired, Pending) are stored as structured fields on AgileATS candidate records. We preserve clearance values in Bullhorn custom fields on the Candidate entity (clearanceLevel__c, clearanceStatus__c, clearanceExpirationDate__c). We flag any candidates whose clearance status may have expired or requires renewal based on the AgileATS clearance expiration date, and we flag candidates pending reinvestigation for compliance review. Clearance type values map to Bullhorn picklist values in the custom field definition.

AgileATS recruiter notes and activity timestamps export from the structured file output and map to Bullhorn Note records linked via ContentDocumentLink to the parent Candidate record. Activity type (call, email, meeting) maps to Bullhorn Task records with TaskSubtype set appropriately. Activity ordering is preserved by setting ActivityDate to the original AgileATS timestamp. Note body migrates as plain text. Bullhorn's Notes support rich text; we convert AgileATS note formatting where present in the export.

AgileATS stores candidate attachments (resumes, certifications, security clearance forms, background check documents) in a separate file store from record data. We export attachments alongside record data, map file names to the Bullhorn Candidate's primary resume field, and re-attach supporting documents as ContentDocument records linked via ContentDocumentLink to the candidate. We flag any file types that may exceed Bullhorn's supported attachment size limits or unsupported formats before import.

AgileATS organization-level settings (org name, federal contractor identification, DCAA audit configuration) have no direct Bullhorn equivalent and do not migrate as structured records. We deliver a written inventory of all organization settings in AgileATS with recommended Bullhorn equivalents (e.g., Bullhorn Admin settings, corporate branding, user role configuration), so the customer's Bullhorn admin can configure these post-migration. This inventory is delivered alongside the field mapping document during the handoff phase.