Eploy to HubSpot
Cloud ATS and Talent CRM for in-house recruitment teams. It covers talent pools, onboarding, analytics and a careers site, and is also delivered through Advanced.
Eploy data can move into HubSpot, landing mainly in Sales Hub. 3 of 9 mapped objects move directly (Candidates, Contacts (client) and Companies); 3 items need manual work and 3 do not move. Plan roughly 3-5 weeks for a small move and 10-16 weeks for a large one.
Migration checklist for Eploy
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
up to 10k candidates
Contacts, companies and basic vacancies.
Mid migration
10k-100k
Adds applications, placements and files.
Large migration
100k+
Multiple workflows, a custom data model and a hybrid run with Eploy.
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 Eploy: what you need to get in, what lands in HubSpot, and what will not.
REST (OpenAPI/Swagger docs)
An API key generated in the Eploy system, plus OAuth2 client details.
The key inherits the permissions of the user it is tied to, so use a user with broad read access.
Choose your route
How will you move the data?
No native connector was found.
- You need: An API key generated in the Eploy system, plus OAuth2 client details.
- Permission: The key inherits the permissions of the user it is tied to, so use a user with broad read access.
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.
- REST API (Applications, Candidates, Vacancies, Placements, Contacts, Companies, Files, Actions, Timesheets, Users)
- Candidate Import supports CSV/XML for loading data into Eploy; a matching export route was not confirmed
- Reporting and analytics (export formats not confirmed)
Limits: To confirm
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: 10-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Eploy
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Candidates | Contacts | yes | Candidates API is available; use a custom property or lifecycle/lead status to separate candidates from client contacts. |
| Contacts (client) | Contacts | yes | Contacts API includes contact details and addresses. |
| Companies | Companies | yes | Companies API covers companies, departments and structure; departments need a parent/child association or a custom property. |
| Vacancies | Deals | partial | Vacancies API gives job descriptions and locations; a Deals pipeline or a Custom object is a design choice. |
| Applications | Custom objects | partial | Applications API includes workflow, Q&A, feedback and source; HubSpot has no native equivalent. |
| Placements | Deals | partial | Placements API includes offers, salaries and costs; map to closed-won Deals or a Custom object. |
| Actions / notes / correspondence | Notes | partial | The Actions API exposes actions, outcomes and statuses. Correspondence logs are tracked per record, but API coverage of them was not confirmed. |
| Files (CVs, documents) | Files | partial | Files API supports downloads and metadata; attach to records after upload. |
| Timesheets / pay rates | Custom objects | no | Back-office data that is better kept in payroll/HR systems. |
What to expect
HubSpot has no ATS parsing or job distribution; keep these in Eploy or a replacement tool.
These are Eploy features with no HubSpot equivalent.
These are payroll back-office functions.
HubSpot has no native vacancy or application object.
Eploy workflows and talent pools do not transfer as configuration.
No native HubSpot connector was found, and a bulk export route is unconfirmed.
Keep Eploy as the system of record for applications, or archive it, until retention periods end.
Migrate consent and opt-out fields and set legal basis before any marketing use.
Use a record-type property and separate lists, and keep candidates out of sales sequences.
Batch the extraction, test in the sandbox and ask Eploy support.
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 objects and auth are backed by Eploy and G-Cloud pages. No Eploy-to-HubSpot connector, export-tool or rate-limit documentation was found. Governance and object mapping rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Eploy to HubSpot?
1. Ask Eploy for Developer Portal access and the sandbox environment. 2. Generate an API key tied to a user with read access to all records. 3. Inventory the custom candidate, application and placement fields and questions. 4. Decide which functions stay in Eploy (parsing, multiposting, onboarding, payroll feeds).
What data can move from Eploy to HubSpot?
These objects move directly: Candidates, Contacts (client) and Companies. Check the mapping table for partial and manual items.
What does not move from Eploy to HubSpot?
CV parsing, careers site and job-board multiposting, Onboarding workflows and e-signature documents and Timesheets, pay rates and payroll/HR integrations. Plan to rebuild or retire these.
How long does a Eploy to HubSpot migration take?
Small (up to 10k candidates): 3-5 weeks. Mid (10k-100k): 6-10 weeks. Large (100k+): 10-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Eploy?
An API key generated in the Eploy system, plus OAuth2 client details. The key inherits the permissions of the user it is tied to, so use a user with broad read access.
What compliance issues apply when moving Eploy data?
Check: Hiring compliance and right-to-work/background checks, Salary data, Public sector (NHS, government) customers and Possible special-category data in diversity or assessment data. Agree consent, retention and access rules before exporting.
Moving Eploy 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