Migrate from Paradox to Recruit CRM & ATS

Paradox Candidates map directly to Recruit CRM Candidates. The Paradox candidate profile includes contact details, application status, screening responses, and Olivia interaction history. We map standard fields (name, email, phone, location) to Recruit CRM's Candidate fields, and preserve the original Paradox record ID in a custom field paradox_original_id__c for reconciliation. GDPR-sensitive records with right-to-erasure or withdrawal-of-consent flags are held in a separate queue during migration and require explicit customer authorization before inclusion.

Paradox Jobs map to Recruit CRM Jobs. Each Job carries pipeline stages, hiring-team assignments, and active or closed status. We map job title, location, department, and job status directly, and reassign the hiring team by resolving Paradox owner email addresses to Recruit CRM user accounts. Multi-location or franchise job structures may require flattening if Paradox uses location as a separate dimension rather than a job field.

Paradox Events (scheduled interviews, assessments, time-bound hiring activities) map to Recruit CRM Interview or Event records. We preserve date, type, participant assignments, and outcome status. Availability windows and calendar-linked scheduling links migrate as structured data, though live calendar integrations are not replicated; these are re-established post-migration in Recruit CRM's calendar settings.

Paradox's Olivia conversational Q&A logs do not map to a standard structured object in Recruit CRM. We export these as structured records and map them to Recruit CRM's Candidate Notes (for human-readable screening history) and custom fields (for structured Yes/No or short-answer responses). During scoping, we capture the customer's specific Olivia screening questions and map each to a corresponding Recruit CRM field or note template.

Paradox schedule records capturing candidate and hiring manager availability windows map to Recruit CRM's Interview Availability model. We preserve the availability window structure, but live calendar integrations (Google Calendar, Outlook) are not migrated as active integrations; these are reconnected post-migration through Recruit CRM's native integrations.

Candidate attachments including resumes, cover letters, and portfolio files are exported from Paradox's document layer and re-uploaded to Recruit CRM as Candidate Documents. We preserve the original file name, MIME type, and binary content. File ordering or folder structure in Paradox may not map directly to Recruit CRM's document organization; we attach all files to the corresponding candidate record and document the original structure in the migration notes.

Paradox Offer records containing compensation details, status, and approval workflow data migrate as Placement records or Offer records in Recruit CRM depending on the destination tier. Pro tier supports basic Placement records; Business and Enterprise tiers support extended Offer tracking with custom fields. Offer approval routing logic from Paradox does not translate to Recruit CRM's workflow model and is documented in the migration inventory for admin rebuild.

Workers created after a successful hire in Paradox's HRIS layer migrate as Employee records in Recruit CRM if the HRIS integration is active, or as Contact records in the CRM layer otherwise. Department, job title, location, and employment status map to Recruit CRM's Contact or Employee fields. Effective-date accounting (start date, termination date) migrates directly.

Paradox Groups representing organizational units (departments, locations, cost centers) map to Recruit CRM Teams or Department structures. Nested group depth may require flattening if Recruit CRM's hierarchy model differs from Paradox's; we document the original group structure in the migration notes and recommend a target structure during scoping.

Custom fields on Candidates and Jobs are unique to each Paradox customer's configuration and are not part of a standard export. We conduct a pre-migration discovery phase to capture the exact custom field schema, field types, and any conditional logic applied to screening workflows. Each discovered custom field is then created in Recruit CRM (as standard or custom fields depending on type) before candidate migration begins, and a field-level mapping document is produced for the customer's review.