Greenhouse to HubSpot
Applicant tracking and recruiting platform covering jobs, candidates, applications, scorecards and offers.
Greenhouse data can move into HubSpot, landing mainly in Sales Hub. 1 of 7 mapped objects move directly (Candidates / Prospects); 3 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Greenhouse
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
Up to 5k candidates
Contacts and jobs only, no attachments.
Mid migration
5k-50k candidates
Includes applications, attachments and custom objects.
Large migration
50k+ candidates
Includes scorecards, long history, ongoing sync and compliance review.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Greenhouse: what you need to get in, what lands in HubSpot, and what will not.
REST (Harvest API; v3 is current, v1/v2 are retired after 2026-08-31)
A Harvest v3 client with granular scopes. Older v1/v2 keys come from Configure > Dev Center > API Credential Management.
A Site Admin must authorize v3 list endpoints.
v1/v2: the X-RateLimit-Limit header sets the limit per 10 seconds, with 50 documented as the example. v3: fixed 30-second window, with 75 observed and no universal number published. Token issuance is throttled separately per 60 seconds.
Choose your route
How will you move the data?
No native connector was found.
- You need: A Harvest v3 client with granular scopes. Older v1/v2 keys come from Configure > Dev Center > API Credential Management.
- Permission: A Site Admin must authorize v3 list endpoints.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Harvest API v3 for candidates, applications, jobs, scorecards and attachments
- UI CSV exports with flat candidate lists only, without relational data, scorecard ratings or resumes
- Audit Log API for security events
- Public Job Board API for published jobs only
Limits: v1/v2: the X-RateLimit-Limit header sets the limit per 10 seconds, with 50 documented as the example. v3: fixed 30-second window, with 75 observed and no universal number published. Token issuance is throttled separately per 60 seconds.
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Greenhouse
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Candidates / Prospects | Contacts | yes | Connectors map candidates to Contacts. Dedupe on email. |
| Jobs / Openings | Deals | partial | Connectors sync jobs as Deals. Custom objects are an alternative for vacancies. |
| Applications | Custom objects | partial | One candidate can have many applications, so Deals or custom objects are suggested. |
| Application status and answers | Notes | partial | Connectors send activity to HubSpot as timeline events, not native Notes. |
| Resumes / attachments | Files | manual | Attachments are retrievable via the API and must be uploaded and associated with records by script. |
| Scorecards, offers, interviews | Custom objects | manual | Readable via the API. No standard HubSpot target exists. |
| Clients / companies | Companies | no | Greenhouse is employer-side and has no client or BD CRM objects to export. |
What to expect
The API returns current permitted profiles only, not deleted payloads or intermediate history.
UI CSV exports are flat and omit these.
HubSpot has no ATS objects, so Deals or custom objects must be chosen.
Job posts need HubDB or another tool, and posting to job boards may need to stay in an ATS.
Build extraction on Harvest v3 with OAuth and token refresh.
Keep the ATS for compliance data or restrict access and apply retention rules in HubSpot.
Honor the Retry-After header, paginate, and run extraction in batches.
Dedupe on email and store the Greenhouse candidate ID as a unique property.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
API auth, rate limits and export paths are backed by Greenhouse docs and secondary guides. Object mapping to HubSpot comes from third-party connector listings, not HubSpot or Greenhouse docs. Greenhouse is an ATS for employer hiring, so client and business-development data is only a partial fit. Governance and cost are category-level.
Sources
Related migrations
Frequently asked questions
How do I migrate Greenhouse to HubSpot?
1. Decide which parts of Greenhouse are retired and which stay, such as parsing, job-board distribution and compliance. 2. Create a Harvest v3 client with the required scopes, authorized by a Site Admin. 3. Inventory custom fields, jobs, stages and sources, plus candidate and application counts. 4. Choose the HubSpot model for jobs and applications (Deals or custom objects).
What data can move from Greenhouse to HubSpot?
These objects move directly: Candidates / Prospects. Check the mapping table for partial and manual items.
What does not move from Greenhouse to HubSpot?
Deleted records and intermediate history and Scorecard attribute ratings and resume files via CSV. Plan to rebuild or retire these.
How long does a Greenhouse to HubSpot migration take?
Small (Up to 5k candidates): 2-4 weeks. Mid (5k-50k candidates): 4-8 weeks. Large (50k+ candidates): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Greenhouse?
A Harvest v3 client with granular scopes. Older v1/v2 keys come from Configure > Dev Center > API Credential Management. A Site Admin must authorize v3 list endpoints.
Is there a native HubSpot connector for Greenhouse?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Greenhouse data?
Check: Employment and EEO or demographic data, Possible background-check results and Possible minors and candidates in other jurisdictions (GDPR). Agree consent, retention and access rules before exporting.
Moving Greenhouse into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner