Migrate from X0PA AI to Recruit CRM & ATS

X0PA AI job records map to Recruit CRM Job records. We extract Job Title, Description, Location, Department, Employment Type, and open/closed status from CSV exports. Recruit CRM supports multiple job statuses and customizable pipelines per job, so X0PA workflow stage names for each job are mapped individually during the CSV field-mapping phase. Active versus archived job state migrates as the Job status field. Any job with a custom stage set in X0PA RPO mode is flagged for manual pipeline reconstruction in Recruit CRM.

X0PA AI Candidate records map to Recruit CRM Candidate records, which serve as the unified contact object in Recruit CRM's ATS+CRM model. We map all standard contact fields including name, email, phone, address, current company, current title, and source. All X0PA AI-generated scoring fields (CV relevance score, predictive performance score, predictive loyalty score) are flagged as read-only reference fields in Recruit CRM with a migration_note prefix indicating they were computed in X0PA and cannot be recalculated. Resume files attached to candidate records are mapped as document attachments in Recruit CRM.

X0PA AI assessment records including the Persona behavioral assessment module map to custom fields on the Candidate record in Recruit CRM. Assessment type, completion status, score, and date migrate as discrete fields. Persona Match behavioral traits (task-oriented vs people-oriented) are stored as text or picklist fields in Recruit CRM. The raw AI interpretation of behavioral fit cannot be reconstructed outside X0PA and is labeled as X0PA reference data in the destination.

X0PA AI interview records (scheduled datetime, interviewer assignment, interview type, and automated scheduling status) map to interview sub-records within the Candidate object or to Tasks in Recruit CRM. X0PA AI Room recording and transcription data does not migrate as no documented export endpoint exists for these media files; we note this limitation explicitly in the scoping document and recommend customers request media exports directly from X0PA support before migration begins. Scheduling status and interviewer assignment transfer as structured fields.

X0PA AI Offer records including status, compensation details, start date, and candidate association map to Offer sub-records attached to the Candidate in Recruit CRM. Offer history and versioned changes are preserved as sequential Offer entries with a status and timestamp. Recruit CRM's offer management covers compensation, start date, and offer status tracking natively.

X0PA AI user accounts including role assignments (Recruiter, Hiring Manager, Admin, RPO Client) map to Recruit CRM User accounts. We resolve by email match and map role assignments to Recruit CRM's permission model (Admin, Recruiter, Hiring Manager, or Client access). Active and inactive status is preserved. Any X0PA user without a matching email in the destination is held in a reconciliation queue for the customer's admin to provision.

X0PA AI RPO tier client records including client name, billing contact, and contract status map to Recruit CRM Client records with a custom RPO tag to preserve the X0PA RPO relationship context. Client-specific workflow routing rules and stage configurations are documented in the scoping form as manual reconstruction items. Recruit CRM does not include native RPO invoice management; we flag this gap and note that billing and contract management require either Recruit CRM's billing module or a separate finance tool integration.

X0PA AI custom workflow stages per job or per RPO client are exported as structured stage names and ordering. We reconstruct pipeline stages in Recruit CRM as configurable pipeline stages on each Job. Stage routing rules and conditional logic from X0PA RPO are documented in the migration scoping form and handed to the customer as a configuration checklist for manual rebuild. Automated routing rules do not have a documented export format and cannot be migrated programmatically.

X0PA AI internal talent pool membership is exported as candidate pool labels or list membership tags. These map to Candidate tags in Recruit CRM, preserving the sourcing and retargeting context. The X0PA AI 250M+ external profile database is X0PA infrastructure-bound and does not migrate; only candidates already processed through X0PA AI as structured records are in scope.

For organizations that use X0PA AI's talent pool retargeting feature to maintain segmented candidate lists, we export the pool membership relationship as Candidate tags or list membership in Recruit CRM. The mapping uses candidate email or unique identifier as the lookup key. Any candidate with multiple pool assignments receives multiple tags in Recruit CRM.