Migrate from Greenhouse to Lever with precision & ease

A seamless, customizable migration solution for moving your Greenhouse data with perfect fidelity and minimal disruption.

Book free consultation
Greenhouse
Lever
MIGRATION OVERVIEW

Why teams migrate from Greenhouse to Lever

There is no native migration path from Greenhouse to Lever. Greenhouse is application-centric — Candidates link to Applications which link to Jobs with structured Scorecards. Lever is opportunity-centric — a single Contact spawns multiple Opportunities through fluid pipelines.
The fundamental gap is data model architecture: Greenhouse's rigid Candidate → Application → Job → Scorecard chain must be translated into Lever's Contact → Opportunity → Posting model, with scorecards serialized into feedback forms or notes.
Every migration requires handling expiring attachment URLs, Lever's strict 10 req/sec rate limit (2 req/sec for POSTs), and the structural loss of scorecard attribute-level ratings.
KEY CHALLENGES

What makes this migration complex

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

Most Critical

Scorecard Structure Loss

Greenhouse scorecards have typed attributes with categorical ratings. Lever feedback forms use a different template-driven schema that cannot replicate per-attribute ratings 1:1.

Relationship Chain Integrity

The Candidate → Application → Scorecard chain must become Contact → Opportunity → Feedback without orphaning records or breaking historical context.

Attachment URL Expiration

Greenhouse serves resume files via signed temporary S3 URLs. If your ETL doesn't download and re-upload in the same run, files are lost permanently.

Rate Limit Management

Lever enforces 10 req/sec steady-state and 2 req/sec for application POSTs. Enterprise imports of 50K+ candidates require hours of carefully throttled throughput.

Timestamp Conversion

Greenhouse uses ISO-8601 timestamps while Lever uses Unix epoch milliseconds. Every date field needs explicit conversion during the transform phase.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Greenhouse to Lever, ensuring perfect continuity for your customer support operations.

Greenhouse
Lever
Candidates
Contacts
Applications
Opportunities
Jobs
Requisitions
Job Posts
Postings
Offers
Offers
Scheduled Interviews
Interviews
Tags
Tags
Attachments
Files
Activity Feed
Notes
Scorecards
Notes
Departments
Not Available
Offices
Not Available

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

Migration Challenge ClonePartner Status
High Complexity —
Solved
Scorecards/Feedback
Per-attribute ratings lost; must map to Lever feedback templates or serialize as notes
Solved
Attachments (Resumes)
Greenhouse S3 URLs expire — must download during extraction and re-upload to Lever
Solved
Interview Scheduling History
Calendar events and panel configurations have no import path in Lever's API
Solved
EEOC/Demographic Data
Stored at application level in Greenhouse; Lever's approach differs and requires legal review
Solved
Custom Engineering —
Handled
Confidential Postings
Lever API cannot create confidential postings — must be recreated manually
Handled
Custom Fields
Greenhouse supports 12+ types; Lever equivalents require type-by-type transformation
Handled
Pipeline Stage History
Lever stages are customer-defined and rarely match Greenhouse stage names 1:1
Handled
Clean Transfer
Source Attribution
Direct mapping with pre-creation of missing sources in Lever
Clean
Tags
Direct mapping; bulk-create in Lever before import
Clean
Notes/Activity Feed
Greenhouse notes map cleanly to Lever notes on opportunities
Clean
4 high-complexity solved
3 custom-engineered
3 clean transfers
CUSTOM MIGRATION

Fully customizable engineer-led migration

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

Migration Filters

Job Status Filter

Filter by open, closed, drafted, or archived positions

Candidate Stage

Select candidates based on pipeline stages or disposition

Hiring Team/Owner

Migrate records assigned to specific recruiters or managers

Time Range

Migrate candidates or jobs from a specific time period

Data Types

Candidates & Profiles

Resumes, contact details, and full candidate history

Jobs & Requisitions

Job openings, descriptions, and hiring team assignments

Interviews & Feedback

Interviewer scorecards, ratings, and internal notes

Offers & Applications

Application metadata, offer letters, and contract files

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 Greenhouse to Lever 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

1

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.

2

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.

3

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.

4

Full Migration

2 days · ClonePartner

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

5

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.

Timeline is an estimate. Actual duration depends on API rate limits, data complexity, and your team's availability.

Get an exact timeline

Complete Technical Guide

Greenhouse to Lever Migration: The CTO's Technical Guide

Greenhouse-to-Lever migration requires translating an application-centric schema into an opportunity-centric CRM — scorecards, attachments, and rate limits are where DIY attempts break.

23 min read

Read the guide

Pros and cons of different migration options

Choosing the right approach is key because migrating from Greenhouse to Lever 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:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. 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 Greenhouse and Lever 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:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. 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:

  1. 100% record-count parity between your Greenhouse data and Lever
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. 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 Greenhouse or Lever 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:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. 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 Greenhouse to Lever. Can't find what you're looking for? Talk to our team.

How long does a Greenhouse to Lever migration take?
Lever's own documentation estimates 8–12 weeks for custom integrations. A managed migration service like ClonePartner typically completes the full data transfer in days, though total project time including mapping decisions and validation is usually 1–3 weeks.
Can Greenhouse scorecards be migrated to Lever?
Yes, but with compromises. Greenhouse scorecards are structured objects with typed attributes and ratings. Lever uses feedback forms with a different, template-driven schema. You can map scorecards to Lever feedback (requires pre-creating templates for each unique scorecard type) or serialize them as detailed notes. Either way, the exact attribute-level rating taxonomy won't transfer 1:1 without custom transformation work.
What are the Lever API rate limits for data migration?
Lever enforces a steady-state limit of 10 requests per second per API key, with bursts up to 20 req/sec. Application POST requests are capped at 2 req/sec. These limits are not guaranteed and may change. Use exponential backoff with jitter and a shared rate limiter (like Redis) for concurrent workers.
Will a CSV export from Greenhouse work for migrating to Lever?
Only for small, simple migrations under roughly 5,000 candidates. CSV exports flatten relational data — you lose the Candidate → Application → Scorecard relationship chain, structured interview attribute ratings, and attachments. For anything beyond basic active-only candidate records, API-based migration is the only viable path.
Is the Greenhouse Harvest API being deprecated?
Harvest API v1 and v2 will be deprecated and unavailable after August 31, 2026. All new integrations should use Harvest v3, which uses OAuth 2.0 instead of Basic Auth and cursor-based pagination instead of page/per_page parameters.
How long does the Greenhouse to Lever 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 Greenhouse 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 Greenhouse to Lever?
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 Greenhouse→Lever migration.

Contact our team

Ready to start your
Lever 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.