Migrate from Paradox to Crelate

Paradox Candidate records map to Crelate Contact. We preserve contact details, application status, source channel, and the Paradox candidate_id for audit traceability. If Paradox Candidates include a company association, we resolve it against a Crelate Company lookup during import. Any GDPR withdrawal-of-consent flags on Paradox records are verified and excluded per the consent audit trail before import.

Paradox custom fields on Candidates vary per customer configuration and require discovery scoping before migration. We capture the full custom field schema during discovery, map field types (text, numeric, picklist, date) to equivalent Crelate Contact custom field types, and configure the destination fields before any contact import begins. Conditional logic applied to screening workflows does not transfer as automation; we document it for the customer's admin to rebuild in Crelate.

Paradox Job records map to Crelate Job records. We preserve job title, description, location, employment type, status (active or closed), and hiring team assignments. Job-stage pipelines from Paradox map to Crelate pipeline stages, with stage probability values migrated to Crelate stage configuration. Multi-location jobs may require split into multiple Crelate Job records if the destination configuration separates by location.

Paradox custom fields on Jobs are unique per customer configuration. We conduct discovery to capture the exact field schema, types, and any conditional visibility logic applied to job posting workflows. Custom fields are pre-created in Crelate before Job import, with field ordering and layout assignments matching the source configuration where possible.

Paradox Event records (scheduled interviews, assessments, other time-bound hiring activities) map to Crelate Activity records linked to the parent Contact. We preserve event date, type, participant assignments, location, and outcome status. Event records without a resolvable Contact parent are held in a reconciliation queue until the parent lookup is satisfied.

Olivia screening conversation logs export from Paradox as structured Q&A records. Crelate has no direct equivalent to a screening response object, so we transform these into Crelate Notes attached to the Contact record with a category tag indicating the origin (e.g., 'Olivia Screening'). The note body preserves the full question-and-answer transcript. We flag any conditional branching logic for the customer's admin to document separately since Crelate's native workflow builder does not import Paradox's screening tree structure.

Schedule records capturing interview availability and calendar integrations migrate as Crelate Activities with date, time window, and participant assignments. Live calendar synchronization links (Zoom, Google Calendar, Outlook) do not transfer as active integrations; we document the calendar tools in use for the customer's admin to reconnect post-migration. Availability windows and scheduling preferences migrate as structured note text.

Candidate attachments including resumes, cover letters, and portfolio files export from Paradox as binary files and re-upload to Crelate as Contact attachments, preserving original filenames and file types. We validate file integrity using MD5 checksums before and after transfer. Attachments exceeding Crelate's size limits are flagged for the customer's admin to store externally with a link in the Contact record.

Assessment results from Paradox migrate to Crelate Assessment records, including score, status, linked candidate, and assessment type. If the assessment content lives in a third-party assessment tool (e.g., Pymetrics, Harver, HireVue), we flag it for separate export handling and note that the assessment content itself does not migrate as a Crelate-native object. The assessment result and metadata transfer as a linked record on the Contact.

Paradox Offer records containing compensation details, status, and approval workflow data map to Crelate Opportunity records. We migrate offer compensation, start date, status history, and the related Contact and Job lookups. Approval routing logic from Paradox does not transfer as executable rules; we document the approval chain in the written handoff inventory for the customer's admin to configure in Crelate's workflow builder.

Post-hire Employee records from Paradox's HRIS layer migrate to Crelate Employee records, including department, job title, location, employment status, and start date. Effective-date fields require careful handling; we migrate the current snapshot and flag any future-dated employment changes for manual verification post-migration.

Paradox Groups representing organizational units (departments, locations, cost centers) map to Crelate Company records used as organizational entities. Nested group hierarchies with deep branching may require flattening into a single Crelate Company record with department as a custom field, since Crelate does not natively support multi-level organizational hierarchies without custom configuration.