Jira to ServiceNow Migration 2026: Mapping, CMDB and Cutover
Jira to ServiceNow migration in 2026: map JSM fields, move Assets to the CMDB, work within export limits and time cutover to renewal. Plan yours.
Published Updated 13 min read

On this page
- Why teams move from Jira Service Management to ServiceNow in 2026
- What moves, what gets rebuilt, what's at risk
- Jira Service Management to ServiceNow field mapping
- Assets to CMDB: moving CIs and relationships
- Export from Jira Service Management, import into ServiceNow
- What really drives effort and cost in this pair
- The migration plan in phases
- Pair-specific failure points
- Jira to ServiceNow migration checklist
- FAQ
A Jira to ServiceNow migration moves Jira Service Management (JSM) incidents, requests, problems, changes, comments, attachments and Assets objects into ServiceNow tables through import sets, transform maps and the Attachment API. Workflows, automation rules and SLA definitions do not move; you rebuild them. This guide is for JSM owners planning the move in 2026, with new Atlassian prices live and Data Center dates setting the clock. The hard part is keeping comment visibility, CIs and ticket links intact.
Why teams move from Jira Service Management to ServiceNow in 2026
A Jira Service Management to ServiceNow migration starts with a dated Atlassian event or a decision to consolidate.
| Atlassian trigger | Date | Status (Atlassian, 26 Oct 2026) |
|---|---|---|
| Data Center: no new-customer sales | 30 Mar 2026 | Passed |
| New cloud list prices, JSM and Service Collection included | 13 Oct 2026 PT | In effect: Standard $21.50, Premium $55.28 per agent per month |
| Confluence Cloud XML export end of life | 1 Dec 2026 | Five weeks away; CSV export is the alternative |
| Usage-based billing, most meters | 3 Dec 2026 | Covers automation steps, Assets objects, Rovo credits |
| Opsgenie end of support and shutdown | 5 Apr 2027 | Data not moved by then is deleted |
| Data Center: last purchases for existing customers | 30 Mar 2028 | Upcoming |
| Data Center: end of life, read-only | 28 Mar 2029 | Atlassian advises against running read-only online |
JSM knowledge lives in Confluence, so run any XML space archives before 1 Dec 2026. Opsgenie users need a new home for on-call by 5 Apr 2027; ServiceNow lists On-Call Management in ITSM Advanced (ServiceNow pricing page, as of 26 Oct 2026). Our Jira Data Center end of life guide covers each Data Center date.
Consolidation is the second driver: a separate JSM instance means a second CMDB, change calendar and reporting stack. ServiceNow puts Service Catalog, Incident and CMDB in ITSM Foundation, adds Change and Problem in Advanced, and quotes every deal (ServiceNow pricing page, as of 26 Oct 2026). Our ServiceNow migration guide covers other source platforms. Running two ServiceNow instances instead? See ServiceNow instance consolidation.
What moves, what gets rebuilt, what's at risk
A Jira to ServiceNow migration moves data, not behavior.
| Moves (as data) | Gets rebuilt on ServiceNow | At risk if unplanned |
|---|---|---|
| Incidents, requests, problems, changes | Workflows and status transitions | Internal vs public comment visibility |
| Comments with author and timestamp | Request types, as catalog items or record producers | Running SLA timers and elapsed time |
| Attachments | Automation rules, SLA goals and calendars | Files above ServiceNow's size limit |
| Assets objects, as CIs | Queues, dashboards and reports | Ticket-to-CI links |
| Assets references, as CI relationships | Priority matrix, as impact and urgency rules | Assets object history |
| Users, groups, organizations, knowledge | Approvals, notifications, portal, on-call | Knowledge article formatting |
Workflows, automations, business rules, SLA definitions, macros and running SLA timers are rebuilt on the target, not migrated.
Jira Service Management to ServiceNow field mapping
Give each JSM work type a ServiceNow target table first.
| Jira Service Management | ServiceNow target |
|---|---|
| Incident work items | Incident |
| Service request work items | Requested item or record producer task |
| Problem and change work items | Problem and Change Request |
| Request type | Catalog item or record producer |
| Status / Priority | State / Impact and Urgency |
| Internal note / reply to customer | Work notes / additional comments |
| Reporter, assignee, team | Caller, Assigned to, Assignment group |
| Linked work items | Problem, Change Request, Caused by Change |
| Assets object field | Configuration item; Impacted Services/CIs |
Request types, statuses and resolutions
ServiceNow defines a record producer as "a specific type of catalog item that allows end users to create task-based records" (ServiceNow docs, as of 26 Oct 2026). Map request types that raise incidents to record producers and fulfillment types to catalog items, keeping the old name in a field.
Every Jira status sits in one of three categories: To do, In progress or Done. ServiceNow incidents use six states: New, In Progress, On Hold, Resolved, Closed and Canceled (Atlassian and ServiceNow docs, as of 26 Oct 2026). Map each status by name, not category, and route Done, Won't do and Duplicate resolutions to Closed or Canceled on purpose.
Priority: impact and urgency
ServiceNow derives priority from impact and urgency, and the field is read-only by default (ServiceNow docs, as of 26 Oct 2026). Map each of Jira's five default priorities to an impact and urgency pair and test it against your lookup rules.
Comments: internal notes to work notes
The JSM Cloud REST API gives every comment a "public" property, false for internal notes; on Data Center, internal comments carry {"internal":true} in a comment property (Atlassian docs, as of 26 Oct 2026). In ServiceNow, every user who can view an incident sees additional comments (ServiceNow docs, as of 26 Oct 2026). Read the flag on every comment and write it to the matching journal field.
Users, attachments and links
Map JSM organizations to companies or groups, and load users and groups before tickets: if a referenced sys_id does not exist, it "could potentially appear in the target record as the DisplayValue" (ServiceNow docs, as of 26 Oct 2026).
Jira Cloud allows files up to 2 GB, while ServiceNow's attachment limit is 1,024 MB by default (vendor docs, as of 26 Oct 2026), so list larger files during discovery. Jira links become the incident's Problem, Change Request and Caused by Change fields, so load problems and changes first.
SLA history
JSM shows remaining SLA time by default; Atlassian's workaround copies elapsed time into exportable fields with automation (Atlassian knowledge base, as of 26 Oct 2026). ServiceNow's SLA repair "removes the SLA record, then recreates and recalculates it from the start", using only the final state of dot-walked fields (ServiceNow docs, as of 26 Oct 2026). Store closed-ticket SLA outcomes as data and test repair on imported records.
Assets to CMDB: moving CIs and relationships
Object types become CI classes, objects become CIs and references become relationship rows (vendor docs, as of 26 Oct 2026). Our ServiceNow CMDB guide explains the target model.
- Export each object type in "data consistent" format, which stores references as keys, users as account IDs and dates as Unix timestamps.
- Map object types to CMDB classes. Pick the most specific class: a laptop class extends computer, which extends the base CI class.
- Load CIs through the Identification and Reconciliation Engine (IRE), which ServiceNow says "prevents duplicate CIs" and can match on source_native_key. Use the Assets key as that key.
- Rebuild references as relationships. Each Assets reference becomes a cmdb_rel_ci row with a parent CI, child CI and relationship type.
- Relink tickets to CIs. The Configuration item field takes the main CI; the Impacted Services/CIs list links any task to many CIs. Affected CIs on change requests can be added only in the New state, so test loads on closed changes.
On Data Center, object schema exports leave out object history and connected Jira tickets. Atlassian's Cloud Migration Assistant keeps history, but only into Atlassian Cloud, and its doc requires JSM Premium or Enterprise for Assets (Atlassian docs, as of 26 Oct 2026). If auditors need CI history, archive it before the source goes read-only.
Export from Jira Service Management, import into ServiceNow
Atlassian has no tool for this direction: its Cloud Migration Assistant is for "migrations from Server or Data Center to Cloud" (Atlassian docs, as of 26 Oct 2026). You read JSM through exports and REST APIs and write through ServiceNow import sets.
| Side | Mechanism | Documented limit or behavior (vendor docs, checked 26 Oct 2026) |
|---|---|---|
| Jira Cloud | CSV export | 10,000 work items per export; split by JQL |
| Jira Cloud | REST API | Since 2 Mar 2026, apps share a 65,000-point hourly pool; API-token traffic keeps burst limits; HTTP 429 with Retry-After |
| Jira Data Center | Filter export | 1,000 issues by default |
| Jira Cloud | Site backup | 25 GB recommended; excludes Assets and automation flows |
| ServiceNow | Table API | sysparm_limit default 10,000; paginate with sysparm_offset |
| ServiceNow | Import Set API | Staging table, then transform map; insertMultiple asynchronous by default |
| ServiceNow | Attachment API | One file per request |
| ServiceNow | Knowledge import | Word files; heading numbers, table borders and custom heading styles lost |
Set a coalesce field on the Jira key in every transform map. A match is updated and no match creates a record, but if several records match, only the first is updated (ServiceNow docs, as of 26 Oct 2026). Reruns and delta loads stay safe only while the key is unique.
What really drives effort and cost in this pair
No neutral public price exists for this migration. These drivers set the effort.
- Files, not tickets. The Attachment API moves one file per request, so file count sets the load window.
- Export caps and rate limits. Atlassian warns that Data Center exports above 1,000 issues "may result in an OutOfMemoryException" (as of 26 Oct 2026). On Cloud, an app-based extractor shares the points pool; an API-token script does not.
- Configuration, not migration. Every request type, automation rule and SLA goal is rebuilt. Give it its own owner.
- CMDB depth. Assets object types and reference types set the class-mapping work.
- History scope. Decide between full history, active work only, or archiving the past and migrating only what you need. Our guide to migrating ticket history covers the trade-offs.
- Licensing overlap and usage billing. Annual customers get a renewal quote 90 days before expiry. From 3 Dec 2026, usage above plan allowances is billed; Assets objects above the allowance (5,000 on Standard) cost $0.02 each per month. Atlassian's usage page says extra usage is on by default; its FAQ says it requires opt-in (Atlassian, as of 26 Oct 2026), so check the setting before a parallel run.
On day one, agents stop setting priority directly, Jira keys give way to ServiceNow numbers (keep the old key searchable), and requesters meet catalog items.
The migration plan in phases
1. Discover
Count work items, comments, attachments and Assets objects per project. Agree history scope with audit owners and note your renewal date.
2. Map
Turn the tables above into a signed mapping document: table, state, priority, comment visibility, organization and CMDB class.
3. Test migration
Load a full copy into sub-production and open records of every work type by hand. A ServiceNow support article and a ServiceNow employee's Community post say import set data older than seven days is deleted (as of 26 Oct 2026), so review loads promptly. Our test migration checklist lists what to check.
4. Cutover with delta sync
Run the bulk load before the freeze window. At cutover, load only work items updated since then through the same coalescing transform maps, then hold the go/no-go.
5. Reconcile
Compare counts per table and state, comments by visibility, attachments and CI relationships. Table API reads with sysparm_display_value=all expose references stored as text.
6. Hypercare
Keep JSM read-only, fix gaps with targeted reruns, and time the JSM shutdown against your renewal.
Pair-specific failure points
- Internal notes go public when every comment lands in additional comments.
- Priority changes on load because ServiceNow derives it from impact and urgency.
- References stored as text when users or groups load after tickets.
- Duplicates after a rerun when the coalesce key is not unique.
- Large files missing above ServiceNow's attachment limit.
- CIs without history because Data Center schema exports leave it out.
- Extraction stalls when a Cloud extractor ignores Retry-After on HTTP 429.
- Closed changes without affected CIs past the New state.
Jira to ServiceNow migration checklist
- Confirm your Atlassian dates, renewal quote window and extra usage setting.
- Archive Confluence knowledge spaces you need as XML before 1 Dec 2026.
- Agree the history scope and where the archive lives.
- Count work items, comments, attachments and Assets objects, and list files above ServiceNow's size limit.
- Map work types to tables and request types to catalog items or record producers.
- Map statuses, resolutions and priorities to states and impact and urgency pairs.
- Map internal notes to work notes, public replies to additional comments.
- Load users, groups and companies before tickets.
- Load Assets through IRE and rebuild references in cmdb_rel_ci.
- Set a unique coalesce key on every transform map.
- Run and reconcile a full test migration before booking the freeze window.
- Run the delta sync, reconcile again and hold the go/no-go.
Facts checked October 26, 2026 from Atlassian pricing, Atlassian Data Center end of life, Atlassian knowledge base, ServiceNow SLA repair docs and ServiceNow Table API. No vendor paid for this article. How we research
FAQ
How long does it take to migrate Jira to ServiceNow?
There is no neutral public benchmark for this pair. Duration depends on history scope, the volume of work items, comments and attachments, Assets depth, the request types you rebuild and the number of test migrations. File count often matters more than ticket count, because ServiceNow's Attachment API takes one file per request. Size it after discovery.
Does Atlassian's 2026 pricing change affect migration timing?
It can. New list prices have applied to renewals and monthly bills since 13 Oct 2026, and usage billing for automation steps, Assets objects and Rovo credits starts on 3 Dec 2026 (Atlassian, as of 26 Oct 2026). If your renewal falls mid-project, price a short term against the cutover date before you sign, and check whether extra usage is switched on.
Can I migrate Jira Assets to the ServiceNow CMDB?
Yes, as data. Export each object type in data consistent format, which keeps references as keys (Atlassian docs, as of 26 Oct 2026). Load objects as CIs through IRE, then rebuild references as cmdb_rel_ci rows. Data Center schema exports leave out object history, so archive it if auditors need it.
Do internal comments stay internal after the migration?
Only if you map them that way. The JSM Cloud API marks each comment public or internal. In ServiceNow, all users who can view incidents see additional comments, so internal notes must go to work notes (ServiceNow docs, as of 26 Oct 2026). Test visibility while logged in as a caller.
Does SLA history move from Jira Service Management to ServiceNow?
Running SLA timers and SLA goals do not move; you rebuild SLA definitions in ServiceNow. Atlassian documents an automation workaround that captures elapsed time in exportable fields (Atlassian knowledge base, as of 26 Oct 2026). Store closed-ticket SLA outcomes as data so reports keep their history.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


