Can I change a next-gen project to a regular project?

[Caleb Gonzalez]

I'm realizing some key limitations pretty late into my project set up, and I can't afford to start new. Can I have my project changed to a regular project?

[Rob Horan · Accepted solution]

Yes you can - please see this page:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/

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

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.

• 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 as the data stored in these fields will be lost.

• 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.

• 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.

• 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.

• Reports: Reports 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).