Best way to archive Service Desk projects when deactivating Jira Service Desk cloud?

[Tamara]

We're planning to deactivate Jira Service Desk cloud. We've got Jira Software cloud, which we're keeping. We have three classic Service Desk projects we'd like to archive for future reference. What's the best way to archive them?

I'm thinking:

1. Take a CSV export of the issues in each of the projects (doesn't save attachments, so this is more of a 'just in case' backup).

2. Create projects in Jira Software (which we're keeping) to move the issues to. Give those projects a read-only permission scheme.

Is this the way to go, or is there a better plan?

Final question: what happens to fields relating to Jira Service Desk when it's deactivated? The moved issues in the Software projects will still have fields like 'Request participants' which are typically only seen in Service Desk projects. Will those fields be preserved when Jira Service Desk is deactivated?

[Nic Brough -Adaptavist- · Accepted solution]

You could just give those three projects a read-only permission scheme, no need to move anything around.

If you remove JSD, the fields it used remain in the data, in case you decide to go back.  But you won't be able to get to them.

[Tamara]

Thanks Nic. We may want to refer back to the data at some point, which is my reason for moving the SD issues to Jira Software.

[Graham Brenna]

@Nic Brough -Adaptavist- I'm in the same situation. I want to be able to continue to open the specific issues from the Jira Service Desk Project without moving them. When we remove our JSD license, what will happen to the Project? If I'm understanding correctly, I'll still be able to "read" the issues, just not edit them. 

[Nic Brough -Adaptavist-]

The project will revert to a plain Jira Core project.  You'll have all the issues and be able to work with them, but all the request layer will disappear.

[Tamara]

Thanks for clearing that up, @Nic Brough -Adaptavist- .

I read the following and assumed the Service Desk projects would be deleted. That's why I was so concerned about moving the issues to different projects.

Once your site has been deactivated (i.e. your site has been taken offline), you have two weeks to pay your outstanding quote or contact Atlassian to have the site restored before your data will be permanently deleted.

https://confluence.atlassian.com/cloud/cancel-your-site-subscription-873871347.html

[Nic Brough -Adaptavist-]

That's about deactivating an entire site, not removing one component.