nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migrating projects from cloud to cloud

Per Kristian Haakonsen

Hi,

I'm trying to migrate all Jira projects (which happens to be only one project) from one cloud instance to another. The source instance will eventually be deleted.

I have tried, and failed, using the three following approaches:

1. From source instance, create a backup of Jira projects under System -> Import and Export -> Backup manager. From target instance, restore this backup under System -> Import and Export -> Import Jira Cloud. The import completes and reports that it succeeds. However, neither Jira projects nor users are actually created on the target instance. Nothing seems to happen at the target instance at all.

2. Using System -> Import and Export -> Migrate cloud site. When creating a new migration, I am unable to create target site with the error message "There are no other sites within the current organization, or you don't have the right admin access.". I am admin on both source and target site, using the same account. Under admin.atlassian.com, the source site appears under the headline "Organization" and the target site appears under the headline "Products". I don't understand how to go from here.

3. Checking out various migration tools. None seem to support cloud to cloud.

#1 seems like the best and simplest option. Our migration scenario is simple an limited, we only need a single Jira project, that's all.

Because we're only importing one project, we're getting close to simply manually copy/pasting everything into the new instance because it seems faster than trying to figure out how to migrate.

All help is appreciated

Accepted answers

Marlene Kegel - codefortynine

Welcome to the community, @Per Kristian Haakonsen.

I am Marlene from codefortynine.

If you're going forward with creating the project manually, you can use Deep Clone for Jira to bulk clone and move all issues to the new instance.

The process is pretty simple and we provide detailed logs to analyze possible errors and warnings. That helps to make sure that no data gets lost.

All comments

Marlene Kegel - codefortynine

Welcome to the community, @Per Kristian Haakonsen.

I am Marlene from codefortynine.

If you're going forward with creating the project manually, you can use Deep Clone for Jira to bulk clone and move all issues to the new instance.

The process is pretty simple and we provide detailed logs to analyze possible errors and warnings. That helps to make sure that no data gets lost.

Per Kristian Haakonsen

@Marlene Kegel - codefortynine thank you so much for your answer. We have used your proposed tool and successfully migrated projects from one instance to another.

The tool migrates almost all data we needed. The only thing we can see missing is that old sprints aren't migrated, but that's something we can live with. Current sprint is migrated and all completed tasks are migrated (they're just not allocated to a sprint anymore).

Converting the first project took about 2 hours with no prior experience in using this tool, which means the tool is simple and easy to use.

Marlene Kegel - codefortynine

Thank you very much for your positive feedback, @Per Kristian Haakonsen. It is great to hear that Deep Clone for Jira was suitable for your use case and easy to use. I'll share this with the rest of the codefortynine team

Also thank you for your feedback about cloning sprints. Unfortunately, Jira doesn't allow adding issues (in our case cloned issues) to completed sprints.

I've updated our Known Limitations documentation, to make it easier to detect that completed sprints cannot be cloned with Deep Clone for Jira.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

clone