Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server or Data Center products.
The Jira Cloud Migration Assistant lets you migrate dashboards, all boards and filters to cloud.
You can select one of the following options to migrate dashboards using Jira Cloud Migration Assistant:
Option | Description |
---|---|
Only dashboards linked to selected projects specified in gadgets or dashboard permissions | This includes dashboards linked to projects selected for migration that are specified in the gadgets or dashboard permissions. This will not include dashboards that are not linked to any projects. To migrate such dashboards, use the All dashboards option. |
All dashboards | This includes all dashboards on your server or Data Center. |
None | No dashboards will be included for migration. |
Note that:
After migration, some dashboard gadgets may not work because certain gadgets on the server are either third-party or not currently supported in the cloud.
Some projects related to dashboards may not have been selected for migration. You can continue migrating these dashboards. We'll relink when you migrate them again, along with their associated projects.
During the migration, you may find that some gadgets are missing from the dashboards. This is because some gadgets on the server are either third-party or not currently supported in the cloud. The following table lists all gadgets that are migrated using Jira Cloud Migration Assistant and those that are unsupported by the migration assistant or the cloud:
Gadgets migrated | Gadgets not migrated |
---|---|
|
|
If you get an error related to gadgets, check the details on the page: Troubleshoot migration with Jira Cloud Migration Assistant
When you decide on the scope to migrate boards and filters, it can include:
Boards created from multiple projects
Boards from an existing saved filter
All shared filters - a filter can have shared access with:
Shared access with | Description |
---|---|
Private | The filter is private and can only be viewed and edited by the owner and Jira admins. |
User/Group/Project | The filter is shared with a user, group, or project. Depending on the permissions granted, users can view or edit the filter. |
Any logged-in user | The filter is shared with all users on your Jira instance. |
Anyone on the web | If a filter is Shared with anyone on the web, this allows public access to certain information on your site. If you want to prevent people who aren’t logged in from viewing this information and limit access to your logged-in users, either:
|
Single project boards and filters created and shared with projects selected for migration would be automatically migrated regardless of the options chosen.
In the Jira Cloud Migration Assistant, you can choose one of the following options:
Option | Migration behavior | Example | |
---|---|---|---|
Only filters and boards shared to selected projects | What’s migrated | What’s not migrated | |
|
|
| |
All filters and cross-project boards |
|
To migrate these boards, include the relevant projects in your migration. |
|
None |
(Some boards and filters are migrated even when this option is selected. Known issue: MIG-1654)
|
|
We have a number of channels available to help you with your migration.
For more migration planning information and FAQs, visit the Atlassian Cloud Migration Center.
Have a technical issue or need more support with strategy and best practices? Get in touch.
Looking for peer advice? Ask the Atlassian Community.
Want expert guidance? Work with an Atlassian Partner.
Was this helpful?