Hi Altassian Community,
I'm researching options to migrate a JSM project from one cloud instance to another cloud instance and could really use your support.
There is plenty information about Jira Software cloud to cloud migrations but not about JSM.
The situation:
Its essential for us to be able to move customers and their affiliated organisations.
I've looked into the following:
I'm not very experienced with CSV import and exports so I'm a little bit reluctant there.
The cloning seemed to work fine but the issue is with the reporters (customers and their organizations)
Is there anyone who has been in this situation and found a good workaround?
Perhaps using automation to comment the reporters and the emailadress to the comments or a custom field or something like that...
Some marketplace app I've looked over?
I'd love to hear your experience and or suggestion for this particular case.
If there is any additional information to required, please do not hesitate to ask!
Thanks in advance & kind regards,
Thijs
I'm a Cloud Migration specialist and let me tell you: you have found yourself in a tricky situation. The reason why you hear so much about Jira Software cloud-to-cloud migration and nothing about JSM is due to the fact that JSM cloud-to-cloud migrations are not possible at the given moment!
Check this out: What migrates in a cloud-to-cloud migration for Jira
Depending on how complex your project configuration is, you might not want to do the migration via CSV export-import, as it migrates just ticket data and no project data.
Deep clone is doing a bit more but from experience is slow and has limitations. You will still have to configure the project by hand.
Another option is to import your project into a new Jira Data Center instance and then use the Jira Cloud Migration Assistant to migrate your JSM project to the target Cloud instance. I know it sounds banana, but it's an official solution written down here. It also comes with challenges and you might want to consider asking for help from an Atlassian Solution Partner in your region.
If it's just one project, the easiest way might be to simply bite the bullet and go through a manual process of creating and configuring the project, importing tickets with CSV, and tidying up after it.
Hi @Dawid Joshua _TechTime_, hi @Thijs Van Baelen,
I am Marlene from codefortynine.
We released an update for Deep Clone for Jira that alleviates the duration problem, when bulk cloning a large amount of issues.
It is now possible to run Bulk Clone jobs in the background. Which means that you can suspend the clone dialog or shut down your computer, even if the clone is not finished.
In the Clone History you can monitor, pause or cancel the clone job at any time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you kindly for your clear reply and confirmation of the tricky situation!
I guess we'll have to bite the bullet and do the tidying manually.
I was wondering if you had any good tips & tricks from your experience as Cloud Migration Specialist that might come in handy when migrating JSM projects?
Kind regards,
Thijs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Thijs Van Baelen ,
We usually make use of the more complex migration option by exporting to Data Center and then migrating to another Cloud instance. So I don't have much experience in doing it manually. I'd give Deep Clone a go, as well as create a Ticket with Atlassian for your migration. When you test your migration, you might want to use either a Sandbox (part of the Premium Subscription) or a test instance. If you don't want to recreate all configurations by hand, you might want to have a look at Project configurator for Cloud (yes, it exists... sort of). Have a look here. It does not work at the moment, at least for me, but you might want to message Adaptavist and ask for help (they have great support from my past experience).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.