• Products
  • Documentation
  • Resources

What gets migrated with Jira site import

Site Import will no longer be available for server to cloud migrations

From February 1, 2022, we’ll discontinue server to cloud migrations using Site Import depending on the number of users you’re looking to migrate.

If you’re looking to migrate:

  • 1-10 users - Site Import will be available until Jan 31, 2022

  • 11 - 100 users - Site Import will be available until Feb 28, 2022

  • 101-250 users - Site Import will be available until Mar 31, 2022

  • 251 - 1000 users - Site Import will be available until Apr 30, 2022

  • More than 1000 users - Site Import will continue to be available until further notice.

To view the number of licensed Jira Server or Data Center users, see the Viewing your licensed user count section on the Licensing your Jira applications page.

We recommend you use the Jira Cloud Migration Assistant for all your migration needs. The Migration Assistant offers several benefits including Apps and Jira Service Management migrations. We’ll soon support Advanced Roadmaps migrations.

For more information on this announcement, read our community post. For any technical or compatibility concerns with this change, contact us.

First, you'll need to consider whether you're migrating to a new or existing cloud site.

Moving to an existing cloud site

If you have existing site data (anything besides users, groups, and permissions) in Jira Cloud and want to import more data from Jira Server, you'll need to use the Jira Cloud Migration Assistant.

This is because the Jira site import process will overwrite all data associated with projects and replace it with project data from the backup file.

Moving to a new cloud site

If you're migrating to a new cloud site, you can use the standard migration process.

What is migrated

  • Users, groups and permissions

  • Site data, including projects and issues

  • Jira configuration. This includes things like project setup, custom fields, and workflow schemes

  • Custom main handlers

  • Application links

  • Attachments

  • Project avatars

  • Logos

  • Portfolio for Jira. Note that Portfolio features differ in cloud and server, and we recommend including Portfolio for Jira Cloud in your user acceptance testing to understand what differences your users can expect after migrating

What isn't migrated

  • The migrator's group permissions. If you're the person doing the migration, you'll need to re-add yourself to your previous groups after migrating

  • Apps. App data is not included in the backup when migrating from Jira Server to Jira Cloud. Some apps do have the capability to export and import their data but you'll need to check with the app developers or their documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed on https://my.atlassian.com/

  • User avatars. Users will need to update their avatars after migrating

  • Passwords. Unless you've set up SSO, users will need to reset their passwords after migrating

  • Timezones. Timezone information on a per-user profile will be lost

  • Users managed by external directories. We recommend using the Jira Cloud Migration Assistant to migrate your data if you have users managed by external directories. If you can't use the Jira Cloud Migration Assistant to migrate all data, consider using it to migrate users only. For example, you can migrate all your Jira users with the migration assistant first and then import your projects through Jira Site import later

More information and support

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

Additional Help