
Jira Service ManagementServiceNow
Jira Service Management to ServiceNow migration
ITSM specialists move your incident requests, service requests, problems and changes into ServiceNow, check a sample with you first, and count every record on both sides.
Free sample migration of 100 of your records, plus a fixed quote within 24 hours.
Last updated November 2026 · 13 object types mapped
- 1000+migrations
- 15 yearsof collective experience
SOC 2 Type IIGDPR compliantHIPAA compliant
Jira Service Management to ServiceNow at a glance
A Jira Service Management to ServiceNow migration splits Jira work items into incidents, problems, changes and requested items, and turns each comment into additional comments or work notes. Records load through import sets with business rules off, so no old change starts an approval. Jira keeps running until cutover, and a delta pass updates what changed.
- Objects mapped
- 13
- in this route's mapping
- Typical timeline
- About 10 business days end to end
- 3 phases
- Free sample
- 100 records
- checked by your team first
- Quote
- Fixed
- within 24 hours
- Who it is for
- IT teams moving service management from Jira Service Management onto ServiceNow, usually to run incident, change, request and CMDB on one enterprise platform.
- What does not move
- Automation rules, workflows, queues, SLA goals and portal layouts are configuration. We hand over a list of each one in scope for the ServiceNow build.
- What sets the scope
- Work item and comment volume, attachments, the work types and request types in use, the Assets object schemas in scope and the Confluence pages behind the knowledge base.
What moves
What moves from Jira Service Management to ServiceNow
Work items become incidents, problems, changes and requested items, public comments become additional comments, internal comments become work notes, organizations become companies, Assets objects become CIs and Confluence pages become knowledge articles.
- 13 included
| Jira Service Management | maps to | ServiceNow | Status |
|---|---|---|---|
| Organizations | CompaniesOur default mapping; departments are used instead for an internal desk on request. | Included | |
| Customers | Users with no rolesThey raise and follow their own requests without any fulfiller role. | Included | |
| Licensed agents | Users with the itil roleMatched by email, with group memberships set before any record loads. | Included | |
| Teams and assignee groups | GroupsSo the assignment group on old records resolves. | Included | |
| Incident requests | IncidentsPriority loaded as an impact and urgency pair; the Jira key is the coalesce field. | Included | |
| Service requests | Requests and requested itemsNeeds a matching catalog item; form answers land on the requested item. | Included | |
| Sub-tasks of a request | Catalog tasksOnly where the parent becomes a requested item. | Included | |
| Problems and changes | Problems and change requestsYour change model is chosen in ServiceNow before the load. | Included | |
| Public comments | Additional commentsIn original order, with the original author and time written into each entry. | Included | |
| Internal comments | Work notesVisible to ITIL users only, never to the caller. | Included | |
| Attachments | AttachmentsOne file per call against the matching record, read through an agent account. | Included | |
| Assets object types and objects | CMDB classes and CIsLoaded through IRE; references become CI relationships. | Included | |
| Confluence knowledge base pages | Knowledge articlesThe page tree maps to knowledge base categories, with images re-uploaded to each article. | Included |
- OrganizationsCompanies
Our default mapping; departments are used instead for an internal desk on request.
- CustomersUsers with no roles
They raise and follow their own requests without any fulfiller role.
- Licensed agentsUsers with the itil role
Matched by email, with group memberships set before any record loads.
- Teams and assignee groupsGroups
So the assignment group on old records resolves.
- Incident requestsIncidents
Priority loaded as an impact and urgency pair; the Jira key is the coalesce field.
- Service requestsRequests and requested items
Needs a matching catalog item; form answers land on the requested item.
- Sub-tasks of a requestCatalog tasks
Only where the parent becomes a requested item.
- Problems and changesProblems and change requests
Your change model is chosen in ServiceNow before the load.
- Public commentsAdditional comments
In original order, with the original author and time written into each entry.
- Internal commentsWork notes
Visible to ITIL users only, never to the caller.
- AttachmentsAttachments
One file per call against the matching record, read through an agent account.
- Assets object types and objectsCMDB classes and CIs
Loaded through IRE; references become CI relationships.
- Confluence knowledge base pagesKnowledge articles
The page tree maps to knowledge base categories, with images re-uploaded to each article.
Looking for another object?Field-level mapping is reviewed with you during scoping.
What does not move
What does not move from Jira Service Management to ServiceNow as-is
Automation rules, workflow transitions, queues, SLA goals and the portal layout are Jira configuration, so your ServiceNow admin or partner rebuilds them as flows, business rules and SLA definitions.
- ChangelogOn request
- In ServiceNow: Work note summaryServiceNow writes its own audit trail, so Jira field history is summarised in one work note when you want it kept.
- On request
- SLA recordsOn request
- In ServiceNow: Fields on the migrated recordMet or breached, with target and actual times. No live task SLA is created for history.
- On request
- Automation rules, workflow transitions and queuesNot migrated
- In ServiceNow: Flows, business rules and listsConfiguration, rebuilt by your ServiceNow admin or partner from the list we hand over.
- Not migrated
- SLA goals and calendarsNot migrated
- In ServiceNow: SLA definitions and schedulesCreated in ServiceNow. Closed records carry their Jira outcome as fields instead.
- Not migrated
- Confluence space permissionsNot migrated
- In ServiceNow: Knowledge base user criteriaJira Service Management inherits knowledge base view permissions from Confluence, so they are listed and set again.
- Not migrated
- Opsgenie alerts and on-call schedulesNot migrated
- Atlassian keeps Opsgenie-powered features outside the Jira Cloud backup; they are rebuilt in ServiceNow if needed.
- Not migrated
Free sample migration of 100 of your records. Fixed quote within 24 hours.
Scope my migrationTimeline
Jira Service Management to ServiceNow migration timeline
Estimated total
About 10 business days
end to end
- MigrateXwe run it
- Youyour team acts
- Bothon a call together
Preparation
Day 1-2
Scoping call
Both0.5 dayWe agree which service spaces, work types, Assets schemas and Confluence spaces move, and which request types become catalog items or incident categories.
Access on both sides
You0.5 dayYou give us a Jira agent account with access to every space in scope, and a ServiceNow integration user with import set and attachment rights on a sub-production instance first.
Mapping sign-off
Both1 dayWork types to tables, statuses to states, priorities to impact and urgency pairs, teams to groups, request types to catalog items and object types to CMDB classes.
Migration
Day 3-7
Free sample
MigrateX1 day100 of your records, picked for internal comments, attachments, changes and service requests, loaded into the sub-production instance end to end.
You review the sample
You1 dayYour team checks work notes as a caller, created dates, calculated priority, and that no approval or email started.
Full load into production
MigrateX2-3 daysCompanies, users and groups first, then CIs, then incidents, problems, changes and requested items with their journals and files, then knowledge.
Delta pass
MigrateX0.5 dayWork items changed in Jira since the full load are coalesced on their Jira key, so nothing is inserted twice.
Validation
Day 8-10
Reconciliation report
MigrateX1 dayWork items against records per table, state and year, comments against journal entries, attachments against files and objects against CIs.
Sign-off
You1-2 daysYour process owners spot-check a random sample, open items go live with business rules on, and Jira stays read-only until you agree.
An estimate. Record volume, API rate limits and how fast your team reviews the sample all move it.
Known risks
Every known risk on this route, with how we handle it
- 3 solved
- 4 handled
- 01SolvedMost critical
Old changes and requests can start approvals in ServiceNow
The problem
With the transform map's Run business rules box ticked, every imported record runs business rules, workflows, approval engines, auditing and field normalization. Years of closed Jira changes and service requests can start approvals and send emails as they land.
How we handle it
Historical records load with Run business rules cleared, which runs setWorkflow(false). Only the items still open at cutover go through with business rules on, and the free sample proves no approval or email starts.
Source: ServiceNow documentation, checked 15 Nov 2026
- 02HandledMost critical
Created dates are stamped with the load time unless the load says otherwise
The problem
ServiceNow sets sys_created_on, sys_created_by, sys_updated_on, sys_updated_by and sys_mod_count itself on every insert. Without autoSysFields(false) in the load, each migrated Jira work item shows the migration day as its created date.
How we handle it
The load scripts call autoSysFields(false), so the Jira created and updated times and authors are kept on the record. Whether opened_at can be written directly on your instance is proven on the free sample before the full load.
Source: ServiceNow documentation, checked 15 Nov 2026
- 03Solved
A re-run without a coalesce field inserts everything twice
The problem
ServiceNow coalesce updates a target record when the key matches and inserts one when it does not. With no coalesce field defined, every imported row is treated as new, so each delta pass duplicates the records already loaded.
How we handle it
The Jira work item key is stored on every ServiceNow record and set as the coalesce field on each transform map. The delta pass at cutover then updates what changed and inserts only what is new.
Source: ServiceNow documentation, checked 15 Nov 2026
- 04Handled
A Jira priority needs an impact and urgency pair
The problem
On a ServiceNow incident the Priority field is read-only by default and comes from Impact and Urgency through priority lookup rules. A Jira priority such as Highest has nowhere to go until it is expressed as that pair.
How we handle it
We agree one impact and urgency pair per Jira priority that produces the same ServiceNow priority under your lookup rules. The original Jira priority is kept in a field for old reports.
Source: ServiceNow documentation, checked 15 Nov 2026
- 05Handled
Service request types need catalog items before the load
The problem
In ServiceNow a request is an sc_request with one sc_req_item per catalog item, catalog variables exist only on the requested item, and ServiceNow warns against creating these tables through record producers. A Jira request type with form fields has no catalog item to point at until one is built.
How we handle it
Request types that carry form fields are matched to catalog items your ServiceNow owner builds first; the field answers land on the requested item. Request types with no fields can become incidents with a category instead.
Source: ServiceNow documentation, checked 15 Nov 2026
- 06Solved
A customer-level export account misses internal files
The problem
Jira Service Management lists only public attachments on a request when the caller is a customer. An export run under a customer account loses every file attached to an internal comment.
How we handle it
The export runs as an agent with access to every service space in scope, and attachment counts per request are checked against Jira before the load.
Source: Atlassian developer documentation, checked 15 Nov 2026
- 07Handled
Assets has to be exported on its own
The problem
Atlassian leaves Assets out of the Jira Cloud backup. Assets objects export per object type to CSV, and the data-consistent format keeps references as object keys and users as account IDs, which have to be mapped before ServiceNow can use them.
How we handle it
Each object type in scope is exported, mapped to a CMDB class with you, and loaded through ServiceNow's Identification and Reconciliation Engine so the same CI is not created twice. References become CI relationships once both ends exist.
Source: Atlassian Support, checked 15 Nov 2026
Technical profile
What makes this route technical
Jira paces the export through its enhanced search and burst limits, and ServiceNow decides through each transform map whether business rules, approvals and auditing run on the records it imports.
- Exporting from Jira: the enhanced search pages by token
- Jira Cloud's enhanced JQL search at /rest/api/3/search/jql pages with nextPageToken and returns 50 results a page by default, or up to 5,000 work items a page when only the id or key is requested.
Source: Atlassian developer documentation, checked 15 Nov 2026
- Exporting from Jira: the older search endpoints are going away
- Atlassian marks the older GET and POST /rest/api/3/search endpoints as being removed. Its enhanced search may not show the latest writes at once, and the reconcileIssues parameter gives read-after-write consistency for a final delta read.
Source: Atlassian developer documentation, checked 15 Nov 2026
- Exporting from Jira: one comment list, two visibilities
- Jira Service Management's Get request comments endpoint returns public and internal comments together, 50 to a page by default, and includes internal ones unless internal is set to false.
Source: Atlassian developer documentation, checked 15 Nov 2026
- Exporting from Jira: burst limits per endpoint
- By default Jira Cloud allows 100 requests a second per endpoint for GET and POST and 50 for PUT and DELETE, and answers HTTP 429 with a Retry-After header when a limit is exceeded.
Source: Atlassian developer documentation, checked 15 Nov 2026
- Why a Jira Cloud backup cannot carry the move
- A Jira Cloud backup that includes attachments can be taken only once every 48 hours, and Atlassian recommends keeping an export within 25 GB in total, so a backup is a snapshot, not a way to run a delta pass.
Source: Atlassian Support, checked 15 Nov 2026
- Importing into ServiceNow: one row or many per call
- ServiceNow's Import Set API transforms a single row synchronously at /now/import/{stagingTableName}. The insertMultiple variant takes many rows a call, transforms them asynchronously by default, and can chain import sets with run_after.
Source: ServiceNow documentation, checked 15 Nov 2026
- Importing into ServiceNow: two journal fields on every task
- Every ServiceNow task carries Additional comments, the journal the caller can see, and Work notes, which only ITIL users can view.
Source: ServiceNow documentation, checked 15 Nov 2026
- Importing into ServiceNow: one file per Attachment API call
- ServiceNow's Attachment API takes a single file in each request, and the com.glide.attachment.max_size property caps each file at 1024 MB unless your admin has changed it.
Source: ServiceNow documentation, checked 15 Nov 2026
Facts checked 15 Nov 2026 against Atlassian and ServiceNow documentation. Each fact links its source.
Jira Service Management to ServiceNow questions
Still unsure? Ask the engineer who would run this migration, not a sales rep.
Can we move from Jira Service Management to ServiceNow and keep the original created dates?
Yes. ServiceNow stamps sys_created_on and the other system fields itself unless the load turns that off with autoSysFields(false), which our load scripts do, so each record keeps its Jira created and updated times and authors. Whether opened_at can be written directly on your instance is checked on the free sample.
Will Jira internal comments arrive as work notes, hidden from callers?
Yes. Each Jira comment marked internal becomes a work note, which ServiceNow shows only to ITIL users, and each public comment becomes an additional comment the caller can see. The export reads internal comments by default and runs as an agent, so files on internal comments come across with them.
How do Jira request types become ServiceNow catalog items?
By agreement, request type by request type. A request type with form fields becomes a catalog item your ServiceNow owner builds, and its answers land on the requested item, where ServiceNow keeps catalog variables. A request type with no fields can become an incident category instead, which needs no catalog item.
Will importing old changes start approvals or send emails in ServiceNow?
No, because historical records load with the transform map's Run business rules box cleared. That box controls business rules, workflows, approval engines and auditing, so closed Jira changes arrive without starting anything. Only items still open at cutover load with business rules on, and the sample proves no email goes out.
How is the Jira priority mapped when ServiceNow calculates priority?
Through an impact and urgency pair. ServiceNow sets incident priority from Impact and Urgency with lookup rules and keeps the Priority field read-only by default, so each Jira priority is given the pair that produces the same result under your rules. The original Jira priority stays in a field for reporting.
Do Jira Assets object schemas move into the ServiceNow CMDB with their relationships?
Yes, object type by object type. Assets is not part of a Jira Cloud backup, so each type is exported on its own, mapped to a CMDB class with you and loaded through ServiceNow's Identification and Reconciliation Engine to avoid duplicate CIs. References become CI relationships once both ends are loaded.
Does the Confluence knowledge base move into ServiceNow Knowledge?
Yes. A Jira knowledge base can draw on several Confluence spaces, folders and pages, so we list every source first, then load each page as a knowledge article with its images. View permissions come from Confluence, not Jira, so they are listed for your admin to set again in ServiceNow.
Can the move be re-run for a delta without creating duplicates?
Yes. Every ServiceNow record stores its Jira work item key, and that key is the coalesce field on each transform map. A delta pass then updates the records that changed and inserts only new ones. Without a coalesce field, ServiceNow would treat every row as new and duplicate the whole load.
Do we need a Jira admin account for the export?
An agent account with access to every service space in scope is what matters. Jira Service Management shows a customer only the public attachments on a request, so a customer-level account would miss internal files. Admin rights help with Assets and workflow reads, which we confirm on the scoping call.
What does a Jira Service Management to ServiceNow migration cost?
The price is driven by work item volume with its comments and attachments, the work types and request types to map, the Assets schemas and the Confluence pages in scope. We start with a free sample migration of 100 of your records, and the fixed quote reaches you within 24 hours.
How it compares
Four ways to run Jira Service Management to ServiceNow
The same data, moved four different ways. This is what changes between them.
Object coverage (incidents, problems, changes, requests, KB)
MigrateX
Every object in the mapping on this page, plus the ones you ask for during scoping.
Automated migration software
Tickets and contacts are covered. Problems, changes and request items often are not.
Vendor CSV import
One object per file, and only the fields the export template exposes.
In-house scripts
Whatever you have time to build before the cutover date.
Work notes vs comments fidelity
MigrateX
Each entry is posted separately, private stays private, public stays public.
Automated migration software
Threads usually arrive, but per-entry author and visibility can be flattened.
Vendor CSV import
Notes collapse into one field on the ticket, if they come across at all.
In-house scripts
Possible, but it is the part teams most often run out of time for.
Attachments
MigrateX
Uploaded against the right note, and re-hosted with a link when they exceed the ServiceNow cap.
Automated migration software
Supported up to the destination cap. Oversize files are skipped.
Vendor CSV import
Not carried by a CSV import.
In-house scripts
Needs its own download, retry and upload pipeline.
Original IDs cross-referenced
MigrateX
Every source id is stored on the destination record and handed back as a map.
Automated migration software
Often kept as a tag or a single text field.
Vendor CSV import
Lost once the file is imported.
In-house scripts
Only if you design the mapping table up front.
Delta sync before cutover
MigrateX
Included. Anything created or changed during the bulk pass is synced at cutover.
Automated migration software
Usually a paid upgrade on the top tier.
Vendor CSV import
You would re-export and re-import by hand.
In-house scripts
Requires change tracking and idempotent writes on both sides.
Rate-limit handling
MigrateX
Paced to your plan limits, honours Retry-After, and resumes from a checkpoint.
Automated migration software
Backs off, but a long run can still stall and leave partial records.
Vendor CSV import
Not applicable, and the file size limits bite instead.
In-house scripts
The most common reason a home-grown run dies overnight.
Validation report
MigrateX
Counts per object and per status on both sides, with every default and placeholder listed.
Automated migration software
A run log and an error list, rather than a reconciliation.
Vendor CSV import
Row counts in a spreadsheet.
In-house scripts
You write the reconciliation queries yourself.
Rollback plan
MigrateX
Every write is tagged, so a batch can be reversed without touching your own records.
Automated migration software
Some approaches can clear a migration, some cannot.
Vendor CSV import
Manual cleanup of everything the import created.
In-house scripts
Only if you built the tagging in from the start.
Who does the work
MigrateX
A MigrateX engineer runs it and stays on the cutover call.
Automated migration software
You run the software. Support answers tickets.
Vendor CSV import
Your admins, one file at a time.
In-house scripts
Your engineers, instead of your roadmap.
Guides
Guides for a Jira Service Management to ServiceNow migration
Related routes
Other routes we run
Built for your security review, from the first call.
Read how we handle your data
SOC 2 Type II
Independently audited controls over how we handle your data.
GDPR compliant
Data processing agreement available.
HIPAA compliant
Business associate agreement available.

Start your ServiceNow move with 100 of your records.
Scope my migrationFree sample migration of 100 of your records, plus a fixed quote within 24 hours.











