Firefish to HubSpot
Recruitment CRM and agency management platform for UK and European agencies. It covers permanent, temporary and contract recruitment, with ATS, business development, compliance and analytics.
Firefish data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Candidates, Contacts (client) and Companies (clients)); 3 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for Firefish
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
<10k records
Contacts and companies only.
Mid migration
10k-100k records
Includes vacancies and activity history.
Large migration
>100k records
Includes placements, documents and ongoing sync.
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 Firefish: what you need to get in, what lands in HubSpot, and what will not.
Open API with read and write access to recruitment data
API access is set up in Firefish API settings; exact credential type not confirmed.
Choose your route
How will you move the data?
No native connector was found.
- You need: API access is set up in Firefish API settings; exact credential type not confirmed.
- Permission: To confirm
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.
- Open API covering candidates, contacts, companies, jobs, placements/offers, actions, adverts, communications and users
- Zapier export of saved candidate or contact lists to tools including HubSpot
- Full data export on request from the vendor; later exports may cost extra, per a third-party review
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: 8-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Firefish
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Candidates | Contacts | yes | Readable via API. Use a candidate contact type or custom property to separate them from client contacts. |
| Contacts (client) | Contacts | yes | Readable via API. Associate to Companies. |
| Companies (clients) | Companies | yes | Readable via API. |
| Jobs (vacancies) | Deals | partial | Readable via API. Mapping to Deals or a Custom object is a design choice. |
| Placements/offers | Deals | partial | Readable via API, including extensions and terminations. Needs a model decision, such as a Custom object. |
| Actions and communications | Notes | partial | Readable via API. Import as Notes, Emails, Calls or Tasks depending on type. |
| Business development leads and pipelines | Deals | partial | Lead data is available to approved BD partners only. Pipeline stages are rebuilt in HubSpot. |
| CV and compliance documents | Files | manual | The documented API objects do not list documents. Confirm with Firefish. |
What to expect
Firefish-native functionality with no HubSpot equivalent.
Native Firefish feature that HubSpot does not replace.
Firefish-specific workflows that may need to stay in Firefish or another system.
Firefish BD pipelines have no direct import.
HubSpot has no native vacancy object.
Not confirmed as available through the API.
Add a record-type property and segment on it.
Export opt-out data and set HubSpot marketing contact status before any sends.
Agree the export scope and cost with Firefish in writing before cutover.
Define a system of record per object and use the API or Zapier for sync.
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.
The Firefish API docs and the Zapier-to-HubSpot path are sourced. The auth method, rate limits, bulk-export specifics, certifications and residency were not found, and object mapping to HubSpot is category-level analysis.
Sources
Related migrations
Frequently asked questions
How do I migrate Firefish to HubSpot?
1. Request a full Firefish data export and confirm cost and format. 2. Obtain API access from Firefish and review the API docs and Postman collection. 3. Decide which recruitment functions (parsing, multiposting, compliance) stay in Firefish. 4. Inventory custom fields, candidate vs contact types, and saved lists.
What data can move from Firefish to HubSpot?
These objects move directly: Candidates, Contacts (client) and Companies (clients). Check the mapping table for partial and manual items.
What does not move from Firefish to HubSpot?
AI CV parsing, Match AI scoring and automation rules, Job-board multiposting (36+ boards) and Contract, pay and compliance workflows, including right-to-work. Plan to rebuild or retire these.
How long does a Firefish to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Firefish?
API access is set up in Firefish API settings; exact credential type not confirmed.
Is there a native HubSpot connector for Firefish?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Firefish data?
Check: Right-to-work and identity documents, Possible special-category data in CVs and Payroll and financial data for contractors. Agree consent, retention and access rules before exporting.
Moving Firefish 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