Crelate to HubSpot
Recruitment CRM and ATS for staffing and recruiting firms. It covers candidates, contacts, companies, jobs and business-development opportunities.
Crelate data can move into HubSpot, landing mainly in Sales Hub. 2 of 6 mapped objects move directly (Contacts (candidates and client contacts) and Companies (clients)); 3 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 Crelate
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 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 10,000
Single-pass CSV import.
Mid migration
10,000-100,000
Custom jobs object and activity import.
Large migration
100,000+
API or backup extraction, phased cutover and a co-existence period.
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 Crelate: what you need to get in, what lands in HubSpot, and what will not.
REST API v3 with a public OpenAPI spec. Its base URL is https://app.crelate.com/api3.
A per-user API key. Enable API Access in the user profile.
Not confirmed in the sources. Full-database backup and export rights are likely admin-level, which I could not verify.
Choose your route
How will you move the data?
No native connector was found.
- You need: A per-user API key. Enable API Access in the user profile.
- Permission: Not confirmed in the sources. Full-database backup and export rights are likely admin-level, which I could not verify.
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.
- Excel/CSV export of Contacts, Companies or Opportunities, up to 15,000 records at a time from the Contacts tab and 10,000 from Search
- Optional Record ID (GUID) column on any export
- Full database export (backup), also available through the API at /api3/backups
- API retrieval using modified-date polling; one source says there are no webhooks
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 Crelate
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts (candidates and client contacts) | Contacts | yes | Export with Record IDs. Add a custom property to hold the Crelate ID, and use a field or tag to separate candidates from client contacts. |
| Companies (clients) | Companies | yes | Companies can be exported. Parent account relationships need a separate association step. |
| Opportunities (business development) | Deals | partial | Opportunities can be exported. Pipelines and stages must be rebuilt in HubSpot first. |
| Jobs (vacancies) | Custom objects | partial | HubSpot has no native job object, so a custom object is a reasonable choice. Jobs can be retrieved through the API. |
| Notes and Tasks | Notes | partial | The Crelate API supports Note and Task records. Import them through the HubSpot imports API or activity import. |
| Candidate documents and resumes | Files | manual | Whether the full backup includes documents is not confirmed in the sources. |
What to expect
These are functions of Crelate rather than data. Keep them in Crelate or replace them with another tool.
Not exportable as data. They must be rebuilt in HubSpot.
Candidate-to-job links need a custom object and custom associations in HubSpot.
Tags are organised by category and custom fields have logical names. Both need property mapping.
Exports are capped at 15,000 records per run, so a large database needs the backup or the API.
Add a contact-type property and dedupe by email before import.
Use the full backup export or the API.
Read each entity's /info endpoint and use polling during any delta sync.
Split files to stay within the limits.
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, API and HubSpot import limits are backed by Crelate and HubSpot docs. The object-to-HubSpot mapping, rate limits, governance and certifications are not documented in the sources I found, so they rest on category-level analyst judgement.
Sources
Related migrations
Frequently asked questions
How do I migrate Crelate to HubSpot?
1. Inventory the Crelate record types: contacts, companies, opportunities, jobs, notes and tasks. 2. Enable API Access and generate an API key, or request a full data export (backup). 3. Export with Record IDs (GUID) included so the Crelate ID can be stored in HubSpot. 4. Decide which functions stay in Crelate: parsing, job-board posting, payroll or compliance.
What data can move from Crelate to HubSpot?
These objects move directly: Contacts (candidates and client contacts) and Companies (clients). Check the mapping table for partial and manual items.
What does not move from Crelate to HubSpot?
ATS resume parsing and job-board distribution and Crelate workflows, automations and portal or application forms. Plan to rebuild or retire these.
How long does a Crelate to HubSpot migration take?
Small (Up to 10,000): 2-4 weeks. Mid (10,000-100,000): 4-8 weeks. Large (100,000+): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Crelate?
A per-user API key. Enable API Access in the user profile. Not confirmed in the sources. Full-database backup and export rights are likely admin-level, which I could not verify.
What compliance issues apply when moving Crelate data?
Check: Candidate PII and possibly sensitive data such as diversity or background check results and Compliance data for hiring, such as right-to-work and payroll records, may need to stay in a system of record. Agree consent, retention and access rules before exporting.
Moving Crelate 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