Teamtailor to HubSpot
Applicant tracking system and employer branding platform with career sites, recruitment workflows, candidate communications and analytics.
Teamtailor data can move into HubSpot, landing mainly in Sales Hub. 1 of 7 mapped objects move directly (Candidates); 3 items need manual work and 2 do not move. Plan roughly 2-3 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for Teamtailor
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 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
Under 5k candidates
Zapier, a script or CSV may be enough.
Mid migration
5k-50k candidates
Scripted API extract with jobs as a custom object.
Large migration
50k+ candidates
Throttled extract, file migration and a parallel run with the ATS.
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 Teamtailor: what you need to get in, what lands in HubSpot, and what will not.
REST, JSON:API
Secret API key with Read scope, plus the regional base URL (EU, NA or APAC).
Keys are generated under Settings > Integrations > API keys by a Company Admin.
50 requests per 10 seconds, HTTP 429 when exceeded, X-Rate-Limit-* headers. Page size max 30. Large endpoints such as answers and actions can return HTTP 500 if fetched in one request.
Choose your route
How will you move the data?
No native connector was found.
- You need: Secret API key with Read scope, plus the regional base URL (EU, NA or APAC).
- Permission: Keys are generated under Settings > Integrations > API keys by a Company Admin.
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.
- Public API reads of jobs, candidates, job applications, users, departments, locations and uploads
- Warehouse or ETL extraction via the API (for example dlt)
Limits: 50 requests per 10 seconds, HTTP 429 when exceeded, X-Rate-Limit-* headers. Page size max 30. Large endpoints such as answers and actions can return HTTP 500 if fetched in one request.
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-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In Teamtailor
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Candidates | Contacts | yes | A candidate is keyed by a unique email address, so use email as the HubSpot dedupe key. |
| Job applications | Deals | partial | Applications link a candidate to a job and a stage. They can map to Deals in a custom pipeline or to a custom object. |
| Jobs | Custom objects | partial | There is no native Jobs object in HubSpot, so a custom object is likely. The HubSpot partner integration works the other way, creating job drafts from closed deals. |
| Notes (comments) | Notes | partial | Candidate notes are exposed as separate objects. They are attached to the Contact on import. |
| Uploads (CVs, files) | Files | manual | The API lists uploaded files. Re-hosting and associating them with records is scripted work. |
| Departments, locations, users | Companies | manual | These are reference data, not client records. Users map to HubSpot owners. |
| Client companies and BD pipelines | Companies | no | Teamtailor is an ATS, so client and business-development data is usually held elsewhere. None of the sources show it. |
What to expect
Teamtailor-specific functions with no HubSpot equivalent, so they would need to be retained.
No source shows these are exposed through the API, so they must be rebuilt.
Teamtailor has a relational model. Custom-field-values and answers are separate objects.
Stage types come from the applications endpoint.
These stay in Teamtailor if the ATS is retained.
Carry consent fields over and set the HubSpot marketing contact status deliberately.
Use include to cut round trips, add a delay of about 300ms between requests, and back off on 429.
Paginate with small pages and filter by date.
Confirm the region and send X-Api-Version on every call.
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 access, auth and rate limits are backed by Teamtailor docs and support pages. There is no HubSpot-documented Teamtailor import path. Object mapping, export options, governance and cost rest on category-level knowledge. Teamtailor has no native CRM export documented here.
Sources
Related migrations
Frequently asked questions
How do I migrate Teamtailor to HubSpot?
1. Decide whether Teamtailor stays as the ATS or is retired. 2. Have a Company Admin generate a Read-scope API key. 3. Confirm the regional base URL (EU, NA or APAC). 4. Inventory custom fields, stages, jobs and candidate volumes.
What data can move from Teamtailor to HubSpot?
These objects move directly: Candidates. Check the mapping table for partial and manual items.
What does not move from Teamtailor to HubSpot?
Career site, job-board distribution and employer branding and Automations and workflow rules. Plan to rebuild or retire these.
How long does a Teamtailor to HubSpot migration take?
Small (Under 5k candidates): 2-3 weeks. Mid (5k-50k candidates): 4-8 weeks. Large (50k+ candidates): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from Teamtailor?
Secret API key with Read scope, plus the regional base URL (EU, NA or APAC). Keys are generated under Settings > Integrations > API keys by a Company Admin.
Is there a native HubSpot connector for Teamtailor?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Teamtailor data?
Check: Recruitment data may include sensitive or special-category information and Candidates may be minors. Agree consent, retention and access rules before exporting.
Moving Teamtailor 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