Migrate from Lever to Recruit CRM & ATS

Lever Contact records map to Recruit CRM Candidate. The Contact's name, email, phone, location, and source attribution migrate directly. We also carry over all Lever talent pool tags and nurture campaign associations as Candidate-level tags and a custom multi-select field for talent pool classification. Custom fields attached to the Contact migrate to matching Recruit CRM Candidate custom fields identified during discovery.

This is the core structural translation for the Lever-to-Recruit CRM migration. Lever's Opportunity model links a Contact to a specific Job with its own pipeline stage, feedback, and interview history. A single Lever Contact may carry multiple Opportunities representing different candidacies. We export all Opportunity records per Contact and map each one to a separate Job Application in Recruit CRM, preserving the stage, assigned recruiter, and application date. Opportunity-level custom fields migrate to Job Application custom fields. Any Opportunity notes and engagement history attach to the corresponding Job Application record.

Lever Job records (position definitions with title, department, location, and opening count) map directly to Recruit CRM Job records. Job posting URLs, board distributions, and the opening count migrate as Job-level fields. We validate that the job title format in Recruit CRM's job creation form matches the migrated data before inserting, flagging any title normalization needed for consistency.

Lever Offer records with compensation details, start date, offer status, and conditional terms migrate directly to Recruit CRM Offers. The Offer record retains its link to the parent Job Application and Candidate in the migration package. Historical offer outcomes (accepted, declined, withdrawn) migrate as status values to maintain reporting continuity on offer-to-placement conversion.

Lever User records with name, email, access role, and department map to Recruit CRM User accounts. We resolve the owner assignment on each migrated Opportunity by matching Lever user email to the corresponding Recruit CRM user created during destination setup. Any Lever user without a matching Recruit CRM account enters a reconciliation queue for the customer to provision before record import resumes.

Lever interview scorecards are structured evaluation forms attached to Opportunities. Lever's API provides read access to scorecard data but does not support programmatic creation. We export all scorecard records as structured note entries on the corresponding Recruit CRM Job Application, using a standardized label format that identifies the interview round, interviewer, evaluation date, and rating values. Scorecard templates do not migrate; we flag this explicitly in the post-migration checklist and recommend rebuilding them in Recruit CRM's candidate evaluation forms post-import.

Lever interview scheduling records with interviewer assignment, interview type, and calendar sync metadata migrate to Recruit CRM Interview records linked to the corresponding Job Application. The interview date, duration, and interviewer assignment transfer directly. Because Recruit CRM's calendar sync does not propagate deleted events to Google Calendar (a documented limitation), any canceled interview records from Lever are imported as note entries on the Job Application with cancellation metadata rather than as active calendar events.

Lever's CRM layer includes Nurture Campaigns and talent pool associations as first-class tagging concepts. Recruit CRM does not have a native nurture campaign equivalent. We carry these associations as Candidate-level tags and a custom multi-select field 'Talent Pool' with values matching the Lever talent pool names. Any automated nurture sequences and cadence rules built in Lever cannot migrate and must be documented separately for the customer to rebuild in Recruit CRM outreach tools or third-party engagement platforms.

Lever stores candidate attachment URLs as session-linked references that expire when customer credentials are rotated or deprovisioned. We download all candidate files (CVs, resumes, portfolio documents) during the export window before any credential cutover. Files are re-uploaded to Recruit CRM and linked to the corresponding Candidate or Job Application record at import time. Customers must not rotate Lever API keys until we confirm the export phase is fully complete.

Lever custom fields attached to Contacts and Opportunities vary by tenant configuration. We enumerate all custom field definitions during discovery, match them to Recruit CRM field types (text, number, date, picklist, multi-select, checkbox, url, phone, email), and pre-create missing fields in Recruit CRM before any data import begins. Fields with no direct Recruit CRM type are converted to text and noted as requiring post-migration review. Opportunity-level custom fields are remapped to Job Application custom fields during the N:1 merge of multiple Opportunities per Contact.

Lever's pipeline stages are configurable per Job with defined stage names, order, and automated stage-change rules. We export the full stage configuration and recreate it in Recruit CRM's pipeline builder, preserving stage order, names, and any automated stage conditions as documented stage rules in Recruit CRM's pipeline configuration. Stage-level probability percentages migrate as informational fields for reporting continuity.

Lever interview event records capture scheduling metadata, calendar invite status, and cancellation flags. These are exported as supplementary event history note entries on the corresponding Job Application. Full calendar reconnection — linking Recruit CRM to each interviewer's Google Calendar — must be completed manually post-migration, and new interview slots must be scheduled via Recruit CRM's own scheduling tool or through direct calendar coordination.