iCIMS to HubSpot
iCIMS is a talent cloud and applicant tracking platform that includes ATS, candidate relationship management and recruiting workflows.
iCIMS data can move into HubSpot, landing mainly in Sales Hub. 0 of 5 mapped objects move directly; 3 items need manual work and 2 do not move. Plan roughly 3-5 weeks for a small move and 10-18 weeks for a large one.
Migration checklist for iCIMS
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 candidates
Mostly contacts and companies.
Mid migration
10k-100k
Jobs custom object and attachments.
Large migration
>100k
Multiple instances, compliance and a coexistence 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 iCIMS: what you need to get in, what lands in HubSpot, and what will not.
REST (Applicant Tracking APIs, Profiles, Workflows) plus flat-file transfers
A client_id and client_secret authorized by the customer's iCIMS Integration Specialist. A customer integration license may be required.
The iCIMS customer must request and authorize API credentials through its Integration Specialist.
A third-party directory reports a default of 10,000 calls per day per customer. This is not confirmed in vendor docs I viewed.
Choose your route
How will you move the data?
No native connector was found.
- You need: A client_id and client_secret authorized by the customer's iCIMS Integration Specialist. A customer integration license may be required.
- Permission: The iCIMS customer must request and authorize API credentials through its Integration Specialist.
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 pulls of profiles and jobs
- Flat-file or file-based exports
- Reports exported from the UI (not verified)
Limits: A third-party directory reports a default of 10,000 calls per day per customer. This is not confirmed in vendor docs I viewed.
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-18 weeks, usually phased.
Talk to a partnerWhere each object lands
In iCIMS
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Candidate profiles | Contacts | partial | Pull via the Profiles API and map to Contacts, with a custom property for the iCIMS person ID. |
| Companies / clients | Companies | partial | Depends on whether the tenant uses iCIMS company or CRM profiles. This is unverified. |
| Jobs / requisitions | Custom objects | partial | Rebuild as a Jobs custom object, or as Deals if a business-development pipeline is wanted. |
| Applications / workflows | Deals | manual | Application-to-job associations need a custom association design. |
| Notes, attachments, resumes | Files | manual | Needs scripted download via the API and re-upload. |
What to expect
HubSpot has no equivalent; retain iCIMS or another ATS for these.
These are platform-specific configuration with no HubSpot equivalent.
Credentials must be authorized by iCIMS, and the authorization server depends on region.
HubSpot has no native ATS objects.
iCIMS uses configurable lists with IDs.
Agree retention rules with legal before migrating.
Request credentials from the iCIMS Integration Specialist early.
Batch extracts and confirm the actual limits with iCIMS.
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.
Auth and API access are backed by iCIMS developer docs. Object mapping to HubSpot, export options, rate limits and governance rest on third-party or category-level knowledge, and no HubSpot-side docs were reviewed.
Sources
Related migrations
Frequently asked questions
How do I migrate iCIMS to HubSpot?
1. Ask the iCIMS Integration Specialist for OAuth client credentials. 2. Identify the correct regional authorization server. 3. Inventory the profile types and custom fields available through the API. 4. Decide which functions stay in iCIMS: parsing, job-board distribution and compliance.
What does not move from iCIMS to HubSpot?
ATS resume parsing and job-board distribution logic and Onboarding, compliance (EEO) and workflow configuration. Plan to rebuild or retire these.
How long does a iCIMS to HubSpot migration take?
Small (<10k candidates): 3-5 weeks. Mid (10k-100k): 6-10 weeks. Large (>100k): 10-18 weeks. These are planning estimates, not a quote.
What access do I need to export from iCIMS?
A client_id and client_secret authorized by the customer's iCIMS Integration Specialist. A customer integration license may be required. The iCIMS customer must request and authorize API credentials through its Integration Specialist.
What compliance issues apply when moving iCIMS data?
Check: EEO/demographic data, Possible background-check data and Candidates who may be minors or in the EU. Agree consent, retention and access rules before exporting.
Moving iCIMS 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