Workable to HubSpot
Cloud recruiting software (ATS) for job posting, candidate tracking and hiring, with HR modules for employees and time off.
Workable data can move into HubSpot, landing mainly in Sales Hub. 1 of 7 mapped objects move directly (Candidates); 4 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Workable
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
<2,000 candidates
CSV and API, contacts only.
Mid migration
2,000-20,000 candidates
Resumes, jobs as custom objects, dedupe.
Large migration
>20,000 candidates, multiple entities
Full history, integration with a retained 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 Workable: what you need to get in, what lands in HubSpot, and what will not.
REST (SPI v3, JSON) at https://<subdomain>.workable.com/spi/v3
Account API token with scopes such as r_candidates, plus the account subdomain.
Admin access to create tokens in the account's Integrations settings.
Account tokens: 10 requests per 10 seconds. OAuth and partner tokens: 50 per 10 seconds. HTTP 429 on breach, with X-Rate-Limit headers returned. Pages hold at most 100 records.
Choose your route
How will you move the data?
No native connector was found.
- You need: Account API token with scopes such as r_candidates, plus the account subdomain.
- Permission: Admin access to create tokens in the account's Integrations settings.
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.
- API extraction of jobs and candidates (candidates are listed per job)
- Candidate Details CSV report (excludes resume attachments)
- Full account data export on request to Workable support (requires archiving all jobs, all-or-nothing)
- Resume download via URLs in candidate detail API responses
Limits: Account tokens: 10 requests per 10 seconds. OAuth and partner tokens: 50 per 10 seconds. HTTP 429 on breach, with X-Rate-Limit headers returned. Pages hold at most 100 records.
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: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Workable
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Candidates | Contacts | yes | Candidates are listed per job, with no account-wide endpoint. Custom fields and questions come from extra endpoints. Dedupe by email. |
| Jobs / vacancies | Custom objects | partial | Jobs are readable by API. HubSpot has no native job object, so use a custom object or Deals. |
| Applications / pipeline stage | Deals | manual | Candidate-per-job records can become Deals or custom-object records associated to Contacts. This is an analyst design choice. |
| Resumes and attachments | Files | partial | Downloaded individually through URLs in candidate detail responses, with no bulk download. |
| Candidate comments / activity | Notes | manual | Not confirmed in the sources reviewed. Check whether the API exposes them. |
| Clients / companies and BD pipelines | Companies | no | No client or business-development objects were found in the sources reviewed. Build these in HubSpot or load from another source. |
| Employees (HR module) | Custom objects | partial | The API covers employees, but this data usually stays in HR systems. |
What to expect
These are Workable product functions, not data. HubSpot does not replace them.
No evidence they are exportable. They must be rebuilt or retained.
Candidates are scoped per job.
No bulk resume download exists, and the CSV report excludes attachments.
Workable has no equivalent CRM structure.
It requires archiving all jobs, which disrupts live hiring.
Keep Workable for hiring and migrate only the CRM and BD data.
Carry over consent and source fields, and set retention rules.
Throttle, back off on 429, or request OAuth or partner access.
Call the single-candidate endpoint for full fields.
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, rate limits and export paths rest on third-party summaries of Workable's docs (I did not open Workable's own docs). HubSpot object mapping and the CRM-side (clients, BD pipelines) are analyst category-level knowledge. Workable is mainly an ATS and has no documented client or BD CRM objects.
Sources
Related migrations
Frequently asked questions
How do I migrate Workable to HubSpot?
1. Decide whether Workable stays for ATS functions (partial replacement). 2. Create a scoped account token (r_candidates and the other read scopes you need) and note the subdomain. 3. Inventory jobs, custom fields and custom questions per job. 4. Define Contact, custom-object and Deal models for candidates, vacancies and applications.
What data can move from Workable to HubSpot?
These objects move directly: Candidates. Check the mapping table for partial and manual items.
What does not move from Workable to HubSpot?
ATS resume parsing and job-board distribution and Hiring workflow automations and scorecards. Plan to rebuild or retire these.
How long does a Workable to HubSpot migration take?
Small (<2,000 candidates): 1-2 weeks. Mid (2,000-20,000 candidates): 3-6 weeks. Large (>20,000 candidates, multiple entities): 6-12 weeks. These are planning estimates, not a quote.
What access do I need to export from Workable?
Account API token with scopes such as r_candidates, plus the account subdomain. Admin access to create tokens in the account's Integrations settings.
What compliance issues apply when moving Workable data?
Check: Hiring and employment data, Possible equal-opportunity or diversity data and Employee HR data, if the HR module is used. Agree consent, retention and access rules before exporting.
Moving Workable 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