Free app
OVERALL RATINGS
INSTALLS
Preinstalled
SUPPORT
- Partner Supported
Key highlights of the appThe best way to move everything you need from Jira Server or Jira Data Center to Jira Cloud
Supporting media
More details
Jira Cloud Migration Assistant (JCMA) is the official tool for migrating from Jira Data Center to Jira Cloud. Watch this demo for a data migration overview, and this demo on app assessment.
Requirements:
- Jira Data Center 7.6 or later
- A Jira Cloud site âÃÂàstart a free cloud migration trial if needed
- JCMA 1.7.1 and older are unsupported
Key points:
- Review the server-to-cloud migration guide
- From v1.12.50, JCMA bundles the Portfolio Insights: Data and metrics app, collecting ID-based operational data to assess cloud-migration readiness. Only activates once connected to Portfolio Insights.
When to use: migrating to Jira Cloud, or when Atlassian Support recommends it.
See the Atlassian Cloud Roadmap for what's coming.
Resources
Download
Get the .jar file downloaded to your system
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is applicable to the use of this app.
Atlassian privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Version information
Version 1.15.0•for Jira Data Center 8.0.0 - 11.3.7
- Release date
- Jul 2nd 2026
- Summary
- Improved migration reliability, performance, and error recovery
- Details
Version 1.15.0 makes Jira migrations more reliable and easier to recover when problems occur. Large and clustered Jira Data Center instances now experience less rate-limiting during migration, with smarter retry behaviour for transient network errors during preflight and attachment uploads. Attachment migration is faster, and missing attachments are now clearly reported. Several bugs have been fixed: exports no longer fail on duplicate custom field rows, complex JQL filters with history clauses now migrate correctly, and Advanced Roadmaps team exports no longer produce broken imports. The remediation workflow is stronger — paused migrations resume more reliably, cross-project errors are correctly retried, and import-phase rich text validation catches errors earlier. Asset exports are faster with batch fetching and parallel processing. Scoped user migration now correctly collects all group references. Security hardening has been applied to file access paths.
- Payment model
- Free