Hi everyone, I need some guidance regarding moving issues between Jira projects one project to another. We currently have Project X, which is a Kanban project, and it contains a large number of existing issues. We have now created a new Scrum project (Project Y), and we would like to move all the issues from Project X to Project Y. Could anyone please let me know: * What is the recommended way to move all issues from one project to another? * Is it possible to move multiple issues in bulk while preserving issue history, comments, attachments, and links? * Are there any prerequisites or limitations that I should be aware of before performing the move? Thank you for your support. Thank you! Dvipa

Below are the steps to do this, hope it helps! Steps * Go to Filters > Search work items * Search for all issues in Project X: project = X * Click 3 dots (•••) in the top right corner > click Bulk Change * Select all issues and click Next * Choose Move Issues and click Next * Select Project Y as the destination project * Map any required fields, issue types, or statuses if prompted * Review the summary and click Confirm (make sure you give it a good review).

Hi @kshridvipa7878 As an alternative I can suggest trying our app Elements Copy & Sync. The native bulk move can work, but it has limits on very large volumes and doesn't give you much control over field mapping between a Kanban and a Scrum scheme. Elements Copy & Sync lets you move a full hierarchy of Jira issues from Project X to Project Y (with all the fields, comments, attachments and links needed), and you can reuse the same recipe as many times as you like, on any batch of issues. The steps are the following: * Create a "Copy and Synchronize work items" recipe * In the Source tab, define your source project (Project X) select "Copy full hierarchy" (this brings along child issues/subtasks) * Define Project Y (your new Scrum project) as the target * Map your fields once, including how backlog items should land (since Kanban has no sprints, you decide where they go in the Scrum backlog) * Go to the issue search bar, filter on Project X, and select your recipe to run the copy in bulk This way you keep full control over the mapping and can run it in batches rather than relying on one large bulk-move operation. Don't hesitate to try the app, it's free for 30 days (and stays free under 10 users).

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; } } }

How to Move All Issues from a Kanban Project to a Scrum Project in Jira?

kshridvipa7878

Hi everyone,

I need some guidance regarding moving issues between Jira projects one project to another.

We currently have Project X, which is a Kanban project, and it contains a large number of existing issues.

We have now created a new Scrum project (Project Y), and we would like to move all the issues from Project X to Project Y.

Could anyone please let me know:

What is the recommended way to move all issues from one project to another?
Is it possible to move multiple issues in bulk while preserving issue history, comments, attachments, and links?
Are there any prerequisites or limitations that I should be aware of before performing the move?

Thank you for your support.

Thank you!

Dvipa

Accepted answers

Ignacio Vera

hi @kshridvipa7878

just seach in issue navigator project = X and the make a bulk change --> move work items

and move them to the new project. Once in the new board you can drag an drop them in the scrum sprint or backlog

Viswanathan Ramachandran

to echo Ignacio, first move all the issues from X to Y. Then create a new scrum board from the Y project.

Jason Krewson

Below are the steps to do this, hope it helps!

Steps

Go to Filters > Search work items
Search for all issues in Project X: project = X
Click 3 dots (•••) in the top right corner > click Bulk Change
Select all issues and click Next
Choose Move Issues and click Next
Select Project Y as the destination project
Map any required fields, issue types, or statuses if prompted
Review the summary and click Confirm (make sure you give it a good review).

Clara Belin-Brosseau_Elevatic

Hi @kshridvipa7878

As an alternative I can suggest trying our app Elements Copy & Sync.

The native bulk move can work, but it has limits on very large volumes and doesn't give you much control over field mapping between a Kanban and a Scrum scheme. Elements Copy & Sync lets you move a full hierarchy of Jira issues from Project X to Project Y (with all the fields, comments, attachments and links needed), and you can reuse the same recipe as many times as you like, on any batch of issues.

The steps are the following:

Create a "Copy and Synchronize work items" recipe
In the Source tab, define your source project (Project X) select "Copy full hierarchy" (this brings along child issues/subtasks)

Define Project Y (your new Scrum project) as the target
Map your fields once, including how backlog items should land (since Kanban has no sprints, you decide where they go in the Scrum backlog)
Go to the issue search bar, filter on Project X, and select your recipe to run the copy in bulk

This way you keep full control over the mapping and can run it in batches rather than relying on one large bulk-move operation.

Don't hesitate to try the app, it's free for 30 days (and stays free under 10 users).

All comments

Ignacio Vera

hi @kshridvipa7878

Viswanathan Ramachandran

to echo Ignacio, first move all the issues from X to Y. Then create a new scrum board from the Y project.

Jason Krewson

Below are the steps to do this, hope it helps!

Steps

Go to Filters > Search work items
Search for all issues in Project X: project = X
Click 3 dots (•••) in the top right corner > click Bulk Change
Select all issues and click Next
Choose Move Issues and click Next
Select Project Y as the destination project
Map any required fields, issue types, or statuses if prompted
Review the summary and click Confirm (make sure you give it a good review).

Clara Belin-Brosseau_Elevatic

Hi @kshridvipa7878

As an alternative I can suggest trying our app Elements Copy & Sync.

The steps are the following:

Create a "Copy and Synchronize work items" recipe
In the Source tab, define your source project (Project X) select "Copy full hierarchy" (this brings along child issues/subtasks)

Define Project Y (your new Scrum project) as the target
Map your fields once, including how backlog items should land (since Kanban has no sprints, you decide where they go in the Scrum backlog)
Go to the issue search bar, filter on Project X, and select your recipe to run the copy in bulk

This way you keep full control over the mapping and can run it in batches rather than relying on one large bulk-move operation.

Don't hesitate to try the app, it's free for 30 days (and stays free under 10 users).

kshridvipa7878

Thank you all so much for your support and for taking the time to help. I was able to successfully transfer all the issues using the Bulk Move option.

Thanks again for your valuable assistance!

kshridvipa7878

Hi @Clara Belin-Brosseau_Elements @Jason Krewson @Viswanathan Ramachandran @Ignacio Vera Thank you so much for your support! Your suggestion really helped. I was able to successfully move all the issues using Bulk Move. Really appreciate your help!

Jason Krewson

Anytime, have a great weekend!

Trudy P Claspill

Hello @kshridvipa7878

What type of project does this concern?

For a Team-managed Software project you can have either the Kanban board activated or the Scrum board activated. If you don't need the Kanban board any more and you want all issues in the project managed by Scrum you can make the switch within the project without moving the issues.

If this concerns other types of projects you still don't necessarily need to move the issues to another project. You can have multiple boards set up for Company-managed software projects. You could keep both the Kanban board and also have a Scrum board. You can create a Scrum board referencing the original project by clicking the "+" next to the project name and select Scrum board.

Screenshot 2026-07-10 at 11.09.14 AM.png

Ignacio Vera

Glad to help

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