• Products
  • Documentation
  • Resources

Choose what Jira data to migrate using the assistant

With this migration option, you build a migration plan and fill it in with data. You can either include everything in a single plan or divide it into many migration plans.

Looking for information on assessments?

Before you migrate data, you should complete assessments available in the assistant:

Good to know

Here are some things you should know about:

  • Data won’t be overwritten or deleted
    The assistant won’t delete anything from either your Server/Data Center or cloud sites. The migrated data will be added to your cloud site along with any data that is already there.

  • Data may get linked to avoid duplication
    When you migrate multiple times, we’ll attempt to link identical configuration items to avoid duplicates. Learn more

  • Jira Align migration
    If you have Jira Align connected to your Jira instance, you need to complete additional steps before you migrate. Learn more

  • Known issues
    Check the troubleshooting guide for the list of known issues related to migration. Some of these actions can help you avoid problems during migration. Learn more

Before you begin

Complete these steps:

  • Check what can be migrated with this option. Learn more

  • Update the assistant and allowlist required IPs and domains. Learn more

  • Complete the pre-migration checklist to prepare your environment. Learn more

  • Pre-migrate users, groups, and attachments before project data to reduce downtime. Learn more


  • To migrate, you need to be a system admin in the source instance and organization admin in the destination cloud site.

Create a migration plan and connect to your cloud site

To create a migration plan:

  1. Open the Jira Cloud Migration Assistant.

  2. Select Create new migration.

  3. On the Connect to your cloud site screen, provide the following data:

Example screen


"Connect to your cloud site" screen.
  • Name your migration

  • Choose migration stage: production or testing. This option doesn’t affect your migration. It will help you recognize different migration plans on the dashboard.

  • Choose destination cloud site: If you don’t have one yet, you can activate your free Cloud migration trial and create one.

4. On the Migration options screen, select Choose what to migrate.

Two migration options, with the "Choose what to migrate" one highlighted.

Choose what data to include in your plan

After selecting Choose what to migrate, you can add the following items to your migration plan.

Example screen

What you can migrate

Cards showing data that can be added to a migration plan, for example projects.
  • Advanced Roadmaps plans

  • Projects (along with attachments and archived issues)

  • Cross-project boards and filters

  • Users and groups

  • Jira Service Management customers

  • Apps

How each data type is migrated

Check how each data type is migrated and what are the best practices:

Migrate Advanced Roadmaps plans

To add Advanced Roadmaps plans to your migration:

  1. On the Advanced Roadmaps plans card, click Select or Edit.

  2. Choose an option to migrate the plans:




Migrate all supported Advanced Roadmaps plans, and:

  • Projects that are linked in these plans

  • Boards that are linked in these plans

  • Filters that are linked in these plans, excluding private filters


Don’t migrate any plans.

3. When you’re ready, select Add to migration.

Migrate projects

To add projects to your migration:

  1. On the Projects card, click Select or Edit.

  2. Select the projects you want to include in your migration.

  3. Choose an option to migrate projects:




Migrate all supported data and configuration items from the selected projects.

Include all archived issues

Migrate all supported data, configurations and archived issues from the selected projects.

Attachments only

Migrate only attachments from the selected projects.

4. When you’re ready, select Add to migration.

Known issues about migration of Archived Issues :

  • Migration Duration: Including archived issues in your migration increases the overall data size being transferred, which may extend the migration process duration.

  • Issue Archival Feature on Cloud: Archiving issues on the cloud is an exclusive feature available to Atlassian Cloud Premium subscribers and is accessible only via APIs. Learn how you can use issue archiving in cloud

Migrate cross-project boards and filters

To add cross-project boards and filters to your migration:

  1. On the Cross-projects boards and filters card, click Select or Edit.

  2. Choose an option to migrate cross-project boards and filters:



Only cross-project boards and filters related to selected projects

Migrates cross-project boards and filters linked to the related projects added for migration

All cross-project boards and filters

Migrate all the cross-project boards and filters present in your server instance.


No cross-project boards and filters will be included for migration, unless they are an issue source for any Advanced Roadmaps plans you’ve included in your migration.

3. When you’re ready, select Add to migration.

Migrate users and groups

To add users and groups to your migration:

  1. On the Users and groups card, click Select or Edit.

  2. Choose an option to migrate users and groups:



Only users and groups related to the selected projects

Migrate only users and groups that are referenced in the projects you added to your migration plan.

Once you select this option, you’ll also be able to add:

  • all users and groups assigned to roles of projects being migrated

  • all users who are members of groups included in the migration

This is useful if you’d like to also migrate users who were assigned projects roles or are members of other migrated groups, but aren’t actually referenced in the projects, which would exclude them from migration.

All users and groups

Migrate all users and groups from your Jira users directory.

If you’re looking to speed up your migration, this option is faster. When migrating only a subset of users, the assistant needs to check them against every project in Jira, which takes time.

3. Choose whether to preserve group membership or not:



Migrate users and groups separately

Migrate selected users and groups without adding them to any groups. Users will be given Atlassian accounts, but they won’t have access to any products or projects, and won’t consume the license.

Preserve group membership

Migrate selected users and groups, preserving their group membership. Users will have access to their projects and will count towards your license.

4. When you’re ready, select Add to migration.

Migrate Jira Service Management customers

To add customers to your migration:

  1. On the Customers card, click Select or Edit. This card is only available if you have Jira Service Management installed.

  2. Choose an option to migrate customers:



All Jira Service Management customers

Migrate all customers who have ever created a request using the customer portal or email channel.

Only customers related to the selected projects

Migrate only customers who have created a request or are referenced on a request in service projects included in your migration plan.

No customers

Don’t migrate any customers. This option is available if you haven’t selected any service projects.

3. When you’re ready, select Add to migration.

Migrate apps

To add data from apps to your migration:

  1. On the Apps card, click Select or Edit.

  2. Choose an option to migrate:




Migrate data from all apps that you marked as ‘Needed in cloud’ when assessing and preparing apps, and that have a migration path provided by the app vendor.


Don’t migrate any app data.

3. When you’re ready, select Add to migration.

Next steps

Once you’re done, check for errors in your migration. Learn how to check for errors in your migration

More information and support

We have a number of channels available to help you with your migration.

Support for Atlassian Server products ends in February, 2024. Learn more about the Server end of support timeline.

Still need help?

The Atlassian Community is here for you.