Issues affecting migration time
This insight checks if your total number of issues (including the archived ones) is above the recommended value.
How does the issue count affect migration time?
The migration assistant’s throughput has its limits. The median migration rate (based on all migrations we’ve observed in the past 3 months) is 7,5M issues per 24 hours. If you try to migrate more issues than that, it’s likely that your migration will take longer than 24 hours.
Note that this rate is a median and might also be affected by other factors that we’ve described on this page. We’ve seen migrations with lower rates and some with even 2-3x higher rates. You should treat this number as a suggestion – depending on your environment, you might achieve a higher or lower rate.
What’s the recommendation?
If the 24-hour (or any fixed) downtime is what you’re looking for, your goal is to reduce the number of issues you migrate in a single migration plan. You can achieve that by migrating issues at different times, and in different plans.
For example, by:
Archiving inactive projects and pre-migrating them
Pre-migrating already archived projects
Speeding up your Jira migration
Dividing the migration of your remaining projects into phases
Archive inactive projects and pre-migrate them
We show the number of inactive projects based on the last issue update set to 24 months. If project issues weren't updated during this time, we'll count it as inactive. The last issue update changes after updating any of the issue fields or adding and editing comments.
It’s not strictly required to archive your inactive projects. Since your goal is to reduce the number of issues in a single migration, you can also pre-migrate these projects as active. But, with such a high total number of issues, we recommend that you archive some inactive projects to avoid having performance issues in cloud in the future.
Before you begin
Migrating projects in phases comes with risks and limitations, mainly related to app dependencies and configuration items that should be migrated together. Before you start pre-migrating projects, check known issues and best practices.
Identify inactive projects
When viewing this insight, you’ll have an option to select View inactive projects in Jira. This is a link to project list in your Jira instance, where projects are sorted by last issue update.
You can also go to Administration > Projects, and select the Last issue update column to sort them:
Archive inactive projects
You can’t archive projects in bulk, so you’ll have to archive them one by one.
To archive any project:
Go to Administration > Projects.
Next to your project name, select Actions (…) > Archive project.
Your project will disappear from Jira, and will land in the Archived projects page. When using the migration assistant, you’ll be able to filter archived projects.
Pre-migrate archived projects
When using the migration assistant, you can quickly add all archived projects into a separate migration plan. If you haven’t archived all inactive projects, you can also include them.
To pre-migrate archived projects:
Go to Administration > Migrate to cloud.
Create a new migration plan.
Follow the steps in the wizard until you reach the screen where you can choose what to include in your migration.
In the Projects card, where you can select projects to include, use the Jira archived filter in the drop-down to list only archived projects.
Select the Select all check box, and add them to your migration plan.
What happens to archived projects after migration?
Archived projects in cloud look and behave in a similar way as in Server or Data Center. You can view and restore them from the same Archived projects page in the Jira administration.
Pre-migrate archived projects
When using the migration assistant, you can quickly add all archived projects into a separate migration plan. If you haven’t archived all inactive projects, you can also include them.
Before you begin
Migrating projects in phases comes with risks and limitations, mainly related to app dependencies and configuration items that should be migrated together. Before you start pre-migrating projects, check known issues and best practices.
To pre-migrate archived projects:
Go to Administration > Migrate to cloud.
Create a new migration plan.
Follow the steps in the wizard until you reach the screen where you can choose what to include in your migration.
In the Projects card, where you can select projects to include, use the Jira archived filter in the drop-down to list only archived projects.
Select the Select all check box, and add them to your migration plan.
What happens to archived projects after migration?
Archived projects in cloud look and behave in a similar way as in Server or Data Center. You can view and restore them from the same Archived projects page in the Jira administration.
Speed up your migration
Migration speed is affected by many factors, such as:
Migration assistant version
Heap size
Network bandwidth
Traffic on the server
Hardware
We’ve described a set of best practices that allow you to speed up a Jira migration.
Learn how to speed up a Jira migration
Divide your migration into phases
For larger instances, a multi-phased migration strategy might be beneficial, dividing the total number of issues into manageable chunks.
Learn how to divide your Jira migration into phases
Was this helpful?