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.

Create a project to receive your existing issues

You'll need to have a new Scrum or Kanban project available, so your current software project issues have a place to go to.

Create a new next-gen project to receive your existing classic project issues

To create a new next-gen project:

  1. Click your Jira icon ().
  2. Select Projects.
  3. Select Create project Try a next-gen project.
  4. Make sure you've selected either the Scrum or Kanban template. You can select Change template to view all available next-gen templates.
  5. Enter a name for your new project, and hit Create.

Or, create a new classic project to receive your existing next-gen project issues

If you want to move from a next-gen project to a classic project, your Jira admin will need to create a new classic project for you. Reach out to them for help. Learn more about creating classic projects.

To create a new classic project:

  1. Click your Jira icon ().
  2. Select Projects.
  3. Select Create project Classic project.
  4. Make sure you've selected either the Scrum or Kanban template. You can select Change template to view all available classic templates.
  5. Enter a name for your new project, and hit Create.

Find and move your existing issues to your new project

Now that you have an empty project waiting to receive your old project's issues, you can move all your existing issues into the new project.

To complete this step, your Jira admin must grant you the Make bulk changes global permission. Learn more about global permissions.

Search for your existing issues

First, you need to find the issues you want to move:

  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. The Bulk Operation wizard appears.

Move your existing issues into your new project

Next, walk through the Bulk Operation wizard to move your issues into your new 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. Here's a few things to consider when you migrate from a classic software project to a next-gen software project:

  • 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: Links between epics and other issues (Story, Bugs, Tasks, etc...) in your classic project won't exist in your next-gen project. The issues themselves will still exist, but the links between them won't.

  • 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.
  • Report history: All reporting history is lost in this migration process. The Burnup report and Velocity report won't be migrated.
  • Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue keys.

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

Next-gen projects and classic projects are technically quite different. Here's a few things to consider when you migrate from a next-gen software project to a classic software project:

  • Board statuses: If you customized your next-gen board, you'll need to set up the same statuses in your classic project's workflow. Only Jira admins can create and modify statuses and workflows. Learn more.
  • Issue types: If you added your own issue types to your next-gen project, you'll need to have a Jira admin recreate these using an issue type scheme that they associate to your new classic project. Learn more.
  • Custom fields: If you customized the fields that appear on your next-gen issue types, you'll need to have a Jira admin recreate these fields in your new classic project's screen schemes and field configuration schemes. Learn more.
  • Project access: Access to classic projects is controlled by a permissions scheme. Only your Jira admin can update your classic project's permission scheme. Learn more.
  • EpicsJira moves your epics across if you map them to an epic issue type in your new project. But, you'll lose the relationship between your epics and their child issues. The child issues themselves will sill exist, but the links between them won't.
  • 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.
  • Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in classic projects (Story points) is different to the custom field used in next-gen projects (Story point estimate). 
  • Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue keys.
Last modified on Aug 27, 2019

Was this helpful?

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