Migrate from Apploi to Bullhorn ATS & CRM

Apploi Job records (title, description, location, department, employment type, job-board posting associations) map directly to Bullhorn JobOrder. The Apploi job status (Active, Paused, Closed) maps to Bullhorn JobOrder status. Apploi's multi-job-board posting configuration is account-level setting data, not job-record data, and does not migrate; we document the posting configuration for the customer's Bullhorn admin to re-enter in Bullhorn's job-distribution settings.

Apploi Candidate records map to Bullhorn Candidate. We preserve firstName, lastName, email, phone, address, employmentHistory, and education. Apploi's healthcare credential custom fields (CNA, RN, LPN license numbers and expiration dates) are extracted during the data-pull phase with their original field names and formats, then mapped to Bullhorn custom fields on the Candidate record. We flag each credential field for manual validation against the original license documentation because Apploi's custom-field formats vary by customer configuration and may contain mis-typed or expired values.

Apploi Application records link a Candidate to a Job and capture status transitions (Applied, Screening, Interview, Offer, Hired, Rejected) with timestamps. Bullhorn does not have a native Application object; candidate-job associations are tracked via the JobOrder's candidate list and the Candidate's job submission history. We migrate the Application status history as a series of Task records on the Candidate with dates and status labels, preserving the pipeline timeline for audit and reporting purposes.

Apploi Offer records (compensation details, start date, offer status) map to Bullhorn Opportunity records. The Apploi Offer's linked Job maps to Bullhorn JobOrder; the Apploi Offer's linked Candidate maps to Bullhorn Candidate. Compensation fields (salary, bonus, equity) migrate to Opportunity fields; if the Apploi configuration uses non-standard compensation fields, we map them to custom Opportunity fields that we create during the Bullhorn schema-setup phase.

Apploi onboarding task records track pre-hire compliance items (I-9, background check, credential verification, new-hire paperwork) linked to a hired Candidate. Bullhorn has Bullhorn Onboarding (formerly Able) as a separate module for this purpose, but it is not part of the standard ATS migration scope. We migrate onboarding task records as Bullhorn custom object instances or as Note records on the Candidate, including task name, due date, completion status, and associated compliance document reference.

Apploi Employee records (created after hire) include hire date, job title, department, and employment status. Bullhorn captures hired employees as Placement records, which link a Candidate (as the placed individual) to a JobOrder (as the job filled) and include start date, end date, pay rate, and placement status. We migrate Apploi Employee data into Bullhorn Placement records, creating the Placement after both the Candidate and JobOrder have been imported.

Apploi stores certifications and license numbers as custom fields on Candidate or Employee records with no standardized schema. We extract every distinct credential field name during scoping, map each to a Bullhorn custom field (text for license number, date for expiration, picklist for credential type), and create the custom fields via Bullhorn Field Mappings during the schema-setup phase. The mapping document flags each credential for manual post-migration validation against the original license documentation to catch expired or mis-typed entries that Apploi's custom-field format does not enforce.

Apploi interview evaluations and scorecards are stored as attachments or notes within the Application record. We export these as files or structured notes during the Apploi data pull, then import them into Bullhorn as Note records or ContentDocument attachments linked to the Candidate. The evaluation date, interviewer name, and rating summary migrate as metadata fields on the Note.

Apploi's shift scheduling module retains only active and recently completed schedules; historical shift data is purged on a rolling basis and is not available for export. Bullhorn Onboarding (formerly Able) handles scheduling separately and does not import Apploi shift data. We scope only current and upcoming schedules as Note records on the Employee (mapped to Placement) if the customer requests it, but we warn that historical schedule data will not transfer. The customer's Bullhorn admin rebuilds the schedule template in Bullhorn Onboarding post-migration.

Apploi's multi-job-board posting configuration (Indeed, ZipRecruiter, LinkedIn) is stored as account-level settings rather than as candidate or job data. We do not migrate job-board credentials, posting history, or distribution settings. We deliver a written inventory of the Apploi job-board integrations in use so the customer's Bullhorn admin can configure the equivalent integrations in Bullhorn's job-distribution settings.

Apploi records are assigned to Apploi users (recruiters, hiring managers). Bullhorn's ATS stores owner assignment as OwnerId on Candidate, JobOrder, and Opportunity referencing the Bullhorn User table. We match Apploi owner email addresses to Bullhorn User records during migration. Owners without a matching Bullhorn User go to a reconciliation queue for the customer's Bullhorn admin to provision before the relevant record phase runs.

If the Apploi instance contains customer-specific custom objects (beyond standard credential fields), we map them to Bullhorn CustomObject entities. Bullhorn custom objects must be initially created via a Bullhorn Support ticket before the REST API can access them; we coordinate this during the schema-design phase. Each Apploi custom object maps to a Bullhorn custom object with equivalent field types, and lookup relationships to standard Bullhorn entities (Candidate, JobOrder) are preserved via Bullhorn's custom object foreign-key references.