Move Projects from Cloud to Server/Data Center

On this page:


Moving projects is one of the most common tasks for Jira Administrators. This document describes how to achieve the use case of moving projects between Jira Cloud and Server/Data Center instances using Configuration Manager. The described approach can be used for consolidating efforts such as merging multiple Jira instances.

The goal is to transfer a project from the Jira Cloud server (Source) to a Jira On-prem Server/Data Center (Target) fully transparently with no loss of data or configuration. Note that 3rd party add-ons even if exist on Cloud and Server will work differently in most cases, please contact the 3rd party add-on vendor regarding the migration procedure of the add-on data.

As a prerequisite, you need to create an additional temporary on-premise Jira Server/Data-center server.



Cloud→Server Migration Architecture

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

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


~ 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 Cloud to Server/Data Center:

  1. Back up the data on the Cloud instance (for more information check the Atlassian document Backing up data). Make sure that you create a backup for Server, not for cloud. See more below.

  2. Restore the XML backup to a Temporary Staging Server (for more information check the Atlassian document Restoring data).

  3. Create a project snapshot on the Temporary Server using Configuration Manager for Jira. Pick the project or Projects which you want to move to the on-premise server (for more information on how to create project snapshots, check the Project Snapshot and Project Snapshot with Issues documents).

  4. Deploy the project snapshot on the Production 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 Configuration Manager's New Project mode during the deployment process and finish the deployment.

  6. (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 32GB for moving a project with 100 000 issues (attachment files moved separately).


Backup Manager on Jira Cloud instance.


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