HRMS migration
Field-level mapping, validation, and rollback between X0PA AI and Crelate. We move data and schema; workflows are rebuilt natively in Crelate.
X0PA AI
Source
Crelate
Destination
Compatibility
8 of 12
objects map 1:1 between X0PA AI and Crelate.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from X0PA AI to Crelate is a CSV-first migration because X0PA AI does not publish a developer-facing API with authentication, rate limits, or bulk export endpoints. All data extraction depends on manually or support-assisted CSV generation, which we coordinate with the customer's X0PA team before scoping begins. We map Jobs to Crelate Job records, Candidates to Person records, Assessments to Activities with score fields preserved where available, Interviews to Activities with interviewer and scheduling data, Offers to Offer records, and RPO client structures to Company records with a custom tag. X0PA's proprietary AI scoring model generates per-candidate per-requisition ranks that are computed by X0PA's gradient boosting engine and cannot be reconstructed in any destination platform. We flag every AI-score field during import scoping and label it as read-only reference data. X0PA Room interview recordings and transcriptions are stored in X0PA's own infrastructure with no documented export mechanism; customers requiring archived recordings must request them from X0PA support before migration cutover. Workflows, automations, and RPO-specific routing rules do not migrate as code; we deliver a written inventory of these for the customer's admin to rebuild in Crelate.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a X0PA AI object lands in Crelate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
X0PA AI
Job/Requisition
Crelate
Job
1:1X0PA AI job records map to Crelate Job. We extract Job Title, Description, Location, Department, Employment Type, and open/closed status from X0PA CSV exports. Workflow stage configuration per job is extracted separately and mapped to Crelate JobCategory values, which requires customer validation of stage names and ordering. The job's assigned Recruiter (Owner) resolves by email match to a Crelate Person record.
X0PA AI
Candidate
Crelate
Person
1:1X0PA Candidate records map to Crelate Person. All standard contact fields (name, email, phone, address, LinkedIn URL) migrate directly. AI-generated scores per candidate per requisition are flagged as read-only text fields with a 'reference-only' label prefix because they cannot be reconstructed in Crelate. Masked or prospective candidate mode is preserved via a custom flag field.
X0PA AI
Assessment (including Persona™)
Crelate
Activity
1:1X0PA Assessment records including the Persona™ behavioral module map to Crelate Activity records of type Assessment. Assessment scores, completion status, and assessment type are extracted from CSV and written to Activity custom fields. AI-generated Persona™ scores are labeled as reference-only in Crelate. Multiple assessment stages per candidate map as separate Activity records linked to the parent Person.
X0PA AI
Interview
Crelate
Activity
1:1X0PA Interview records map to Crelate Activity with type Interview. Scheduled datetime, interviewer assignment, interview type, and automated scheduling status transfer to Activity fields. Recording status is preserved as a text field noting whether X0PA Room recording was enabled. X0PA Room media files (recordings, transcriptions) are not accessible via documented export endpoint and are excluded from migration scope.
X0PA AI
Offer
Crelate
Offer
1:1X0PA Offer records map to Crelate Offer with status, compensation details, start date, and candidate association preserved. Offer history and versioned changes are captured as sequential Offer records in Crelate with the original offer date and status transition timestamps preserved. Offer amount, currency, and start date map to Crelate's standard Offer fields.
X0PA AI
User/Hiring Manager
Crelate
Person
1:1X0PA user accounts including role assignments (Recruiter, Hiring Manager, Admin, RPO Client) map to Crelate Person records with a role flag. Active/inactive status migrates. Email address is the dedupe key. Any X0PA user without a matching email in Crelate is placed in a reconciliation queue for the customer to provision before record import.
X0PA AI
RPO Client Record
Crelate
Company
many:1X0PA RPO tier multi-client data maps to Crelate Company records with a custom RPO Client tag applied to distinguish them from standard company records. Client name, billing contact, and contract status transfer to Company fields. Invoice and contract management data is not supported for migration and is documented as reference-only for the customer's admin to re-enter in Crelate's financial tracking tools.
X0PA AI
Pipeline/Workflow Stages
Crelate
JobCategory
lossyX0PA custom workflows per job or per client generate stage names and ordering that map to Crelate JobCategory values. We extract the full stage list from CSV exports and present it to the customer for confirmation of stage names, order, and any stage-specific routing rules. Automated conditional logic is documented in the migration scoping form and is not automatable in Crelate without post-import workflow configuration.
X0PA AI
Internal Talent Pool
Crelate
Tag / List
lossyX0PA internal talent pool membership maps to Crelate Tags and List membership. Pool name becomes a Crelate Tag or List name; candidate membership is written as Tag assignments or List records linked to the Person. The 250M+ external sourcing database is not exportable and is not in migration scope. Candidates retargeted from the internal pool in X0PA are represented by their tag membership in Crelate.
X0PA AI
Job Board Integration Source
Crelate
Activity
1:1X0PA job board and sourcing integrations that generated candidates are captured as Activity records in Crelate indicating the source channel. Source attribution from X0PA's job board posting history migrates as text fields on the related Job record.
X0PA AI
Custom Fields (Job, Candidate, Offer)
Crelate
Custom Fields
lossyAny X0PA custom fields beyond the standard schema are identified during CSV review and created as custom fields in Crelate before import. Field type mapping follows Crelate's supported field types (text, number, date, dropdown, checkbox, etc.). Multi-select custom fields from X0PA map to Crelate multi-select or tag-based fields depending on cardinality.
X0PA AI
Application/Submission History
Crelate
Activity (Application type)
1:1X0PA application submissions per candidate per job map to Crelate Activity records with type Application. Submission date, source channel, and application status transfer. Stage progression history within X0PA's pipeline maps to sequential Activity records representing each stage transition.
| X0PA AI | Crelate | Compatibility | |
|---|---|---|---|
| Job/Requisition | Job1:1 | Fully supported | |
| Candidate | Person1:1 | Fully supported | |
| Assessment (including Persona™) | Activity1:1 | Fully supported | |
| Interview | Activity1:1 | Fully supported | |
| Offer | Offer1:1 | Fully supported | |
| User/Hiring Manager | Person1:1 | Fully supported | |
| RPO Client Record | Companymany:1 | Fully supported | |
| Pipeline/Workflow Stages | JobCategorylossy | Mapping required | |
| Internal Talent Pool | Tag / Listlossy | Mapping required | |
| Job Board Integration Source | Activity1:1 | Fully supported | |
| Custom Fields (Job, Candidate, Offer) | Custom Fieldslossy | Mapping required | |
| Application/Submission History | Activity (Application type)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
X0PA AI gotchas
No documented public API with published auth or bulk export
AI scoring data is platform-locked and non-portable
X0PA Room interview recordings are infrastructure-bound
Enterprise pricing is opaque and requires sales negotiation
Custom RPO workflows require manual mapping to destination pipeline schema
Crelate gotchas
120 req/min API rate limit throttles bulk migrations
20 custom field per-entity cap forces data model decisions
15,000-record export ceiling on single operations
Sequences and automation workflows do not migrate
API key is a querystring parameter, not a header
Pair-specific challenges
Migration approach
CSV export coordination and discovery
We work with the customer to generate X0PA AI CSV exports for Jobs, Candidates, Assessments, Interviews, Offers, and Users. Since X0PA does not publish a self-service bulk export feature, we guide the customer through X0PA's documented data migration process or coordinate a support-assisted export request. We simultaneously audit the X0PA platform for RPO client structures, custom pipeline stages, internal talent pool lists, and any custom fields in use. This phase produces the migration scope document including record counts per object, field inventory, and explicit flagging of AI-score columns and X0PA Room recording status.
Schema mapping and staging environment setup
We map every X0PA export column to a Crelate field (standard or custom). AI-score columns are mapped to text fields with a 'reference-only' prefix label. RPO client records are mapped to Company with an RPO tag. Custom pipeline stages are mapped to JobCategory values. We create all custom fields in Crelate's staging environment before any data loads. We present the complete field mapping document to the customer for sign-off, including a list of fields that will migrate as read-only reference data and a list of fields that have no destination equivalent and will be documented for manual re-entry.
Test migration and reconciliation
We run a full test migration into Crelate's staging environment using representative data volume. The customer reconciles record counts (Candidates in, Jobs in, Activities in, Offers in), spot-checks 25-50 records against the X0PA source for field accuracy, confirms that AI-score labels are correctly prefixed, and validates that RPO client tags and talent pool Tags are applied correctly. Interview records are verified to have the correct interviewer assignments and scheduling data without media content. The customer approves the test results before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Person records first (Users, then Candidates), then Job records, then Activity records (Assessments, Interviews, Applications), then Offer records, then Tags and Lists for talent pool membership, then Company records for RPO clients with the RPO tag applied. Each phase emits a row-count reconciliation report. During cutover, X0PA writes are frozen and a final delta migration captures any records modified during the window. X0PA Room recordings are explicitly excluded with a note to the customer requesting they coordinate direct retrieval from X0PA support before cutover.
Cutover, validation, and handoff documentation
We complete the production migration and validate final record counts against the scope document. We deliver a written migration inventory that lists every object migrated, the record count, and the disposition of non-transferable data (AI scores as reference-only text, X0PA Room recordings as excluded with support request guidance). We deliver a separate Workflow and Routing Logic Inventory documenting every X0PA pipeline stage, conditional routing rule, and RPO client workflow structure that requires manual rebuild in Crelate's workflow tools. We do not rebuild these as Crelate workflows inside the migration scope.
Platform deep dives
X0PA AI
Source
Strengths
Weaknesses
Crelate
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across X0PA AI and Crelate.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
X0PA AI: Not publicly documented.
Data volume sensitivity
X0PA AI doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during X0PA AI to Crelate migration scoping. Not seeing yours? Book a call.
Walk through your X0PA AI to Crelate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave X0PA AI
Other ways to arrive at Crelate
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.