2. Considerations before migrating
If you have any issues or concerns, let us know via portfoliofeedback@atlassian.com.
- 1. Understand the types of plans
- 2. Considerations before migrating
- 3. Migrate classic plan data to a live plan
- 4. Enable the improved interface in a plan
Depending on how your teams work, you'll need to consider first the type of plan that you'll be migrating your classic plan data into either a plan with the improved interface or a live plan.
To use the latest and greatest features of Portfolio for Jira, we recommend you migrate from classic plans to plans with the improved interface.
Migrating to plans with the improved interface
To migrate from classic plans to plans with the improved interface, you'll need to:
- Migrate your classic plan data into a Portfolio for Jira live plan.
- Once you have your live plan ready, enable the improved interface in that plan.
Required migration path
BE ON PORTFOLIO FOR JIRA 2.21 TO 2.27 → MIGRATE CLASSIC PLAN TO LIVE PLAN → UPGRADE TO PORTFOLIO FOR JIRA 3.0 OR LATER
This means that:
- You'll first need to be running on any version from 2.21 to 2.27 of Portfolio for Jira.
- Once you're running on any of these versions, you can then proceed to migrating your classic plan data to a live plan.
- Once you've migrated your classic plan data to a live plan, you can then proceed to upgrading to Portfolio for Jira 3.0 or later.
Why should you migrate to the improved interface
The improved interface offers multiple advantages over classic plans. Most importantly, however, is the fact that the improved interface relies on real-time, dynamic data directly from Jira. Meanwhile, in classic plans, data is stored independently.
Rather than having to import data from Jira to a classic plan, you can define projects, boards, or filters as issue sources instead. With issue sources configured, real-time data is automatically surfaced, and you can quickly save any changes you make in your plan back to Jira.
Migration to live plans
To migrate from classic plans to live plans, you'll only need to migrate your classic plan data into a Portfolio for Jira live plan.
Required migration path (minimum version)
BE ON PORTFOLIO FOR JIRA 2.21 TO 2.27 → MIGRATE CLASSIC PLAN TO LIVE PLAN
This means that:
- You'll first need to be running on any version from 2.21 to 2.27 of Portfolio for Jira.
- Once you're running on any of these versions, you can then proceed to migrating your classic plan data to a live plan.
Recommended migration path
BE ON PORTFOLIO FOR JIRA 2.21 TO 2.27 → MIGRATE CLASSIC PLAN TO LIVE PLAN → UPGRADE TO PORTFOLIO FOR JIRA 3.0 OR LATER
Even if you prefer to use live plans, and not plans with the improved interface, we still highly recommend that you ultimately upgrade to Portfolio for Jira 3.0 or later. This is so that you would have access to the latest and greatest features of Portfolio for Jira, and should you change your mind later on, you can already easily enable the improved interface for any of your live plans.
Things to consider before you migrate
After migrating from classic plans to plans with the improved interface, you'll need to reconfigure the following items for each new plan:
| Initiative relationship | If migrating from classic plans to plans with the improved interface or live plans The "parent-child" relationship of initiatives and epics will not be automatically set. The issue links may already be created between the initiatives and epics in the Jira tickets themselves, but you'll still need to set the parent initiatives for all your epics. If you're already using a live plan If you're already using a live plan and you're simply enabling the improved interface in that plan, then the "parent-child" relationship of initiatives and epics are already automatically set. |
| Team data | Teams, team members, availabilities, and velocities will not carry over during migration. You'll need to create the teams, add members, and configure other team settings as needed. Also, individual availabilities are no longer supported in the improved interface. |
| Plan configurations | Configurations of your plan, such as default estimates, will not carry over during your migration. They will need to be reconfigured once your migration is complete. |
| Sprint creation | If you have sprints in your classic plans that you want to be available when you migrate to the improved interface, then you'll need to create these sprints in Jira. The advantage of sprints in the improved interface is that these are the actual sprints in Jira. This way, you can directly plan and groom your actual sprints in Portfolio for Jira. |
The following items will not be migrated and cannot be reconfigured in the improved interface:
| Earliest start dates | We're simplifying the experience of scheduling issues by using only one type of date — target dates. This is why earliest start dates are no longer available in the improved interface. You can still use other custom date fields that you may have configured before enabling the improved interface. However, you'll first need to add these custom fields to your plan. |
Scheduled start and end dates | The calculated dates from classic plans won't be directly accessible in the improved interface. The dates will need to be reproduced by either:
Note that the date fields used in the improved interface are called target dates, and these can be accessed and updated in both Jira and Portfolio for Jira. |
| Stages and skills | Stages and skills are not supported in the improved interface for the following reasons:
|
| Themes | Themes are no longer available in the improved interface. Instead, we're replicating much of its value by providing flexible coloring options for labels and other custom fields. |
| Future sprints | At this stage, we're not considering implementing the functionality of future sprints in the improved interface. |