Migrate your Lever data

Contacts are the person records at the center of Lever's model. Each Contact may have multiple linked Opportunities. We export all Contact fields including name, email, stage history, and any custom properties. Merging duplicate Contacts on import is handled via email deduplication logic.

Opportunities are Lever's core record unit — a candidacy linking a Contact to a specific Job posting with its own pipeline stage. Many destination systems split this into separate Candidate and Application objects. We preserve all Opportunity fields, stage history, and source attribution, mapping them to the destination's equivalent structure.

Jobs are the position definitions in Lever — the role, department, location, and opening count. We export Job records including posting URLs, job board distributions, and associated pipeline stage configurations. Active vs. archived status is preserved in a custom field on the destination.

Interview records carry scheduling data, interviewer assignment, and interview type. Lever's interview scheduling links to calendar integrations. We map interview slots to the destination's interview or event records, but format differences in interviewer attribution may require manual review post-import.

Interview feedback in Lever is tied to Opportunities. Scorecards are structured evaluation forms; they cannot be created via Lever's API and must be imported as structured note records or post-import manually. We flag all feedback entries for manual verification in systems like Greenhouse where scorecards are rigidly structured.

Offer records in Lever include compensation details, start date, and status. We export all offer fields and preserve the link between Offer, Opportunity, and Contact in the migration package. Offer history is carried as a chronological list on the candidate record.

User records include name, email, access role, and department. We export the full user roster for remapping Owner and interviewer assignments in the destination system. Inactive users are flagged separately from active users in the export.

Lever's CRM functionality includes candidate tagging and nurture campaign associations for talent pools. These do not map 1:1 to most ATS objects — we carry them as Contact-level tags and a custom 'Talent Pool' multi-select field in the destination.

Lever stores candidate CVs and attachments linked to Opportunities. We download all attachment URLs during the export phase before cutting over credentials. Files are re-uploaded to the destination on a per-Opportunity basis with the original filename preserved.

Custom fields attached to Opportunities and Contacts vary by tenant configuration. We enumerate all custom field definitions during the discovery phase and build a field-level mapping matrix before any data is written. Fields with no destination equivalent are flagged for customer review.

Lever's pipeline stages are configurable per Job. We export the full stage configuration including stage order, names, and any automated stage-change rules. Stages are recreated in the destination or mapped to equivalent stage names.

Interview events in Lever capture scheduling metadata including calendar invite status and cancellation records. These are exported as supplementary event history on the Opportunity. Full calendar integration recreation is not supported — scheduling must be re-established in the destination ATS.