Migrate from Lever to Crelate

Lever Contacts map to Crelate Contacts. Every Lever Contact field (name, email, phone, stage history, LinkedIn URL, custom properties) migrates directly. Crelate Contact records are created before any Job or Application records so that the Contact lookup is satisfied at import time. We preserve Lever's Contact-level tags as Crelate Contact tags, and talent pool associations carry over as a custom multi-select 'Talent Pool' field on the Contact.

This is the primary schema transformation in the Lever-to-Crelate migration. Each Lever Contact may have multiple Opportunities, each representing a distinct Job candidacy with its own stage and feedback history. In Crelate, we create a separate Job record for each Lever Opportunity (preserving the role name, department, location, and posting status) and then create a Crelate Application record linking the Contact to that Job. The Opportunity's stage becomes the Application's pipeline stage, and we preserve the full stage progression history. If the same candidate applied to the same role multiple times, we flag the duplicate Application for the customer's review before import.

Lever Jobs map directly to Crelate Jobs. The job title, department, location, employment type, and posting status migrate as-is. Lever's job board distribution URLs and posting metadata carry over as a custom field on the Crelate Job. Job stage configurations (pipeline stage names and order) migrate separately as Crelate pipeline stage configuration entries that are associated with the Job after Job creation.

Lever's configurable pipeline stages per Job require recreation in Crelate. We export the full stage configuration including stage names, order, and any conditional rules during discovery, then configure matching pipeline stages in Crelate before Job records are imported. Each Crelate pipeline stage is linked to the corresponding Job so that stage history from Lever's Opportunity records maps to the correct Crelate stage on the Application.

Lever Offer records map directly to Crelate Offer records. Compensation details, start date, offer status, and any custom offer fields migrate intact. We preserve the link between Offer, Opportunity (now mapped to Crelate Job and Application), and Contact by resolving the Application ID at migration time. Offer history for candidates with multiple Applications carries over on a per-Application basis.

Lever Users (hiring managers, recruiters, interviewers) map to Crelate User records. We export the full user roster including name, email, access role, and department, then match by email against Crelate's User table during import. Owner assignments on Lever Contacts, Opportunities, and Offers resolve to Crelate User records by this email lookup. Inactive or departed Lever users are flagged separately in the reconciliation report for the customer's admin to provision or merge.

Lever's interview scorecards cannot be created via Lever's API and are read-only. We export all scorecard records during the discovery phase and import them as structured Note entries in Crelate, with a standardized format capturing interviewer name, rating dimensions, overall score, and feedback text. Post-import, the customer's Crelate admin must verify scorecard appearance and manually recreate scorecard evaluation templates if Crelate's form builder is available on their tier. We flag this gap explicitly in the migration checklist and do not allow scorecard data to be silently dropped.

Lever interview event records carry scheduling metadata, interviewer assignment, interview type, and calendar sync status. These export as supplementary event history on the corresponding Crelate Application record. Full calendar integrations (Google Calendar, Outlook) do not migrate — interviewers must re-connect their calendar accounts to Crelate post-migration, and new interview slots are scheduled manually or through Crelate's scheduling tool. We document every interview event timestamp and interviewer assignment so that the scheduling history is preserved even without live calendar sync.

Lever stores candidate CVs and attachments as session-linked URLs pointing to Lever's file server, not as downloadable blobs. These URLs expire when Lever credentials are rotated or the account is deprovisioned. We download all candidate attachment URLs during the export window before any credential cutover. Files are re-uploaded to Crelate as Document records attached to the corresponding Contact or Application. Customers must not rotate Lever API keys until we confirm the export phase is complete; premature credential rotation causes attachment URLs to become inaccessible.

Lever's CRM layer includes talent pool tagging and nurture campaign associations — concepts that have no direct Crelate equivalent. We carry these as Contact-level tags in Crelate (one tag per Lever talent pool or nurture campaign association) and add a custom 'Talent Pool' multi-select field on the Contact record to preserve the pool classification without losing it to ad-hoc tagging. Automated nurture sequences tied to those pools do not migrate and must be rebuilt in Crelate's outreach or email tooling post-migration; we document each sequence in the automation inventory deliverable.

Lever custom fields attached to Opportunities and Contacts vary by tenant configuration. During discovery we enumerate all custom field definitions including field type, picklist values, and the object they are attached to. We build a field-level mapping matrix before import, converting Lever field types to the equivalent Crelate field types (Short Answer, Long Answer, Date, Numeric, Picklist, Multi-Select). Crelate's custom field best practices guide recommends using picklists over free-text for controlled fields to maintain searchability — we flag any opportunity to convert free-text to picklist during mapping if the source data has a consistent value set.

Lever engagement records (calls, emails, meetings, notes) associated with Contacts and Opportunities export as activity history in Crelate. Call engagements map to Crelate call activity records with duration and disposition; email engagements map to Crelate email activity records with content preserved; meeting engagements map to calendar event history linked to the Application; notes map to Crelate notes attached to the Contact or Application record. Engagement timestamps preserve ordering so the candidate's full activity timeline is intact in Crelate.