What gets migrated with Jira site import

We’ve replaced the Restore system screen (also commonly referred to as Site Import) with the Import Jira Cloud and Import Jira Server screens.

Now, to import Jira Server backups:

Click Jira Settings > System.
In the Import and Export section, click Import Jira Server.

To import Jira Cloud backups:

Click Jira Settings > System.
In the Import and Export section, click Import Jira Cloud.

Site Import will no longer be available for Server to Cloud migrations

From May 1, 2022, we’ve discontinued Server to Cloud migrations using Site Import if you’re looking to migrate 1-1000 users. If you’re looking to migrate 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, Jira Service Management, and Advanced Roadmaps migrations.

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

Jira Cloud Migration Assistant now supports ‘all data at once’ migrations

Jira Cloud Migration Assistant 1.7.7 allows you to migrate all data at once, in addition to the existing project-by-project migration capability.

The migrate all data at once feature in the Migration Assistant will migrate the same types of data that Site Import currently supports.

Future Migration Assistant releases will increase the reliability and performance of migrating all data at once, as well as the types of data migrated.

For more information on this announcement, read our Community post.

Only use Jira site import if you are importing data into a new Cloud site. Existing data on a Jira Cloud site (except for users, groups, and permissions) will be overwritten by a Jira site import process.

If you have existing data in your Jira Cloud site and want to import more data from Jira Server or Data Center, you can use the Jira Cloud Migration Assistant. Learn more about the Jira Cloud Migration Assistant

What is migrated	What isn’t migrated
Users, groups and permissions Site data, including projects and issues Jira configuration, including 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 Server and Cloud. We recommend including Portfolio for Jira Cloud in your user acceptance testing to understand what differences your users can expect after migrating. Learn how to test your migrations	The migrator's group permissions: If you're the person performing the migration, you'll need to re-add yourself to your groups after migrating Apps: App data is not included in the backup when migrating from Jira Server to Jira Cloud. Some apps have the capability to export and import their data but you'll need to check with the app vendors or their documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed on https://my.atlassian.com/ 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. 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

What is migrated

What isn’t migrated

Users, groups and permissions
Site data, including projects and issues
Jira configuration, including 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 Server and Cloud. We recommend including Portfolio for Jira Cloud in your user acceptance testing to understand what differences your users can expect after migrating. Learn how to test your migrations

The migrator's group permissions: If you're the person performing the migration, you'll need to re-add yourself to your groups after migrating
Apps: App data is not included in the backup when migrating from Jira Server to Jira Cloud. Some apps have the capability to export and import their data but you'll need to check with the app vendors or their documentation to confirm if this is possible. Your licenses for Atlassian Marketplace apps can be viewed on https://my.atlassian.com/
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.
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

More information and support

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

for migration planning information, visit the Atlassian Migration Program website
for technical issues or support with strategy and best practices, get in touch with our support team
for peer advice, ask the Atlassian Community
for expert guidance, work with an Atlassian Partner

Was this helpful?

It wasn't accurate

It wasn't clear

It wasn't relevant

Atlassian Support

What gets migrated with Jira site import

What is migrated

What isn’t migrated

More information and support

Additional Help