Loxo to HubSpot
Loxo is a talent intelligence platform that combines ATS, recruiting CRM, sourcing, outreach and, for agencies, Deals for business development.
Loxo data can move into HubSpot, landing mainly in Sales Hub. 3 of 7 mapped objects move directly (People (candidates), People (client contacts) and Companies (clients)); 4 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 Loxo
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 people, <1k companies
CSV and API only.
Mid migration
10k-100k people
Includes job custom object and activities.
Large migration
>100k people with resumes and history
Needs a support export and custom scripting.
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 Loxo: what you need to get in, what lands in HubSpot, and what will not.
REST Open API (bearer token)
An API domain/account and API key. One third-party guide says Loxo Support must create the API account first, and the key is then issued under Settings > API Keys.
Admin is required for UI export. API keys are issued in settings.
Choose your route
How will you move the data?
No native connector was found.
- You need: An API domain/account and API key. One third-party guide says Loxo Support must create the API account first, and the key is then issued under Settings > API Keys.
- Permission: Admin is required for UI export. API keys are issued in 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.
- Admin UI CSV export of selected People or Company records, limited to fields visible in List view
- Job pipeline candidate export from List view
- Open API (People, Companies, Jobs, dynamic fields per third-party guide)
- Full data export via Loxo support (per third-party guide, may be at contract end)
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 Loxo
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People (candidates) | Contacts | yes | Available via CSV and the /people API. CSV is List-view fields only and excludes resumes, activity history, work experience and education per a third-party guide. |
| People (client contacts) | Contacts | yes | People records in Loxo cover both candidates and contacts. Use a type property to separate them in HubSpot. |
| Companies (clients) | Companies | yes | Available via CSV and the /companies API. |
| Jobs | Custom objects | partial | The /jobs API exists. Candidate-to-job pipeline membership needs a List-view export per job, and HubSpot has no native job object. |
| Deals (business development) | Deals | partial | The guide reports no documented list endpoint, only webhooks, so a full export likely needs Loxo support. |
| Activities and notes | Notes | manual | There is no self-serve UI export. Only a full export from Loxo support includes them, per the third-party guide. |
| Resumes and attachments | Files | manual | These are excluded from CSV export per the third-party guide. |
What to expect
Loxo treats Source data as proprietary and limits exports of it, including via the API. Your own custom field entries on Source profiles are exported.
These are Loxo functions with no HubSpot equivalent, so they must be rebuilt or retained.
The self-serve CSV is limited, and the third-party guide says a full export comes via support.
HubSpot has no native job object, so a custom object or deal pipeline is needed.
Resumes and attachments are not in CSV export.
Outreach automation does not export.
Configure the List view columns before export, or use the API.
Confirm API entitlement early and throttle requests.
Add a record-type property and dedupe on email before import.
Export only records you own.
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.
Export paths and the Open API are backed by Loxo help docs and a third-party guide. Object-level API coverage, rate limits and HubSpot mapping are not confirmed in vendor or HubSpot docs, so they rest on the third-party guide and category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Loxo to HubSpot?
1. Confirm you have an Admin login, since only Admins can export. 2. Ask Loxo Support about API enablement and a full data export. 3. Inventory custom fields, lists, activity types and pipelines. 4. Decide which functions stay in Loxo (ATS parsing, job-board posting).
What data can move from Loxo to HubSpot?
These objects move directly: People (candidates), People (client contacts) and Companies (clients). Check the mapping table for partial and manual items.
What does not move from Loxo to HubSpot?
Loxo Source (database) profiles beyond the 500-profile export limit and ATS parsing, job-board distribution and sequence automations. Plan to rebuild or retire these.
How long does a Loxo to HubSpot migration take?
Small (<10k people, <1k companies): 2-4 weeks. Mid (10k-100k people): 4-8 weeks. Large (>100k people with resumes and history): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Loxo?
An API domain/account and API key. One third-party guide says Loxo Support must create the API account first, and the key is then issued under Settings > API Keys. Admin is required for UI export. API keys are issued in settings.
What compliance issues apply when moving Loxo data?
Check: Employment and hiring data, Possibly protected-class or diversity data and Candidate data subject to GDPR/CCPA. Agree consent, retention and access rules before exporting.
Moving Loxo 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