Jira Bulk Move: A Step-by-Step Guide to Moving Issues Safely
Need to move Jira issues safely? Follow this jira bulk move guide to avoid broken workflows and protect issue data. Read now to learn the steps.
A Jira bulk move can save hours when you need to transfer many issues between projects. It can also create broken workflows, missing field values, and confusing issue-key changes if you rush through the process.
That risk grows when projects use different issue types, required fields, permissions, or status rules. A move that looks simple in a dialog can affect dashboards, links, automation, and teams that depend on the original setup.
But here's the truth: careful preparation makes the operation far more predictable. I’ll walk you through the permissions, selection, field mapping, and post-move checks that help you move issues safely and catch problems early.
How to Move Jira Issues in Bulk Safely
A Jira bulk move transfers multiple issues to a different project or issue type through Jira’s bulk change workflow. You select issues, choose the move operation, map fields and statuses, then review the results.
The exact labels can vary by Jira version and configuration. Before moving a large group, test the process with a small, representative set of issues.
- Confirm permissions and scope. Check that your account has permission to browse the affected projects and perform bulk changes. You may also need permission to move issues, create issues in the destination project, and assign users. Ask a Jira administrator to confirm access before scheduling the move.
- Define exactly which issues should move. Use Jira’s issue search to build a precise filter. For example, you might select open bugs in one project that belong to a retiring product area. Review the results for unexpected issue types, statuses, or projects before continuing.
- Check the destination project. Compare its issue types, workflows, required fields, components, versions, and permission settings with those of the current project. Identify fields that do not exist in the destination or have different allowed values.
- Run a small test move. Select a few representative issues, including different issue types and statuses, and move them first. A test can reveal mapping problems before they affect hundreds of issues. If you cannot test in a safe project, coordinate a maintenance window and recovery plan with your administrator.
- Start the bulk operation. Open the selected issues in Jira’s search view, choose the bulk change option, and select the move action. Follow the prompts to choose the destination project and map each issue type to a valid destination type.
- Map fields and statuses carefully. Jira may ask you to map statuses, components, versions, and other fields. Choose values that preserve the intended meaning. If a field has no equivalent, decide with the project owner whether to leave it blank, use a suitable replacement, or stop and adjust the destination configuration.
- Review the confirmation screen. Check the issue count, destination project, issue-type mappings, and field choices. Confirm that the selected issues match your plan. Bulk operations can be difficult to reverse cleanly, so do not proceed if the summary contains unfamiliar values.
- Complete the move and inspect the result. Review Jira’s completion message and any errors. Check a sample of moved issues for their project, type, status, assignee, links, comments, and key fields. Then ask affected teams to verify their usual boards and workflows.
Let me explain: a successful operation is not just a completed progress indicator. It also means the moved issues still make sense to the people who use them.

Prepare the Projects Before You Move Anything
A short pre-move review can prevent most avoidable errors. Treat the move as a change to project configuration, not simply a change to issue location.
- Agree on the reason for the move, the destination, and the teams affected.
- Record the intended issue count and selection criteria so you can compare them with the final result.
- Check issue type schemes, workflows, required fields, components, versions, and custom fields in both projects.
- Confirm which users will need access after the move, including project roles and notification settings.
- Choose a low-activity window if the move could interrupt active work.
- Ask your Jira administrator about a recovery point and any organization-specific limits on bulk changes.
Here's why: two projects can look alike to an issue reporter while enforcing very different rules behind the scenes. For example, a destination project may require a component that the selected issues do not have.
List any known differences before starting. If the destination has a required field without a clear value for every issue, resolve that configuration question first.
Understand What Can Change During a Bulk Move
Moving an issue to another project can change its issue key because the key includes the project identifier. Jira generally keeps old keys as references to the moved issue, but you should verify how your organization’s setup handles links and integrations.
A move can also affect status mapping, issue type, field values, project permissions, notifications, and automation. For example, an issue in “In Review” may need to map to a different review status in the destination workflow.
You might be wondering: will a bulk move carry every project-specific setting with each issue? No. The destination project’s configuration governs the issue after the move, so values that do not fit may require mapping or manual review.
Also check dashboards, saved filters, board queries, and external systems that refer to project keys or issue links. A team might rely on a saved filter that only includes the old project, even though the issues have moved successfully.
Validate the Move and Follow Up With Teams
Once the operation finishes, compare the result with the selection you intended to move. Confirm that the number of successful moves and any reported errors match your expectations.
Then inspect examples from each important group. If you moved bugs, tasks, and support requests, check at least one of each rather than reviewing only the first issue in the results.
- Verify project, issue type, status, assignee, priority, and required fields.
- Check comments, attachments, links, and parent-child relationships where relevant.
- Confirm the moved issues appear on the correct boards and in expected filters.
- Test automation and notifications that should run in the destination project.
- Tell affected teams where to find the issues and whether saved links or filters need updating.
The best part? You do not need to inspect every field on every issue manually when the move is well scoped. A risk-based sample plus error review can reveal patterns, while owners can check the issues most important to their work.
ONES.com for Project Workflows Around a Migration
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management, while ONES Wiki provides knowledge management; they are sold separately.

ONES.com is not a Jira bulk-move utility, and it does not automatically transfer Jira issues through the steps above. It may be relevant if your team is also reviewing project workflows or knowledge management while planning a broader platform change.
Value Proposition
ONES Project can support teams that want Jira-compatible workflows, reporting, sprint management, automation, and custom fields in one project management environment. Its on-premise and other self-hosted deployment options can matter when teams need control over where their platform runs.
Core Capabilities
- Jira workflow familiarity: Teams concerned about retraining can use Jira-compatible workflows in ONES Project, helping preserve familiar work patterns while evaluating a Jira alternative.
- Custom workflows: Teams with processes that do not fit a default flow can configure custom workflows, making it easier to reflect their actual review and approval steps.
- Custom fields: If teams need project-specific details, custom fields can capture those details in the project workflow rather than relying on informal workarounds.
- Sprint management: Agile teams that need to plan and track iterations can manage sprints in ONES Project, keeping sprint work within their project management environment.
- Built-in reporting: Teams that want visibility into project progress can use built-in reporting, reducing reliance on extra reporting plugins for common needs.
- Automation: Repeated project actions can be automated, helping teams reduce routine manual steps and keep work moving consistently.
- Deployment choice: Organizations with hosting or network requirements can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment options.
- Free plan capacity: Teams evaluating the platform can start with a free plan for up to 30 seats, giving them room to assess workflows before making a broader decision.
Application Scenarios
A team consolidating several Jira projects might first complete its Jira bulk move, then review whether its future project workflows should remain in Jira or use another platform. ONES Project can be considered as a Jira alternative during that separate evaluation.
An organization with restricted networks may compare deployment requirements while planning a future change. ONES.com offers self-hosted options, including On-Premise, Private Cloud, and Air-gapped deployments, with full feature parity between cloud and self-hosted versions.
Teams that manage project work and internal knowledge separately may also evaluate ONES Wiki alongside ONES Project. The products are sold separately, so a team can assess each according to its own requirements.
Common Bulk-Move Challenges and Fixes
- Some issues fail because required fields are missing. Check the destination project’s required fields before moving. Update its configuration or decide on valid field values before retrying failed issues.
- Statuses do not have a clear equivalent. Compare both workflows with the project owners. Map each current status to a destination status that represents the same stage of work, then test the mapping with a small group.
- Moved issues disappear from a board. Review the board’s filter and project scope. Update the filter if it still targets only the previous project or excludes the moved issue types.
- Issue keys in links or integrations seem outdated. Check how Jira handles old-key references in your environment, then review the integrations and saved links that rely on project identifiers. Notify teams before they treat a stale reference as a missing issue.
- The operation reports errors or only partly completes. Preserve the error details, identify which issues did not move, and correct the specific cause before retrying. Avoid running the full selection again until you know which issues already reached the destination.
Frequently Asked Questions
Can I bulk move issues between Jira projects?
Yes. Jira provides a bulk change workflow that can move multiple issues to another project, if your permissions and project configuration allow it. You select the issues, choose the move operation, and map issue types, statuses, and fields as needed. Test with a small, representative group first, since required destination fields and workflow differences can prevent some issues from moving cleanly.
Do Jira issue keys change after a project move?
They can. An issue key contains a project identifier, so moving an issue to another project may give it a new key. Jira generally retains the old key as a reference, but integrations, saved filters, or external links may behave differently depending on your setup. Check those dependencies and confirm how old-key references work in your Jira environment before moving a large group.
Can I undo a Jira bulk move?
There may not be a simple one-click rollback for a completed bulk move. You might be able to move issues back, but field mappings, workflow changes, and issue-key changes can complicate that recovery. Before starting, ask your Jira administrator about recovery options and create a suitable recovery point. A small test move can also catch configuration issues before a larger operation begins.
Why did some issues fail to move?
Common causes include missing required fields, unsupported issue types, permission gaps, or a status that has no valid destination mapping. Jira’s completion details can help identify the affected issues and errors. Review each failure, correct the underlying configuration or field value, and retry only the issues that did not move. Confirm which issues succeeded first so you do not create duplicate work.
Conclusion
A safe Jira bulk move starts with a precise issue selection and a clear understanding of both projects’ configurations. Check permissions, test representative issues, map fields and statuses carefully, then validate the results with project owners.
But here's the truth: skipping preparation can turn a quick move into a long cleanup. A few deliberate checks help protect workflows, links, and team visibility as issues change projects.
If your move is part of a broader project-management review, evaluate any future platform separately from the Jira operation itself. Keep the immediate goal clear: move the right issues, preserve their meaning, and make sure people can find and continue their work.