Importing issues

You can import issues into your JIRA Cloud site from existing JIRA Server or Cloud applications. We also recommend using this process to import data from third-party issue trackers that require direct database access (e.g. Bugzilla and Mantis). 

Overwriting existing data

This import process overwrites all existing data and configuration (including cross-application settings) in your JIRA Cloud site. This impacts existing issues and attachments, look and feel configuration, along with users and group memberships. 

On this page:

How to generate a backup file

From another JIRA Cloud site

Follow the steps on Exporting issues to generate a backup file. Then read the import steps below. 

From a JIRA Server instance

Follow the steps on Backing up data to generate a backup. 

  • If you're migrating from JIRA Server 6.4 (and earlier) and JIRA Agile 6.7 (and earlier) to JIRA Software Cloud, you must first upgrade to JIRA Software Server 7.0 or above.
  • From JIRA 4.4 and up, it is recommended that you use the zip that JIRA generates during backup to fully restore your data.
  • JIRA Cloud applications use UTF-8 encoding. If your JIRA instance uses other character encoding methods, you will not be able to import JIRA Server data to JIRA Cloud applications.

 

From a third-party issue tracker

Check out Migrating from other issue trackers to find out more about built-in importers and importing data from CSV. 

How to import a backup file

  1. Make sure your backup file has a similar structure to:

    JIRA-backup-20161021
    ├── activeobjects.xml
    ├── entities.xml
    ├── data
    │   ├── attachments
    │   └── avatars
    └── logos

    Note that importing entities.xml and activeobjects.xml will overwrite the database in your JIRA Cloud site. Importing the attachments, avatars, or logos files will overwrite any existing attachments, avatars, or logos in your JIRA Cloud site, respectively. 

  2. If you don't want to import issue attachments, user avatars, or project logos, unzip your backup file, remove the corresponding directory, and zip up the modified file. 

  3. Choose > System
  4. In the Import and Export section, click JIRA Import and follow the steps to upload your backup file. This process checks URLs in the specified XML backup, and will let you choose whether or not to update URLs to point to the new JIRA Cloud application.

After the import

Granting application access to new users

The import process does not honor the default application access settings and does not give access to any applications to new users. You must grant application access to these users for them to be able to log in.

For information on how to assign application access, see Manage application access.

Setting permissions

This process imports global permission settings such as Browse User; however, imports from JIRA Server to JIRA Cloud will not contain the JIRA System Administrators global permission (which doesn't exist in JIRA Cloud) and will not contain any changes made to the JIRA Administrators global permission. 

Application permissions are managed in each application individually. You can configure the JIRA Administrators global permission after the import by adding groups and users as needed. If your site has other cloud applications, e.g. Confluence or Bamboo, refer to Manage application access for information on how to configure permissions.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport