Jira Service Management to HubSpot
Atlassian's ITSM and service desk product, built on Jira issues with request types, queues, SLAs, organizations, a customer portal and Assets (CMDB).
Jira Service Management data can move into HubSpot, landing mainly in Service Hub. 2 of 7 mapped objects move directly (Customers (portal users) and Organizations); 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 10-20 weeks for a large one.
Migration checklist for Jira Service Management
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 tickets, 1 service desk
CSV or tool-based.
Mid migration
10k-100k tickets, several desks
API or migration tool with workflow rebuild.
Large migration
>100k tickets, Assets integration
Custom scripts, phased cutover.
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 Jira Service Management: what you need to get in, what lands in HubSpot, and what will not.
REST (Jira platform API v2/v3 plus the JSM Service Desk API at /rest/servicedeskapi/)
Site URL plus an API token for an admin user, or an OAuth app.
Jira/site admin is needed for the full CSV import and export. Migration tools also require an admin user.
Cloud uses an hourly points-based quota plus per-second burst limits per endpoint, and returns HTTP 429. Exact thresholds are not fully published. Assets endpoints are limited to 1,000 requests per minute per instance.
Choose your route
How will you move the data?
No native connector was found.
- You need: Site URL plus an API token for an admin user, or an OAuth app.
- Permission: Jira/site admin is needed for the full CSV import and export. Migration tools also require an admin user.
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.
- Issue search results exported as CSV (all fields)
- REST API pagination for issues, requests, customers and organizations
- Assets export/import APIs
Limits: Cloud uses an hourly points-based quota plus per-second burst limits per endpoint, and returns HTTP 429. Exact thresholds are not fully published. Assets endpoints are limited to 1,000 requests per minute per instance.
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-20 weeks, usually phased.
Talk to a partnerWhere each object lands
In Jira Service Management
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Requests/issues (incidents, service requests) | Tickets | partial | CSV exports the latest state of issues but does not reliably keep comments, attachments, links, history or SLA data. Use the API for full fidelity. |
| Customers (portal users) | Contacts | yes | Retrievable via the servicedeskapi customer endpoints. Match on email. |
| Organizations | Companies | yes | Organizations are listed as an object that needs separate verification in JSM migrations. |
| Comments (public/internal) | Notes | partial | Needs the API. CSV does not reliably keep comments. |
| Attachments | Files | partial | Must be downloaded via the API, then uploaded and associated to tickets. |
| Knowledge base (Confluence articles) | Custom objects | manual | HubSpot knowledge base articles are not a standard object for import, so approved content is likely rebuilt by hand. This is category-level knowledge. |
| Assets (CMDB) | Custom objects | no | Retained in JSM or an ITAM tool per the scope note. Assets fields are not migrated by CSV. |
What to expect
These are JSM configuration, not data, and CSV does not carry them.
There is no equivalent import into HubSpot, so they must be rebuilt as HubSpot workflows.
Out of scope by design: retained in the source system.
Jira treats incidents, requests and problems all as issues.
SLA data is not preserved by CSV.
Only current, approved content should move.
This limits volume and risk.
Use the REST API or a migration tool for full-fidelity data.
Paginate, use exponential backoff and honour Retry-After.
Dedupe on email before import and decide how to handle users with no email.
Store the JSM issue key and asset reference as custom ticket 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.
Atlassian API, auth and CSV export are documented. Object mapping into HubSpot rests on category-level knowledge and third-party guides, and I found no HubSpot-side doc or native connector for JSM.
Sources
Related migrations
Frequently asked questions
How do I migrate Jira Service Management to HubSpot?
1. Inventory service desks, request types, queues, organizations and SLAs. 2. Create an admin API token or OAuth app and test the /rest/servicedeskapi/ endpoints. 3. Decide the cut-off date and which closed issues to migrate. 4. Define a JSM-to-HubSpot field map and create custom ticket properties, including the issue key.
What data can move from Jira Service Management to HubSpot?
These objects move directly: Customers (portal users) and Organizations. Check the mapping table for partial and manual items.
What does not move from Jira Service Management to HubSpot?
Request types, queues, SLA configuration and portal fields, Automation rules and workflows and Assets/CMDB and ITAM data. Plan to rebuild or retire these.
How long does a Jira Service Management to HubSpot migration take?
Small (<10k tickets, 1 service desk): 2-4 weeks. Mid (10k-100k tickets, several desks): 4-10 weeks. Large (>100k tickets, Assets integration): 10-20 weeks. These are planning estimates, not a quote.
What access do I need to export from Jira Service Management?
Site URL plus an API token for an admin user, or an OAuth app. Jira/site admin is needed for the full CSV import and export. Migration tools also require an admin user.
What compliance issues apply when moving Jira Service Management data?
Check: Tickets may hold health, financial or minors' data depending on the customer base. and Attachments may contain credentials or sensitive data.. Agree consent, retention and access rules before exporting.
Moving Jira Service Management 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