nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Converting JSM to JSW ready for Migration

Dani Miles

Hi there,

This is a strange case but our customer has decided to convert 12 JSM projects to JSW to avoid paying for the agent licenses when they migrate to Cloud.

I am assuming it will be best to change the projects from JSM to JSW in situ on Server and then migrate to Cloud so I was intending to build new JSW projects with shared config and then move the issues into them. Anyone had any experience with this? Any recommendations? Is this the right approach or would there be any benefit to a different approach?

I understand I will lose, Request Types, SLA's, Organisations, Queues... but is there anything else I need to worry about losing? Some of the projects are linked to a slack channel.

I am guessing I can replace most queue queries with boards. The projects I am switching are not customer facing at the moment anyway and the companies internal users basically just need to be trained on new ways of use.

Some projects have 10's of thousands of issues, how can the move best be managed when there are say 50k issues? This won't be able to be done through Bulk Move so would I need to do an Export/Import? Are there any risks using that method?

Appreciate any shared experiences of this.

Thanks,
Danielle

Accepted answers

Dani Miles

Steps I eventually took:-

Check if SLA's, Internal/External commenting, Organizations, Request Types, Request Participants and anything else specific to JSM were being used to any extent within the project.
Speak with users about the changes that were intended and new methods of working.
Demonstrate how they can use boards rather than queues
Convert Project to Jira Software in DC
Migrate the project using JCMA as Software to Cloud.

As this was a business decision to move away from JSM the teams were told they had to get used to the new way of working. This could have been a lot more problematic if teams were relying on SLA's or a customer portal etc.

All comments

Brant Schroeder

@Dani Miles You really only have three options.

1. Export then import the project
2. Move the issues
3. Us an app from marketplace that copies the project or clones issues
4. Write a script that uses the APIs to move issues for you

Moving them like you are suggesting will take forever if you have that many issues. I would suggest an app from the marketplace. The app has a 30 day free trail so you can try it out before purchasing it to make sure it works. https://marketplace.atlassian.com/search?hosting=server&product=jira&query=clone%20project

Brant Schroeder

@Dani Miles Please accept the answer to help others if this was helpful.

Dani Miles

Steps I eventually took:-

Check if SLA's, Internal/External commenting, Organizations, Request Types, Request Participants and anything else specific to JSM were being used to any extent within the project.
Speak with users about the changes that were intended and new methods of working.
Demonstrate how they can use boards rather than queues
Convert Project to Jira Software in DC
Migrate the project using JCMA as Software to Cloud.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

migration

jira-software

jira-service-management

jira-service-management-server