Migrate from Lever to Greenhouse

MIGRATION OVERVIEW

Why teams migrate from Lever to Greenhouse

There is no native migration path from Lever to Greenhouse. Lever is opportunity-centric — a single Contact has multiple Opportunities representing candidacies. Greenhouse separates this into distinct Candidate and Application records where Applications link Candidates to Jobs with structured scorecards.

The fundamental gap is that Greenhouse's Harvest API does not expose a POST endpoint for creating scorecards. Interview feedback from Lever cannot be migrated as native Greenhouse scorecards — only as structured notes on the activity feed.

Every migration requires handling Lever's temporary resume URLs, the On-Behalf-Of header on all Greenhouse writes, strict rate limits on both sides, and the structural translation from a relationship-first model to a process-enforcement model.

KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Lever to Greenhouse migration.

Most Critical

No Scorecard Creation API

Greenhouse exposes GET endpoints for scorecards but no POST endpoint. Lever feedback must be imported as structured notes, losing native scorecard queryability.

Multi-Opportunity Splitting

A single Lever Contact with multiple Opportunities must become one Greenhouse Candidate with multiple Applications. Incorrect handling creates duplicate profiles that cannot be bulk-merged.

Temporary Resume URLs

Lever hosts attachments via temporary download URLs. Files must be downloaded during extraction and re-uploaded to Greenhouse as base64 or staged URLs.

On-Behalf-Of Requirement

Every Greenhouse write operation requires a valid On-Behalf-Of header with an active user ID. Deactivated employees referenced as authors require workarounds.

Custom Field Type Mismatches

Lever custom fields live at the Opportunity level while Greenhouse splits across candidate, application, job, and offer levels. Application-level fields require Enterprise tier.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Lever to Greenhouse and built proven solutions for each one.

Migration Challenge ClonePartner Status

High Complexity —

Solved

Scorecards/Feedback

No API creation endpoint — must import as structured notes, losing native queryability

Solved

Attachments/Resumes

Lever URLs are temporary; must download immediately and re-upload as base64

Solved

Interview Scheduling History

Calendar events and panel configurations have no import path in Greenhouse

Solved

EEOC/Demographic Data

Lever stores at opportunity level; Greenhouse has different privacy model requiring legal review

Solved

Custom Engineering —

Handled

Confidential Postings

Lever requires special API key permission at creation time; cannot be added retroactively

Handled

Custom Fields

Application-level custom fields require Greenhouse Enterprise tier; type mismatches common

Handled

Pipeline Stage History

Stage names rarely map 1:1; requires semantic mapping via lookup tables

Handled

Clean Transfer

Source Attribution

Direct mapping with pre-creation of matching sources in Greenhouse

Clean

Fully customizable engineer-led migration

Tailor your migration from Lever to Greenhouse exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Lever to Greenhouse migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Greenhouse, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Pros and cons of different migration options

Choosing the right approach is key because migrating from Lever to Greenhouse isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited SLA
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / SLA predictability	✓ Predictable SLAs	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Lever and Greenhouse APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving conversation threads, attachments, and internal notes
Syncing custom fields, SLAs, and macros without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your Lever data and Greenhouse
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Lever or Greenhouse exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

Custom fields, ticket forms, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for CRMs, chat, or feedback tools

The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Lever to Greenhouse. Can't find what you're looking for? Talk to our team.

How does Lever's data model map to Greenhouse?

A Lever Contact maps to a Greenhouse Candidate (1:1). Each Lever Opportunity maps to one Greenhouse Application tied to a specific Job. A single Contact with multiple Opportunities becomes one Candidate with multiple Applications. Keep both source IDs as immutable external keys for reconciliation.

Can you migrate interview scorecards from Lever to Greenhouse?

Not as native scorecards. Greenhouse's Harvest API does not expose a POST endpoint for creating scorecards — only GET endpoints for reading them. The standard workaround is to import Lever feedback as structured notes on the candidate's activity feed, preserving interviewer name, overall recommendation, and per-attribute ratings.

What is the Greenhouse Harvest API rate limit?

For Harvest v1/v2, the rate limit is typically 50 requests per 10-second window. Exceeding this returns an HTTP 429. Official docs say 429 responses include Retry-After and X-RateLimit-Reset headers, but X-RateLimit-Limit and X-RateLimit-Remaining may be absent. Harvest v3 uses a fixed 30-second window. Note that v1/v2 will be deprecated on August 31, 2026.

Can Zapier or Make handle a Lever to Greenhouse migration?

They can help with low-volume delta syncs during a transition period, but they are not viable for bulk historical migration. Zapier's Greenhouse triggers use polling rather than instant webhooks, neither tool natively handles the On-Behalf-Of header required for Greenhouse writes, and they lack the state management needed for large backfills.

How long does a Lever to Greenhouse migration take?

It depends on dataset size and complexity. A small team (<500 candidates) using CSV import can finish in hours. API-based migrations of 10,000–50,000 candidates with feedback, attachments, and custom fields typically take 40–200 hours of engineering time for DIY, or 2–5 days with a managed migration service.

How long does the Lever to Greenhouse migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will my team lose access to Lever during the migration?

No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.

Will there be downtime when migrating from Lever to Greenhouse?

No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.

Do I need professional help for this migration?

While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Lever→Greenhouse migration.

Contact our team

Ready to start your
Greenhouse Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.

Migrate from Lever to Greenhouse with precision & ease

Why teams migrate from Lever to Greenhouse