Migrate from Lever to Zoho Recruit

Lever Contacts migrate as Zoho Recruit Candidates. The Contact's name, email, phone, source, stage history, and any custom fields map directly. We preserve the original Lever contact ID in a custom field lever_original_id__c for reconciliation. If a Lever Contact has multiple Opportunities, we create one Candidate per Contact and link it to multiple Job Openings, carrying each Opportunity's stage as a separate association note on the Candidate.

Lever Opportunities are the core migration transformation. Each Opportunity links a Contact to a specific Job and carries its own pipeline stage, interview history, and feedback. We split each Opportunity into a Zoho Recruit Job Opening (the position definition: title, department, location, status) and an association record linking the Candidate to that Job Opening. The Opportunity's stage maps to a Zoho Recruit Interview stage or custom picklist value. Candidates who applied to multiple Lever Jobs produce multiple Job Opening associations.

Lever Job records (role, department, location, job board distributions, and opening count) map to Zoho Recruit Job Openings. The lever_job_posting_url and any job board distribution history migrate as notes or custom fields on the Job Opening. Pipeline stage configurations from Lever migrate as custom stage picklist values in Zoho Recruit's Hiring Pipeline configuration.

Lever interview records map to Zoho Recruit Interview records linked to the Candidate and Job Opening pair. The interviewer assignment, interview type, scheduling timestamp, and status (completed, cancelled, rescheduled) transfer directly. Lever's calendar sync metadata does not migrate; interviewers must reconnect their calendar to Zoho Recruit's scheduling tool post-migration.

Lever structured scorecards cannot be created via Lever's API and therefore cannot be programmatically reproduced in Zoho Recruit's evaluation form structure. We migrate scorecard responses as structured Notes on the Candidate record, tagging them with a [Scorecard] prefix and preserving the rating dimension, score, and evaluator name. Post-migration, the customer recreates scorecard templates in Zoho Recruit's Interview Feedback form builder if Enterprise tier is licensed.

Lever Offer records (compensation details, start date, offer status) map directly to Zoho Recruit Offer records linked to the Candidate-Job Opening pair. Offer history and status transitions migrate as a timeline of Notes on the Offer record. If the candidate was moved through offer stages in Lever, those statuses map to Zoho Recruit offer status values.

Lever User records (name, email, role, department) migrate to Zoho Recruit Users. We resolve by email match against the destination User table. Inactive Lever users are flagged in a reconciliation queue for the admin to provision in Zoho Recruit before record import proceeds. Owner and interviewer assignments on Opportunities, Interviews, and Feedback records resolve through this User mapping.

Lever candidate attachments are stored as session-linked URLs that expire when the Lever account is deprovisioned. We download all attachment URLs during the export window before credential cutover and re-upload files to Zoho Recruit's Document Library on a per-candidate basis. The CSV attachment manifest references the uploaded files using Zoho Recruit's import folder structure (Data folder with CSV, Attachments folder with source files). This step cannot be skipped or deferred.

Lever's tenant-specific custom fields on Opportunities and Contacts are enumerated during discovery and mapped to Zoho Recruit custom fields of equivalent type. Standard picklists, text fields, number fields, and date fields transfer directly. Multi-select picklists map to Zoho Recruit multi-select picklists. Zoho Recruit Standard edition allows 50 custom fields per module; Enterprise allows 300 per module. If the customer's Lever tenant exceeds Zoho Recruit's field limits per edition, we prioritize the most operationally critical fields and document the remainder for post-migration manual entry.

Lever's configurable pipeline stages per Job (stage name, order, automated rules) migrate to Zoho Recruit's Hiring Pipeline stage configuration. Stage order and names map directly. Any Lever stage-change automation rules cannot migrate and are documented in the automation inventory delivered at cutover for the admin to rebuild in Zoho Recruit Workflow Rules.

Lever's CRM layer includes candidate tagging and nurture campaign associations for talent pool management. Zoho Recruit has no native Nurture Campaign equivalent. We carry Lever talent pool memberships as Candidate tags and a custom picklist field talent_pool__c with the original pool name. Nurture sequences tied to those pools do not migrate and must be rebuilt in Zoho Recruit's Workflow Rules or external outreach tooling if the customer uses a separate engagement platform.

Lever's interview event records capture scheduling metadata, cancellation flags, and calendar sync status that do not have direct Zoho Recruit equivalents. These are exported as supplementary notes on the Interview record. Calendar integrations (Google Calendar, Outlook) must be reconnected manually by each interviewer in Zoho Recruit post-migration. New interview slots are scheduled through Zoho Recruit's Interview module or the customer's preferred scheduling tool.

Lever engagement records (call logs, email threads, meeting summaries, task entries) associated with Opportunities and Contacts migrate to Zoho Recruit's Calls, Emails, Events, and Tasks modules linked to the Candidate record. Engagement metadata (disposition on calls, email open/click status in Lever) is preserved as note content or custom fields where Zoho Recruit supports the field type. Task assignments resolve via the User mapping to assign OwnerId in Zoho Recruit.