In this page

Migrate from Jira Server/Data Center to Jira Cloud

The Better Excel Exporter for Jira app is available for all three Jira deployment types: Server (legacy), Data Center, and Cloud.

While Server and Data Center share the same app features, the Cloud version is built on a different infrastructure and REST API, which makes it work differently in key areas. This new environment required us to rebuild the app from the ground up, and we used the opportunity to make it even better by applying the knowledge and experience gained from the self-hosted versions.

This guide will help you transition the app from Jira Server/Data Center to Jira Cloud.

How to read this guide

We've broken the guide down into multiple sections. We recommend reading them in this order:

  1. Key changes: Changes enforced by the switch to Cloud platform.
  2. Feature parity: A comparison of equivalent features.
  3. Step-by-step guide: A clear, executable plan for carrying out the migration process.

Key changes

Migrating from Server/Data Center to Cloud involves more than transferring configuration and data. It requires adapting to a platform with different features, even if the core functionality remains the same.

Product changes

The following changes have been implemented to align with the Atlassian Cloud platform's architecture and APIs and to improve the overall user experience. We also used this transition as an opportunity to expand the app's capabilities and introduce new features that weren't possible in the Server/Data Center versions.

Server/Data Center behavior Cloud behavior
Where are the app and its resources located? The app is running on the same server and in the same Java Virtual Machine (JVM) as Jira does. The templates and scripts are saved to the Jira database. The app is running in the cloud, more precisely in an Amazon AWS environment operated by Midori. The templates and scripts are saved to a secure cloud-hosted database.
How can the app communicate with Jira and other Jira apps? Through the public Jira Java API and Jira REST API - inside the same JVM where Jira is running. (It is possible to access non-public Java API if required for your use case.) Through the public Jira Cloud REST API and the integrated app-specific REST API or GraphQL API (if they exist) - over the public internet. (No access to non-public APIs.)

Feature parity

Core features are still available, though their locations and how they work may have changed. This section helps you find and use them quickly.

Server/Data Center feature Cloud feature
Integrations The integrated apps are different. See the Data Center integrations page (Server is the same). The integrated apps are different. See the Cloud integrations page.
REST API Available. See the REST API page. Not available yet. If it would be useful for your team, please vote on the feature request!
Excel view visibility Views can be optionally restricted to certain groups, users or issues (specified by JQL). Views are visible for all users. Restricting views is not available yet. If it would be useful for your team, please vote on the feature request!
Export limits Virtually unlimited. The capacity of your own server sets the limit for exports. The number and the duration of the exports are limited by a quota system. It's a protection for extreme cases. Normal business usage will not be disturbed.

Questions?

Ask us any time.