Is it possible to migrate a JSW project/space without its data?

[Christian Lipski]

I could have sworn that it was possible to choose to migrate the structure of the space without the data, but I'm not seeing any mention of that in my searches.

Does anyone know if this is or was possible? 

My workaround is to create a new space with shared settings, and then re-add roles and other things that don't get shared, but if I don't have to, that would be nice.

[Trudy Claspill · Accepted solution]

Hello @Christian Lipski 

Migrate from where to where; DC to Cloud, Cloud to Cloud, Cloud prod to Cloud sandbox?

Are you willing to acquire a third party app to handle this?

What exactly are you trying to "migrate"? What do you consider project data that shouldn't migration and project data that should migrate?

[Christian Lipski]

Ha ha, hey Trudi. I totally neglected to mention JCMA.

It's DC to Cloud using JCMA. I want to migrate the project without the work items. I seem to recall this was possible with JCMA, and I'm looking for confirmation that it is or isn't. Thanks!

[Trudy Claspill]

In this 2021 post an Atlassian Team Member said that the Migration Support team could enable a "configuration only" migration option. I don't know if that is still available.

Otherwise, to the best of my knowledge, there must be at least one issue in the project for it to migrate via JCMA.

I've been told (but have not done a migration myself recently) that there is an option to exclude Archived issues. If that is still true then you could archive all but one issue to minimize what comes across in JCMA.

https://support.atlassian.com/migration/docs/choose-what-jira-data-to-migrate-using-the-assistant/#Migrate-projects

[Christian Lipski]

Thank you, that's helpful!

[Monika Ambrozowicz_Seibert_]

Hi @Christian Lipski, is it a one-time migration or something you are going to repeat at least a few times, to migrate more spaces and/or boards? Have you considered using templates for that? Because I might have a solution if you're open to marketplace apps, and it makes sense especially if you have more than one space and board to migrate. Full disclaimer: I am affiliated with the team behind the app. 

If so, Templating.app has a pace Templates (Project Templates) feature that might help you. 

The idea is that you capture a project's configuration as a reusable template (including board settings and who gets which roles), and then spin up new projects from that template without any of the existing issue data. Non-admin users can even be given permission to create projects from approved templates, which also removes the usual admin bottleneck.

For your specific situation, you'd essentially create a template from your existing project's configuration once, and then use that template going forward instead of the manual "create new space + re-add roles" workaround you described.

The setup is very intuitive. If your projects are on Jira Cloud, it's free for up to 10 users and worth testing to see if it captures the configuration elements you need. et me know if you have questions - happy to help. 

[Christian Lipski]

https://jira.atlassian.com/browse/MIG-2091

The dark feature is com.atlassian.jira.migration.project.configuration.only, but it might only work in earlier versions of JCMA.