Migrate between next-gen and classic projects

Get started with next-gen projects

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This page will be useful to you if:

  • Your team currently works in a classic project, and you want to migrate to next-gen projects.
  • Your team gave next-gen projects a try, found that it didn't suit how you work, and you want to move your issues to classic projects.

Before we begin

You'll need to have available a new Scrum or Kanban project, so that the issues from your current software project have another project to go to. To create a new project:

  1. Click your Jira icon ().
  2. Select Projects.
  3. Select Create project > Classic project (if you're migrating from next-gen to classic) or Try a next-gen project (if you're migrating from classic to next-gen).
  4. Click Change, and select either the Scrum or Kanban template.
  5. Enter a name for your new project, and hit Create.

Start the migration process

  1. Click your Jira icon () to navigate to the Jira home page.
  2. Select Issue and filters.
  3. Select All issues.
  4. Click the Project filter, and select the project you want to migrate from.
    (If you're looking at the Advanced mode, you'll need to select Basic)
  5. In the top-right corner, select more (•••) > Bulk change all.

Migrate your project

  1. Select the issues you want to migrate and hit Next.
  2. Select Move Issues and hit Next.
  3. On the Select Projects and Issue Types screen, you'll need to select where the issues from your old project will go. Select a destination project and issue type, and hit Next. This is the issue type that each issue in your old project will become in the new project.
  4. On the Map Status for Target Project screen, select a destination status for each status in your old project. This is the status that each issue in your next-gen project will take on in the new project.
  5. On the final screen, click Confirm.

Things to keep in mind if you migrate from classic to next-gen

Next-gen projects and classic projects are technically quite different, so a few things can break when you migrate from a classic software project to a next-gen software project. Here's what we know so far:

  • Active sprints: Sprints in progress in your classic project won't move to your next-gen project. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project.

  • Epic links and issue links: Any issue links in your classic project will not exist in your next-gen project. The issues themselves will still exist, but the links between them won't.

  • Subtasks: All subtasks will be lost in this migration process.

  • Custom fields: These must be recreated in your new next-gen project.

  • Story points estimation: This data will be lost, however you'll be able to start using story points estimation by enabling the Estimation feature in your next-gen project.

  • Reports: Data for your project's Velocity report won't be saved. The Velocity report will show that no points were completed in past sprints.

Things to keep in mind if you migrate from next-gen to classic

  • ReportsReports data won't be saved. Even though your issues will be retained, data for your project's Velocity and Burnup reports won't transfer over, and will be lost.
Last modified on Apr 12, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.