Migrate from X0PA AI to Bullhorn ATS & CRM

X0PA job records map directly to Bullhorn JobOrder. Job Title, Description, Location (city/state/country split), Department, Employment Type (mapped to JobOrder employmentType picklist), and open/closed status migrate as standard fields. X0PA workflow stage configuration per job maps to Bullhorn JobOrder status (Open/Closed/On Hold) and a custom JobStatus stage field if the customer requires granular stage tracking beyond Bullhorn's native status. We coordinate with X0PA support to generate the CSV export covering all active and closed jobs within a defined date range.

X0PA Candidate records map to Bullhorn Candidate with all standard contact fields (name, email, phone, address, LinkedIn URL) preserved. X0PA's candidate-specific fields including candidate type (active/passive/prospective), source channel, and talent pool membership migrate to Bullhorn Candidate custom fields. The X0PA masked/prospective candidate flag maps to a custom Candidate_IsProspective__c boolean. We preserve the original X0PA candidate ID in a custom field x0pa_candidate_id__c for reconciliation.

X0PA's Persona™ behavioral assessment module stores structured assessment scores per candidate per requisition. Bullhorn does not have a native behavioral assessment object, so we provision a Custom Object on the Candidate entity (customObject1 through customObject10 depending on the customer's Bullhorn edition tier) to store Persona™ scores, completion status, assessment type, and date taken. The Front Office Growth/Enterprise tier supports up to 10 custom objects with 55 fields each; Bullhorn ATS supports 2 custom objects. We coordinate with the customer during scoping to confirm which Bullhorn edition they hold and which custom object slot to use.

X0PA's proprietary AI scores (CV relevance, predictive performance, predictive loyalty) are computed by X0PA's gradient boosting model and are platform-locked. We migrate these values as custom read-only fields on the Bullhorn Candidate record (x0pa_cv_relevance_score__c, x0pa_predictive_performance_score__c, x0pa_predictive_loyalty_score__c) with field-level security set to read-only for all roles. We clearly label these as reference-only data during scoping so customers understand they cannot be regenerated or recalculated in Bullhorn. Any hiring logic that relies on these scores requires rebuilding using Bullhorn's native filters and reporting.

Interview records from X0PA — including scheduled datetime, interviewer assignment (mapped to Bullhorn User), interview type, candidate association, and interview stage — map to Bullhorn Event records linked via EventRelation to the Candidate. Automated scheduling status migrates as a custom Event field event_scheduling_status__c. Interview notes and feedback fields migrate as Note records attached to the Event. Bullhorn Event does not natively support interview score or rating fields, so structured feedback from X0PA interview evaluations maps to a custom Event field or a custom object on Event if the customer's Bullhorn edition supports it.

X0PA Room stores interview recordings, analysis, and transcription in X0PA's own infrastructure with no documented export capability or public API endpoint. We do not attempt to migrate interview recordings as no export mechanism is evidenced. We flag X0PA Room media files as a migration gap in the scoping document and recommend the customer request their X0PA Room export directly from X0PA support before migration cutover. If the customer requires archived recordings post-migration, they must be retrieved from X0PA and stored externally.

X0PA Offer records map to Bullhorn Opportunity. Offer status, compensation details (salary, bonus, equity if stored), start date, and candidate association migrate as Opportunity fields. X0PA offer history and versioned changes (if the customer used offer versioning) migrate as a custom text area field offer_history__c holding a structured summary of prior offer versions. We create the Opportunity under the Candidate's associated JobOrder to preserve the offer-to-requisition relationship.

X0PA user accounts (Recruiter, Hiring Manager, Admin, RPO Client roles) map to Bullhorn User records by email match. Role mapping requires a mapping matrix: X0PA Recruiter maps to Bullhorn Recruiter role, X0PA Hiring Manager maps to Bullhorn Hiring Manager role, and X0PA Admin maps to Bullhorn Admin. Active/inactive status migrates. RPO Client users who are external to the organization map to Bullhorn ClientContact records under the corresponding ClientCorporation rather than User records. We resolve owners by email match; any X0PA user without a matching Bullhorn User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

X0PA RPO tier includes multi-client dashboard and client relationship tools with client name, billing contact, and contract status. These map to Bullhorn ClientCorporation (company-level) and ClientContact (billing contact, primary RPO client relationship manager) records. We apply a custom tag RPO_Client__c on ClientCorporation to distinguish RPO client records from standard Bullhorn client corporations. Client billing and invoice history migrates to a custom ClientCorporation field or a custom object if the Bullhorn edition supports it and the customer requires it.

X0PA RPO supports custom workflows per job or per client with stage configurations, client-specific routing rules, and invoice/contract management. These workflow definitions have no documented export format. We reconstruct RPO pipeline stages manually by mapping from CSV exports — specifically, X0PA job stage names and ordering map to Bullhorn JobOrder status values and a custom RPO_Stage__c field that captures the original X0PA stage name. Conditional routing rules and automated stage transitions are documented in a migration scoping form and delivered as a written workflow map for the customer's admin to rebuild in Bullhorn. Bullhorn Record Types can be used to separate RPO pipeline views from standard ATS pipeline views if the customer runs both modes.

X0PA maintains a searchable internal talent pool for sourcing and retargeting, with candidate pool membership as tags. We export pool membership and map it to Bullhorn Candidate Tags (comma-separated or multi-select custom field depending on the customer's Bullhorn edition). For organizations that use X0PA's talent pool retargeting feature heavily, we also recommend Bullhorn Candidate Lists as a destination for group-based sourcing campaigns. The 250M+ external profile database that X0PA uses for candidate sourcing is X0PA's own infrastructure and does not migrate.

X0PA stores candidate applications as the association between a Candidate and a Job with status and stage. Bullhorn models this as JobSubmission — a join record between Candidate and JobOrder with status, date submitted, and current stage. We map X0PA application status (applied, screening, shortlisted, interviewed, offered, hired, rejected) to Bullhorn JobSubmission status values. X0PA application date and last-modified date map to Bullhorn dateAdd and dateLastModified fields on JobSubmission.

X0PA tracks candidate source channels including job board postings, career site applications, resume database searches, and employee referrals. Source channel, source campaign, and UTM data migrate as custom Candidate fields (candidate_source_channel__c, candidate_source_campaign__c, candidate_source_utm__c) to preserve attribution data for reporting in Bullhorn.