Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira migration

nikki
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 6, 2026

Hello,

We would like to move away from the current customer structure and migrate from Jira ITSM to Jira Software. Is this recommended and Is anyone aware of successful cases where the migration went smoothly?
In my test environment, I notice that tickets are not migrating correctly because certain fields do not exist in Jira Software and are therefore not transferred properly.

4 answers

0 votes
nikki
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 8, 2026
We are currently using Jira ITSM with a service desk where employees can submit requests. However, this setup is used exclusively for internal purposes; we do not have any external customers.

Therefore, we want to provide our internal employees with regular Jira licenses and move to Jira Software. One of the reasons for this decision is also cost-related.

The IT Service Desk template we are currently using is specific to Jira Service Management and is not available in Jira Software. As a result, we need to recreate the existing service desk functionality within Jira Software in a different way.

Given this context, is it possible to migrate the existing tickets from Jira ITSM to Jira Software, or at least create an export (for example, a CSV) of the current tickets so we can retain the historical data?
0 votes
Marc -Devoteam-
Community Champion
January 6, 2026

Hi @nikki 

JSM projects and Jira projects are based on a different structure.

JSM uses specific fields related to its projects that indeed don't exist in Jira.

So as my other community members ( @Jack Brickey / @Dave Mathijs ) are referring to what is your use case?

Marc -Devoteam-
Community Champion
January 8, 2026

Hi @nikki 

Yes you can.

You could search for all the tickets and then do a bulk update and move the issues to the new Jira space.

Or you can export them and import them via csv, but as you are just creating a new project the bulk move option would be the most logical

0 votes
Jack Brickey
Community Champion
January 6, 2026

Hi @nikki , when you say you want to migrate, what exactly do you mean? Are you wanting to retain the data that exists in some of your JSM spaces a.k.a. projects? If so, you can export the data to CSV and import it into your new Jira projects. Of course @Dave Mathijs a has raised import questions that should be considered before switching horses.

0 votes
Dave Mathijs
Community Champion
January 6, 2026

Hi @nikki 

Could you please elaborate on the WHY of this idea/decision?

What are the reasons or what is the rationale for the switch from Jira Service Management to Jira?

What are you tracking? Requirements, development or customer support?

Although both Jira Service Management and Jira belong to the Jira platform, their capabilities/features differ quite extensively, and thus it's not a lightweight decision to move your "work items" from one app to another.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events