Greenhouse → Eightfold

Catalog plan outline

General guidance from the Afterstack catalog for Greenhouse → Eightfold. Not Greenhouse or Eightfold vendor documentation.

Migration friendliness

Greenhouse 6/10 · Eightfold 5/10

Speed to live

Greenhouse 4/10 · Eightfold 3/10

Catalog migration difficulty

Greenhouse high · Eightfold high

Data to export from Greenhouse

• pipeline and deal records
• synced email and calendar links
• workflow rules
• saved reports
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: ats

How the catalogs differ

• Eightfold is flagged for custom objects. Collapse unused fields before loading them.
• Eightfold adds catalog flags Greenhouse does not have: custom objects.
• Greenhouse is flagged with an open API, which is the export path to test.
• Eightfold is flagged with an open API for the load.
• Greenhouse is cataloged as a fit for: Structured hiring programs with interview kits and scorecards.
• Eightfold is cataloged as a fit for: Enterprise talent intelligence.

Phases

1. Export

   Take Greenhouse as the source of truth for this pair. Export pipeline and deal records; synced email and calendar links; workflow rules; saved reports; installed marketplace apps; AI assistant configuration; records for the catalog use cases: ats. The structured-hiring ATS incumbents still standardize on.

2. Map

   Load into Eightfold only after the field map is written down. Talent intelligence platform — AI matching across hire, retain, and mobility. Eightfold is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Eightfold scores 3/10 on speed to live and 5/10 on migration friendliness. Run one sample load and one report the team already uses in Greenhouse before a full cutover.

4. Cut over

   Greenhouse scores 6/10 on migration friendliness and is marked high difficulty in the catalog. Keep Greenhouse readable until the team is working in Eightfold. Greenhouse made structured hiring the default for scaled tech recruiting. Scorecards, interview kits, and a marketplace. AI features arrived later. This is the ATS many teams want to replace when the pain is speed, sourcing, or admin weight.

Greenhouse to Eightfold: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Greenhouse or Eightfold vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Greenhouse

Greenhouse's own Eightfold article, last updated November 2, 2022 and reopened on 2026-10-17, is the source procedure for this pair. It is not a spreadsheet dump. The article says the Eightfold Integration Adapter uses Harvest, and that the same connection pushes some Eightfold actions back into Greenhouse. The credential screen it describes asks for API type Harvest, partner Eightfold, and a description of Eightfold Harvest API key. Permissions it tells you to select, all of them, cover activity feed, applications, candidates, close reasons, EEOC, job openings, job posts, job stages, prospect pool, rejection reasons, tags, and users. The read list it names is candidates, applications, jobs, stages on a job, job posts, sources, rejection reasons, a candidate activity feed, application EEOC, application scorecards, and users so Eightfold can see recruiter and hiring-manager name and email. The write list it names is notes and emails on the activity feed, a patch of application answers, reject, move, advance, a new application on a candidate, and a new candidate. Beside the key, Eightfold wants a site-admin user id taken from an Excel export of users. The article recommends a shared mailbox such as recruiting@ rather than a person who might leave. Four webhooks are required, and Eightfold supplies the endpoint URL and secret: application updated, new candidate added, candidate has submitted application, and application workflow status changes. Greenhouse's pricing page, opened the same day, names Core, Plus, and Pro and ends in a demo. The FAQ says price depends on plan, hiring volume, and complexity. No software dollar and no trial length appear. The catalog's empty starting price matches that page. The catalog's trial flag does not.

• Greenhouse Eightfold integration — checked 2026-10-17
• Greenhouse pricing — checked 2026-10-17

How Eightfold imports

Eightfold's getting-started page, opened the same day, describes API v2 as a REST surface on a different host from v1. It says v2 can inject and fetch profiles, positions, and ATS-shaped candidates, that several writes are asynchronous, and that a 2xx on an async call returns a transaction id rather than proof the write finished. The comparison table lists ATS candidate create as POST https://apiv2.eightfold.ai/api/v2/core/ats-systems/{systemId}/ats-candidates and marks that create async. ATS position create is on the same table and is not marked async. The page says existing customers may keep v1 until they move, that v1 feature work is mostly stopped, and that v1 bug fixes continue until deprecation. It does not print a deprecation date in the section that was read, and it does not mention Greenhouse. The Greenhouse article is the document that names the adapter. Finish-setup in that article happens in Eightfold's Admin Console. Eightfold's onboarding team enables the Greenhouse webhook and gives you the secret and the endpoint. Open jobs show on the Eightfold recruiter homepage. Confidential jobs stay visible only to the creator and users assigned in Greenhouse. Closed jobs are searchable from the global bar if you have the requisition number. Custom application questions appear on the candidate profile under Applications in the Recruiting Activity feed. Eightfold's request-demo URL, opened the same day, asks for a live demo of the Talent Intelligence Platform and prints no fee. A blog about AI Interviewer packaging is not the platform price and is not used here. The catalog's custom model matches the missing platform fee. The catalog's trial flag does not match a demo form.

• Eightfold API getting started — checked 2026-10-17
• Eightfold request a demo — checked 2026-10-17

Object and field mapping

• A Greenhouse candidate plus an application is what the adapter syncs. Eightfold's v2 ATS-candidate create is a different door. The Greenhouse article does not say the adapter posts that v2 body.
• A Greenhouse job is what shows as an open role on the Eightfold homepage. A closed job is a search by requisition number, not a homepage card.
• Scorecards are in the Harvest read list as application scorecards. Interview feedback is in the sync table: Greenhouse to Eightfold in 30 minutes, and the article says that sync can be turned off.
• Notes added in Eightfold sync to Greenhouse within 24 hours. Email sent from Eightfold lands on Recruiting Activity and on the Greenhouse activity feed within 24 hours.
• Advance and reject are asymmetric. Eightfold to Greenhouse is within 30 minutes. Greenhouse to Eightfold is within 24 hours. Do not treat those clocks as the same job.
• Profile edits are explicitly No in both directions. A name, position, or contact change in either system stays put.
• Saving a lead, starring a lead, saving from the Chrome extension, and saving to another pipeline stay in Eightfold. The article says they do not sync to the ATS.
• Add to ATS does sync. It places a lead or prospect on a Greenhouse job in Application Review within 30 minutes.

What will not carry over

• A one-time file that replaces Greenhouse. The article describes a living adapter, not a cutover export.
• Candidate profile edits, in either direction.
• Eightfold lead saves, stars, and Chrome-extension saves.
• Confidential-job visibility for people who cannot see that job in Greenhouse.
• A published Eightfold platform price. The demo page has none.
• A Greenhouse trial length. The pricing page offers a demo.
• v1 as the long-term API. The getting-started page says enhancements mostly stop and recommends v2, without a date in the section that was read.

Cutover checklist

1. Create the Harvest key with partner Eightfold and the permission groups the article lists. Do not invent a narrower scope.
2. Export the user list to Excel, copy a site-admin user id, and prefer a shared mailbox so the integration survives a departure.
3. Create the four webhooks with the endpoint and secret Eightfold gives you during onboarding. The article does not publish those values.
4. Hand Eightfold the key, the user id, and the organization web-service URL. Finish the adapter in the Eightfold Admin Console.
5. Decide whether interview-feedback sync stays on. The article says it can be turned off.
6. Tell recruiters that name and contact edits do not cross, and that lead saves stay in Eightfold until someone uses Add to ATS.
7. Keep Greenhouse as the system of record until a sample of open jobs, confidential jobs, and a stage change in each direction matches the clocks in the article.
8. Quote both products. Greenhouse's page is a demo. Eightfold's demo page is also a quote. Do not paste a third-party per-employee figure.

Common pitfalls

• Treating the adapter as permission to delete Greenhouse. Closed jobs and confidential jobs still depend on Greenhouse rules.
• Expecting a profile edit in Eightfold to repair the Greenhouse record. The sync table says no.
• Using v1 candidate routes for a new build because they still answer. The getting-started page says to move.
• Reading a 2xx on an async v2 write as a finished candidate. The page says you must check the transaction.
• Quoting an AI Interviewer blog as the Talent Intelligence Platform price. That page was not used as a source.

Related catalog pages

• Best AI-native Greenhouse alternatives (2026) — Which tool, compared
• What should replace Greenhouse? — Switch narrative
• Eightfold product page — Talent intelligence platform — AI matching across hire, retain, and mobility.
• Eightfold vs Greenhouse — Head-to-head already in the catalog
• Recruiting category — Catalog hub for this category