The best two tools you can use for this are: Configuration manager and Project configurator.
If you do it manually, you have to consider used apps, workflows, users, statuses, etc, etc. It is a hell of a job. These two apps will take care of most of the problems you can face when migrating projects.
Neither of these are available for Jira Cloud, so they cannot be used.
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.
Are you migrating one instance to another empty/new instance or does the other instance already have data on it?
It also plays a very huge role depending on what deployments we're talking about -- i.e. whether it's Cloud->Cloud, Cloud->Server, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Migrating one instance from to a instance which already different project under it.
Its Cloud > Cloud
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, then snap - if it were an empty instance you could do it in a single backup export/import, but now this complicates things because Cloud does not allow single project imports: https://jira.atlassian.com/browse/JRACLOUD-72570
You can find the article about your options here:
# https://confluence.atlassian.com/jirakb/merge-multiple-instances-of-jira-cloud-779160767.html
So, 3 options then:
- host Jira on your Server and migrate both Cloud instances to it, and then continue hosting Server
- install Jira Server locally as a temporary site, which you would be able to restore your Cloud data on, and then migrate the data to the other Cloud instance (sounds comical, but generally should be the better option if you are looking at many many projects and want to retain data which .csv option does not allow)
- .csv export of issues, and import to the target Cloud instance; .csv of course however has limitations, not all data can be exported; this is generally recommended if you only want to migrate several projects, or if they are not that huge and/or you do not require data which the Server->Cloud option could provide
In any case, do please read the above knowledge article thoroughly to make the decision which path to take - you're potentially looking at hours of work. Regardless of the option you'll take, migrations are not trivial and do take a lot of time and testing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.