Hey everybody!
We have a setting that Atlassian migration doesn't cover in my opinion, so I hope you can help here.
Currently we are using Jira Server and have some projects to migrate (Service Desk and Software) to Cloud. But: In Cloud there are existing projects already in use.
For this reason, Site Export/Import is not an opinion as we would delete the existing projects.
The only way I see at the moment is the Cloud Migration Tool. We do not like the missing Metadata (like Filters, Reports and so on), but we can come to terms with it. But: Our Server Instance is used by really a lot of users. We can not stop the Jira usage, so there's a strong need to continue working seamlessly in the cloud. For this reason we need to do a lot of end-user testing in the Cloud. So we need to do a realistic Test Migration with a really big set of issues.
As the migration tool does not allow to do updates to a Cloud project, we can not do this test migrations as the Key will not be usable for the final Go-Live. It's not an option to rename the Server Projects as there are a lot of dependencies. So what can we do in this scenario?
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.