Migrate from Lever to BambooHR

Lever Contact records map to BambooHR Candidate records. The Contact's name, email, phone, and address fields map directly to BambooHR's candidate fields. Any custom Contact-level properties migrate to BambooHR custom candidate fields. The Lever Contact's email address serves as the dedupe key. If a Lever Contact has multiple Opportunities, each generates a separate Application record in BambooHR tied to the same Candidate.

Each Lever Opportunity attached to a Contact maps to a separate BambooHR Application record linked to the same Candidate. The Opportunity's stage (Applied, Phone Screen, Onsite, Offer, Hired, etc.) maps to the BambooHR Application stage. If the same Contact has three historical Opportunities across different Jobs, we create three Application records in BambooHR, each with its own stage history and linked to the Candidate. This split is the central schema transformation of this migration.

Lever Job records (requisition, department, location, job board distributions, opening count) map to BambooHR Job records. The Lever Job's status (Open, Closed, Draft, Archived) carries over to BambooHR's job status. Job descriptions migrate as structured fields; any rich-text formatting that BambooHR does not support is flattened to plain text.

Lever Offer records (compensation amount, pay type, currency, start date, status) map to BambooHR employee record fields: Pay Rate, Pay Type, Hire Date, and Employment Status. The Offer must be linked to a Hired Opportunity. BambooHR requires Job Title to match an existing job title value in the system; we validate this match during the transform phase and flag any mismatches for admin resolution before import.

Lever Interview records (scheduling metadata, interviewer assignment, interview type, date/time) map to BambooHR Application interview entries. Interview history per Opportunity carries over as ordered interview records on the corresponding BambooHR Application. Calendar sync links do not migrate; interviewers reconnect their calendars to BambooHR's scheduling tools post-migration.

Lever's structured scorecard data cannot be written via Lever's API — only read access exists. We export scorecard records as structured note entries on the corresponding BambooHR Application, preserving interviewer name, rating dimensions, and comments. BambooHR does not have native structured evaluation forms; the customer must rebuild scorecard templates manually in BambooHR's forms or as an approved third-party tool post-migration.

Lever User records (name, email, access role, department) migrate for Owner and interviewer remapping in BambooHR. We match by email address. Users without a matching BambooHR account go to a reconciliation queue for admin provisioning before the production migration phase. Active and inactive status is preserved in a custom field on the BambooHR User record.

Lever's CRM layer tags (talent pool associations, nurture campaign membership) have no direct equivalent in BambooHR ATS. We carry these as a custom multi-select field 'Talent_Pool__c' on the BambooHR Candidate record and as tag entries on the candidate profile. Automated nurture sequences tied to these pools do not migrate; the customer rebuilds any candidate outreach sequences in BambooHR's email tools or a separate sales engagement tool post-migration.

Lever stores candidate attachments as session-linked URLs that expire upon credential cutover. We download all attachment files during the export phase before any credential rotation. Files are re-uploaded to BambooHR on a per-record basis as attachments to the corresponding Candidate or Application. Customers must not rotate Lever API credentials until we confirm the export phase is complete.

Lever's custom Opportunity fields vary by tenant configuration. We enumerate all custom field definitions during the discovery phase, map field types to compatible BambooHR ATS custom field types, and build a field-level mapping matrix before migration. Custom field values carry over as structured data; any field type that cannot map directly (e.g., Lever-specific structured objects) migrates as text. BambooHR field names must be pre-created by the admin before the migration phase.

Lever's pipeline stages are configurable per Job. We export the full stage configuration (stage order, names, probabilities) and map each to a corresponding BambooHR Application stage value. If BambooHR's default stage set does not match Lever's custom stages, we document the gap and recommend stage-set configuration before migration begins.