Move Projects from Server/Data Center to Cloud

On this page:


Moving projects is one of the most common tasks for Jira Administrators. This document describes how to move projects from Jira Server/Data Center instances to Jira Cloud using Configuration Manager. The described approach can be used for configuration tasks such as merging multiple Jira instances.

The goal is to transfer a project from a Jira On-prem Server/Data Center (Source) to a Jira Cloud instance (Target) fully and transparently with no loss of data or configuration. Note that 3rd party apps, even if they are available for Cloud and Server, will work differently in most cases. Please contact the 3rd party app vendor regarding the migration procedure of the app data.

As a prerequisite, you need to create an additional temporary on-premise Jira Server instance called Temporary Staging Server in this document.



Server→Cloud Migration Architecture

This section illustrates the recommended high-level architecture and phases to move projects between Server/Data Center and Cloud Jira and instances safely and reliably.


~ 3 hours

Jira Cloud

2 Jira Servers* 

Project Snapshot

New Project Mode  




2 Servers are required.  (Temporary Staging) and the Production Server (Target) system.


Step-by-step Instructions

To move projects from Server/Data Center to Jira Cloud:

  1. Restore the Cloud Jira to the Temporary Staging Server, so that the target's configuration is available before you apply the changes from the snapshot.

  2. Create a project snapshot on the Source Jira Server/Data-center instance using Configuration Manager for Jira. Pick the project or projects which you want to move from the on-premises server to the cloud (for more information on how to create project snapshots, check the Project Snapshot and Project Snapshot with Issues documents).

  3. The Temporary Staging Server should use the latest available Jira version, so the cloud can be restored without problems.

  4. Deploy the project snapshot on the Temporary Staging Server using Configuration Manager for Jira (for more information on how to deploy project snapshots, check the Single Project Snapshots and Multi-project Snapshots documents).

  5. Choose one of Configuration Manager's New Project or Merge Project mode during the deployment process and finish the deployment.

  6. Back up the data on the Temporary Staging Server instance (for more information check the Atlassian document Backing up data).

  7. Restore the XML backup to a Jira Cloud instance (for more information check the Atlassian document Restoring data).

  8. (optional) Decommission the temporary server.

For best performance and to avoid potential OutOfMemory errors for large snapshot deployments make sure you increase the Java heap for your Jira. You can use the Jira sizing guide as a reference, and double the heap numbers for very large deployments. A rough guideline is 16-32GB for moving a project/projects with a total of 100 000 issues (attachment files moved separately).


To extend the use case of moving projects from Server/Data Center to Jira Cloud, explore Configuration Manager's functionalities and use cases: