How to Migrate from Greenhouse ATS: Data Export, Timeline & What to Expect

Greenhouse is a well-built product. The companies that are migrating away from it are typically doing so for one of two reasons: pricing that has increased significantly since initial selection, or a reduction in hiring volume that means the platform's capability exceeds current needs and the cost no longer justifies the feature set.

Both are valid triggers for a migration evaluation. What's worth acknowledging up front is that Greenhouse's core contribution to your hiring operation is often the structured hiring methodology it supports — structured interview kits, scorecard-based evaluation, multi-stage approval workflows. These practices don't live in Greenhouse; they live in your team's habits and processes. A migration that preserves the data but abandons the methodology is a step backwards. A migration that moves both data and methodology to a new platform that supports them at a lower cost is a genuine win.

This guide is for teams that want to do the second kind of migration: careful, complete, and preserving the hiring quality standards you've built, not abandoning them for the convenience of a simpler product.

Greenhouse data export options

Greenhouse's Harvest API is one of the most capable data export interfaces in the ATS category. It gives you programmatic access to virtually all data in your Greenhouse account in structured JSON format. If your target ATS supports Greenhouse API import — which several modern platforms do — the data migration itself is relatively clean.

For teams without API access or developer resources, Greenhouse's native CSV export covers most data types. The following data categories are exportable from Greenhouse:

• Candidate profiles. Name, contact details, source attribution, custom tags, and all custom fields added to your Greenhouse configuration.
• Application history. Each application to a specific job, the pipeline stages it passed through, and the dates of each stage transition.
• Rejection reasons. The reason recorded at each rejection point — important for EEOC disposition code requirements.
• Notes and activity logs. Recruiter and hiring manager notes on candidate records, activity timestamps, and communication history.
• Offer data. Offer details for accepted and rejected offers in your history.
• Job postings. Job titles, descriptions, hiring team assignments, and status history.
• Source tracking. Application source attribution data (job board, referral, direct, etc.).

What doesn't export as functional data

The critical distinction in any Greenhouse migration is between data (candidate records, application history, notes) and configuration (interview kits, pipeline stages, automation rules, approval workflows). Data exports cleanly. Configuration needs to be rebuilt.

Greenhouse's interview kits — the structured templates with competency areas, specific questions, and scoring guides that your interviewers use — are Greenhouse-specific configurations. They can be exported as documentation (a structured list of each kit's content) and used as blueprints for rebuilding in the new system. But they don't import as functional templates. Plan the interview kit rebuild explicitly in your migration project plan: it typically takes 1–2 weeks for a team with 10–20 active interview kits.

Preserving structured hiring methodology: the real risk

This is the migration risk that's underestimated in most Greenhouse migration plans. Greenhouse users have often built sophisticated structured hiring practices: multi-stage interview processes with specific interview types at each stage (phone screen, technical assessment, culture interview, executive review), scorecard-based evaluation with specific competency ratings, and team calibration conversations structured by the scorecard data.

When evaluating alternative ATS platforms as a Greenhouse replacement, the evaluation criteria that matters most is: does this platform support the hiring practices we've built, or will using it require simplifying our process? Ask each vendor to demonstrate:

• How you build a structured interview kit with multiple competency areas and specific questions per competency
• How an interviewer accesses their interview kit during the interview and records scorecard ratings
• How hiring manager scorecards from multiple interviewers are aggregated and visible to the hiring team for a calibration discussion
• How you configure a multi-stage approval workflow for job requisitions and offer letters

If any of these demonstrations shows a meaningful capability gap, that gap will translate directly to a reduction in the quality of your hiring process post-migration — regardless of how much the new platform costs.

Migration timeline: 6–10 weeks

The timeline below assumes a company that has been on Greenhouse for 2–4 years with a well-developed structured interview configuration, 4–8 active integrations, and 15–30 active users.

Weeks 1–2: Discovery and selection

• Export all interview kit documentation from Greenhouse. This is your rebuild specification.
• Complete your integration inventory — list every tool connected to Greenhouse and document the data flows.
• Export candidate data and review completeness. Identify historical data you can archive vs. migrate.
• Evaluate 2–3 alternative platforms. Prioritise demonstrations of structured interview and scorecard capability.
• Select target platform and sign contract.

Weeks 3–5: Configuration and rebuild

• Configure pipeline stages that mirror your Greenhouse configuration.
• Rebuild interview kits using your exported Greenhouse documentation as the specification. Review and improve where appropriate.
• Configure user accounts and permission groups (recruiter, hiring manager, interviewer, admin).
• Set up job templates and application form configurations.
• Begin integration re-mapping. Prioritise the integrations your team uses daily.
• Configure approval workflows for job requisitions and offers.

Weeks 6–7: Data import and testing

• Run pilot candidate data import (200–500 records). Verify completeness and field mapping.
• Run a complete end-to-end test job: post, apply, screen, conduct structured interview with scorecard, calibrate, offer.
• Brief 2–3 experienced recruiters to use the new system for one active role. Collect structured feedback.
• Fix configuration gaps identified in testing.
• Run full candidate data import once testing is confirmed.

Weeks 8–9: Training, go-live, parallel running

• Train recruiter users. Focus on the structured interview workflow — this is the highest-risk area for user adoption.
• Prepare interviewer-specific guidance (simpler than full recruiter training — focused on accessing and completing scorecards).
• Communicate go-live to hiring managers and interviewers.
• Go live. All new job postings go in the new system.
• Keep Greenhouse in read-only mode for active pipelines. Complete late-stage candidates in Greenhouse.

Week 10: Close out Greenhouse

• Confirm all active Greenhouse pipelines are resolved.
• Verify data export completeness and store securely.
• Submit Greenhouse cancellation notice per your contract's notice period requirement.

The Greenhouse cost reality in 2026

Greenhouse's pricing model has evolved significantly since the product's early growth phase. The platform now operates on a custom enterprise pricing model that is not published, varies by company size and hiring volume, and increases annually. Companies that joined Greenhouse three to five years ago at mid-market pricing have often seen their annual costs double or triple as Greenhouse has repositioned upmarket and renegotiated renewals at higher rates.

The economics that drive Greenhouse migration decisions typically look like this: a company has 50–200 employees, is doing 50–150 hires per year, and is paying $20,000–$60,000 annually for Greenhouse. When a renewal quote comes in at 20–35% above the previous year, the question becomes concrete: is the value differential between Greenhouse and alternatives worth the price premium?

The honest answer depends on what features your team actually uses. Greenhouse's differentiation points — structured interview kits, scorecard aggregation, approval workflow depth — are genuinely valuable if your team uses them consistently. If your team uses Greenhouse's pipeline management features but has never built out the structured interview capability, you're paying for capability you're not using.

Three questions to answer before you start a Greenhouse migration evaluation:

1. What does your team actually use? Pull usage data from Greenhouse if available: which features are actively used, which have been configured but rarely accessed, which are not configured at all. Usage patterns tell you more about your requirements than feature lists.
2. What would you rebuild in a new system? For every feature you actively use, identify whether your shortlisted alternatives support it at equivalent depth. The migration is worth doing if you can preserve 90%+ of your capability at meaningfully lower cost.
3. What is the migration cost in time, not money? A migration project runs 6–10 weeks of focused effort from a 2–4 person project team. The time cost is real. Factor it against the annual savings and ask whether the savings justify the investment. For most teams paying Greenhouse enterprise pricing, the payback period is 6–12 months.

What to evaluate in a Greenhouse replacement

Not every ATS that can import Greenhouse data can replace Greenhouse's hiring methodology. The platforms most commonly evaluated as Greenhouse replacements fall into two groups: those that support structured interviewing and scorecards at roughly comparable depth, and those that offer a simpler pipeline management approach at significantly lower cost.

Choosing the second category isn't necessarily wrong — if your hiring volume has reduced, or if you've reflected and concluded that Greenhouse's structured interview depth exceeded what your team actually used, a simpler platform at lower cost is a defensible choice. But make that choice consciously, not by default.

For teams that want to preserve Greenhouse-quality structured hiring, the evaluation should focus on:

• Interview kit structure: Can you build templates with multiple sections, section-level questions, and separate ratings per competency? Or does the platform offer a simpler overall rating?
• Scorecard aggregation: When multiple interviewers complete scorecards, can the hiring manager see a consolidated view with individual and aggregate ratings? Can they filter by competency across interviewers?
• Calibration support: Is there a structured way to facilitate a calibration conversation using scorecard data, or does calibration happen in Slack/email/a meeting room whiteboard?
• Approval workflows: Multi-stage approval for job requisitions and offer letters — who can approve, in what sequence, and what happens when an approver is unavailable?
• Historical data usability: Once your Greenhouse data is imported, can your team actually work with it? Search it, filter it, use it for pipeline analysis?

Treegarden as a Greenhouse migration path

Treegarden supports structured interview kits with multi-stage competency assessment, scorecard aggregation across interviewing teams, and approval workflows for both requisitions and offers. The structured hiring methodology that Greenhouse teams have built can be preserved — it just needs to be rebuilt in Treegarden's configuration rather than imported as-is.

Treegarden's pricing starts at $299/month and includes all features at every tier. There's no premium tier required for structured interview capability, approval workflows, or integration access. For a team paying $20,000–$40,000/year for Greenhouse, the economics of migration typically justify the 6–10 weeks of project time within the first year.

Treegarden's onboarding team provides structured migration support: data import tooling for Greenhouse CSV exports and Harvest API data, integration re-mapping documentation, and configuration consulting to rebuild interview kits from Greenhouse export documentation. The migration timeline is what it is — 6–10 weeks done properly — but you're not doing it alone.

Communicating the change to hiring managers

Greenhouse users — particularly hiring managers who use the scorecard review process regularly — have developed muscle memory for how hiring works. The most important communication isn't the announcement; it's the specific answer to their question: "Will this new system still let me review structured scorecards from all my interviewers before we make a decision?"

If the answer is yes, lead with that. If the answer is "sort of" or "in a different way," be honest about what's changing and why the trade-off is worth it. Hiring managers who discover after go-live that the evaluation workflow they relied on has been simplified — without being told in advance — become persistent critics of the new system regardless of its other merits.

The communication sequence that works: announce the migration with sufficient lead time (3–4 weeks before go-live), hold a 30-minute demo session for hiring managers showing specifically the structured interview and scorecard workflow in the new system, and provide written guidance (1–2 pages) on what's the same, what's different, and why. Hiring managers who understand the change before go-live are net-positive about the new system within 60 days of launch. Hiring managers who discover the change at go-live are never fully on board.

Frequently asked questions

What data can I export from Greenhouse?

Candidate profiles, application history, rejection reasons, notes, offer data, job postings, and source tracking all export cleanly via Greenhouse's Harvest API or native CSV export. Interview kit templates, automation rules, pipeline configuration, and approval workflows do not export as transferable data — they need to be rebuilt in the new system from your Greenhouse documentation.

How long does a Greenhouse migration take?

6–10 weeks for a company with established structured interview configurations and multiple integrations. The data migration itself is 1–2 weeks; the interview kit rebuild, integration re-mapping, and testing period account for the rest. Companies that have rushed this and gone live with an incomplete rebuild have typically needed to go back and complete it under production pressure, which is harder than doing it right the first time.

Will I lose my interview scorecards when migrating?

The scorecard templates don't transfer as functional configurations — they need to be rebuilt. But your scorecard content (questions, competency frameworks, scoring guidance) can be exported from Greenhouse as documentation and used as the blueprint for the rebuild. Budget 1–2 weeks specifically for interview kit rebuild, and treat the rebuild as an opportunity to review and improve your interview designs rather than just copying them.

Is it hard to switch from Greenhouse to a simpler ATS?

The migration isn't hard — the methodology gap is. Greenhouse teams have built structured hiring practices that require a platform that supports structured interviews and scorecard evaluation. Switching to an ATS that doesn't support these practices means either simplifying your hiring process or building manual workarounds. Verify structured interview capability in any alternative before committing to the switch.