Importing and exporting data
Administering Jira Data Center and Server 9.12 applications
- Jira applications and project types overview
- Getting started as an administrator
- Installing Jira applications
- Layout and design
- User management
- Configuring projects
- Importing and exporting data
- Configuring Jira application emails
- Jira system administration
- Jira Data Center documentation
- Performance and scaling
- Security overview and advisories
- Getting help
On this page
In this section
Related content
- How to define a default merge strategy per Project
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Commits missing from Pull Request merge on target branch
- Automatic branch merging
- Understanding Diff view in Bitbucket Server
- Pull Request is automatically marked merged in Bitbucket Data Center and some of the code changes are lost on target branch after performing conflict resolution in a different branch
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Using forks in Bitbucket Server
At times, you may need to import or export data to or from Jira. You may want to import data from another tool (like Github or Fogbugz), another Jira instance, or from a manually prepared file such as a CSV or JSON file. You may want to export your data so that you can perform some manual manipulation on it, or to move a project from one instance to another. This section of the documentation explains how to perform imports and exports of your data. If you'd like more information on backing up your data, and restoring a backup, please refer to the System administration section of the documentation.
Migrating data from other tools
Learn more about ho to import data from various tools. We also have information on how to structure CSV or JSON files for import.
Moving or archiving projects
Learn more about how you can move or archive individual or multiple projects between Jira instances.
Importing to a Cloud instance
In this section
Related content
- How to define a default merge strategy per Project
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- Commits missing from Pull Request merge on target branch
- Automatic branch merging
- Understanding Diff view in Bitbucket Server
- Pull Request is automatically marked merged in Bitbucket Data Center and some of the code changes are lost on target branch after performing conflict resolution in a different branch
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Using forks in Bitbucket Server