ServiceNow ITSM to HubSpot
ServiceNow ITSM is an enterprise IT service management product on the Now Platform. It covers incident, request, problem, change and knowledge, and is built on a shared CMDB.
ServiceNow ITSM data can move into HubSpot, landing mainly in Service Hub. 3 of 6 mapped objects move directly (Incident / customer service case, Caller / user (sys_user) and Company / account); 4 items need manual work and 3 do not move. Plan roughly 3-6 weeks for a small move and 12-24 weeks for a large one.
Migration checklist for ServiceNow ITSM
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
<50k tickets
CSV export and import.
Mid migration
50k-500k tickets
API extraction, attachments, notes.
Large migration
>500k tickets
Batched API extract, a coexistence design with ServiceNow, and archive decisions.
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 ServiceNow ITSM: what you need to get in, what lands in HubSpot, and what will not.
REST (Table API) on the instance
Integration user on the instance, with a Bearer token or Basic credentials.
The integration user needs read access (ACLs) to the target tables. Rate limit rules are changed by an admin.
Rate limits are instance-configured. One source found no default rules on the Table API. Default page size is 10,000 records, and the default REST transaction quota is 60 seconds.
Choose your route
How will you move the data?
No native connector was found.
- You need: Integration user on the instance, with a Bearer token or Basic credentials.
- Permission: The integration user needs read access (ACLs) to the target tables. Rate limit rules are changed by an admin.
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.
- Table API GET with sysparm_limit/sysparm_offset pagination
- CSV export from a list or URL (can silently truncate on large tables; batch by filter such as date)
- Scripted REST APIs for custom extracts
Limits: Rate limits are instance-configured. One source found no default rules on the Table API. Default page size is 10,000 records, and the default REST transaction quota is 60 seconds.
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: 12-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In ServiceNow ITSM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Incident / customer service case | Tickets | yes | Map state to ticket status and a pipeline. HubSpot ticket import needs name, pipeline and status. |
| Caller / user (sys_user) | Contacts | yes | Email is the dedupe key. Keep the sys_id in a custom unique property. |
| Company / account | Companies | yes | The company domain is the match key. |
| Knowledge articles | Custom objects | manual | Rebuild only approved articles in the HubSpot knowledge base. Bulk import of articles is not confirmed in the sources found. |
| Comments and work notes | Notes | partial | Pull from the journal table (sys_journal_field) and load as Notes associated to the Tickets. The route and any limits are unverified. |
| Attachments | Files | manual | Attachments are served by a separate attachment API. File import needs scripting. |
What to expect
Out of scope by analyst note. Retain in ServiceNow.
These are platform logic, not data. Rebuild them with HubSpot workflows.
No HubSpot equivalent. Retain in ServiceNow.
HubSpot rejects invalid stages, statuses or pipelines.
Only approved content moves.
The API returns references as sys_id unless display values are requested.
Association labels need Professional or Enterprise.
Use paginated API extraction, or batch the CSV exports by date, and reconcile counts against X-Total-Count.
Page in batches, order by sys_created_on, and run off-peak.
Check association limits before import.
Check ticket and contact limits before loading.
Store the original dates and sys_id in custom properties.
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 ServiceNow Table API, CSV export and pagination behaviour are supported by ServiceNow support and community material, and HubSpot import limits are sourced. I did not retrieve ServiceNow's official auth docs, a native HubSpot connector, or certification and residency pages. Those parts, and the object mapping, rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate ServiceNow ITSM to HubSpot?
1. Scope tables with the ServiceNow team: incident, sn_customerservice_case, sys_user, customer_account, kb_knowledge. 2. Create a read-only integration user and a Bearer or Basic credential, and confirm its ACLs. 3. Count records per table with X-Total-Count and agree what is kept in ServiceNow. 4. Create HubSpot ticket pipelines, statuses and custom properties for number and sys_id.
What data can move from ServiceNow ITSM to HubSpot?
These objects move directly: Incident / customer service case, Caller / user (sys_user) and Company / account. Check the mapping table for partial and manual items.
What does not move from ServiceNow ITSM to HubSpot?
CMDB, asset management and relationships, Workflows, flows, SLAs, business rules and ACLs and Change, problem and workforce management / dispatch. Plan to rebuild or retire these.
How long does a ServiceNow ITSM to HubSpot migration take?
Small (<50k tickets): 3-6 weeks. Mid (50k-500k tickets): 6-12 weeks. Large (>500k tickets): 12-24 weeks. These are planning estimates, not a quote.
What access do I need to export from ServiceNow ITSM?
Integration user on the instance, with a Bearer token or Basic credentials. The integration user needs read access (ACLs) to the target tables. Rate limit rules are changed by an admin.
What compliance issues apply when moving ServiceNow ITSM data?
Check: Cases may hold health, financial or minors' data in free text and Employee HR data if HR cases are in scope. Agree consent, retention and access rules before exporting.
Moving ServiceNow ITSM 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