1. Home
  2. Knowledge Base
  3. Assistance Setting up Your Demo Migration
  4. How to migrate data between Classic and Next-Gen projects in Jira Service Management

How to migrate data between Classic and Next-Gen projects in Jira Service Management

Recently, Jira Service Management introduced a new type of project - Next-Gen project. However, for now, they don’t provide a way to import a JSON or CSV file to these Next-Gen projects. That’s why Help Desk Migration only can migrate your records to Classic projects.

But if you still want to migrate to a next-gen project with Help Desk Migration service, there’s a workaround. You can import your data to the classic project and then migrate data between classic and next-gen projects using the free solution from Jira Service Management.

So, the first thing you should do after the migration to the Classic project is to have “Make bulk changes” global permission (granted by Jira admin). Here’s how to give this permission:

1. Click the Settings.

jira service management settings

2. Under the System section, find Global Permissions.

jira service management global permissions

3. Now, scroll down right to the bottom of the page. In the Grant Permissions section, you have to choose the Make bulk changes permission and grant it to the necessary user group. Then, click the Add button.

Grant permissions in Jira

Now, when you have the necessary permissions, you can go on to the next step. Here’s how to find the migrated issues from your previous platform and move them to the necessary next-gen project:

1. Click the Filters and select All issues.

jira service management filters

2. Click the Project filter button and choose the project you want to migrate from.

jira service management projects

3. Then, in the top-right corner, select more (three-dot sign) and Bulk change all. The system will open the Bulk Operation wizard.

Bulk change issues in Jira

4. Go through the wizard, choose the issues that you want to move and click Next.

jira service management bulk update

5. Click Move Issues and then Next again.

jira service management bulk updates

6. The “Select Projects and Issue Types” screen will appear. Here, you have to choose the destination project to move the records there. You’ll also have to pick the type of each issue in the destination project. Click Next when you’re ready.

jira service management bulk updates

7. The next step is “Map status for Target Project”, where you will have to choose the destination status for each issue status from the old project.

jira service management bulk updates

8. The last step is reviewing the summary of all the issues prepared for the migration to the next-gen project. When you’re done reviewing, click Confirm.

jira service management confirming bulk updates

What to remember when migrating from Classic to Next-Gen projects:

There are a few things to consider when you migrate from Classic to Next-Gen project. They are technically quite different, so keep in mind these peculiarities:

  • Active sprints (sprints in progress) won’t migrate to the next-gen projects. However, the issues that were in the active sprints will move to the backlog of the destination project.
  • Epic links between the issues won’t exist in the next-gen project.
  • Custom fields must be recreated in your next-gen project manually after the migration.
  • Story points estimation will be lost, however, you can still use them in the next-gen project by enabling the Estimation feature.
  • The data for your Velocity report won’t be saved, so the report will show that no points were completed before.
  • Reporting history will also be lost in the migration process.
  • Project and issue key will change as you move to the new project because they cannot be reused. The links from your old keys will also be redirected as soon as you migrate using the Jira migration wizard.

Looking for more data migration details?

Let’s talk now
Did this answer your question?
Book a Call
— %s