Exporting issues from Cloud to Server
How to create a backup
You can generate a new backup every 24 hours from the time the previous backup has finished. Note that Jira only stores one backup file at a time, and any existing existing backup will be overwritten by a new one. To generate a backup:
In the upper-right corner of the screen, select Administration
> System. In the Import and Export section, click Backup manager.
Check the additional files option if you want to include issue attachments, user avatars, and project logos in the export.
- Select the type of backup:
- If you will restore the data to a cloud instance, select Create Backup for Cloud
- If you will to restore the data to a server instance, select Create Backup for Server
After the backup is complete, click the file link to download the backup.
How to structure the export file
Once you have generated and unzipped a backup file, you should have an output similar to the following:
Jira-backup-20161021
├── activeobjects.xml
├── entities.xml
├── data
│ ├── attachments
│ └── avatars
└── logosNote that database data is stored in both activeobjects.xml and entities.xml. Issue attachments, user avatars, and project logos are stored in corresponding directories. If you don't want to import attachments, avatars, or logos to your new Jira Cloud site, you can remove the corresponding directory and then zip the modified directory tree before importing.
How to import backup data into Jira Cloud
- Structure your export file as mentioned above.
- Follow the instructions on importing issues.
- After the import, log into your new Jira Cloud site with the same admin account you used to log into your original site. Cross-application links (links to a source file page from a Jira issue) will point back to the corresponding source location after the import.
How to import backup data into Jira Server
- Structure your export file as mentioned above.
- Follow the instructions on the Migrating from Jira Cloud to Jira Server page.
- After the import, log into your Jira Server instance with the sysadmin username and corresponding password. Make sure to change your password after you log in. Cross-application links (links to a source file page from a Jira issue) will point back to the corresponding source location after the import.
Note that the sysadmin user is created automatically during the backup process. This user is created to allow you to log in with the necessary Jira System Administrator permission (a server-specific permission not available in the cloud) after restoring data in Jira.