---
title: "Migration to Cloud"
canonical: "https://help.releasemanagement.app/space/RM4J/1643544577/Migration%20to%20Cloud"
format: markdown
---
> Macro (include)

# Quick intro

If you are considering to migrate your Jira instance to Cloud we we would be happy to introduce our [Release Management: Workflows, Calendar & Roadmaps - Cloud](https://marketplace.atlassian.com/apps/1221946/release-management-roadmap-jira-cloud?hosting=cloud&tab=overview) App. 

This post is mainly about “How to migrate?” and “What is the difference?” so you can make an educated decision about migration strategy if applicable.

Let’s start with so quick Q&A.

# FAQ about Cloud App

| **Question** | **Answer** |
| --- | --- |
| Is it secured? | Yes, we are Cloud security Participant in collaboration with Atlassian & Bugcrowd where 300+ researches are continuously trying to breach our security.<br>As a result of this effort and meting reliability and resilience requirements we are now [Cloud Fortified ](https://www.atlassian.com/trust/marketplace?source=app-tile-badge)by Atlassian.<br>Also please check [https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441/Data+Processing+Addendum+DPA#EXHIBIT-B:-Technical-and-Organizational-Security-Measures](https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441/Data+Processing+Addendum+DPA#EXHIBIT-B:-Technical-and-Organizational-Security-Measures)<br>*We are SOC2 Type 2 compliant with a commitment to carry on at least till Oct’27. * |
| Did they find any vulnerabilities? | Yes, a number items were reported. All of them are fixed on timely manner. We have a practice in place to communicate within 48hours any P1 and P2 items found and our action to eliminate. |
| Where the data is stored? | **As of November 14, 2025**<br>We are a hybrid App with a fraction of data stored with Atlassian and a great part is still stored in AWS (US, East). We expectation is to be fully [Runs on Atlassian](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3496902657) by Q4’26.<br>**As of September 14, 2024**<br>Distributed cluster in AWS (US, East)<br>**Till September 14, 2024**<br>Distributed cluster in two location in Europe (Germany, Finland).<br>**Backups**<br>AWS (US, East), but also backups in AWS (Frankfurt, Germany). |
| Is it GDPR/CCPA compliant? | Yes, please check [https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441](https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441) |
| The biggest client tier using the App?<br>(performance concerns) | 16000 (as of 6/23/2026) |
| **Is there any automation migration tool?** | <span style="color: #006644">**Yes**</span>, please check [https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/4146659330](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/4146659330) |
| Functionality is the same or different? | Both. Core functionality is the same. There’s approx. 10% deviation in features. Some are pending development for another App. Others - we do not have plans to migrate. [See below](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1643544577/Migration+to+Cloud#Functionality-parity). |
| Do you plan to abandon Server Apps? | > ℹ️ **Update: **Server is EOL.<br>Nope, not at all. We have single code base for Server and Data Center and we actually keep on investing in the Apps as the segment is keep on stable. So, while Atlassian allows upgrade of Server versions … clients will be receiving the same builds we are preparing for DataCenter edition.<br>Read more here: [https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/2573828097](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/2573828097) |

# More details

> Macro (toc)

## Migration Options

As of now (June 23rd, 2026) we started to offer a migration buddle to help automate the migration process to a great extent. But we would still suggest explore all the options below to decide on your migration strategy.

**Note: **Any automated migration assumes an element of manual copy past that could not be avoided.

### Manual Migration

If you do not have too many boards or your boards configurations are not complex it might be way easier to re-create boards after you migrate Jira data. This might be also a perfect opportunity to clean unnecessary boards, review access, review configurations, etc. 

### Automated Migration

As of now (June 23rd, 2026) we started to offer a migration buddle. Please check the below section of documentation to verify it suits your migration use case:

[https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/4146659330](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/4146659330) 

The automated script is predominantly based on the guide referenced in the following sections of documentation, but also here:

[https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/3196387331](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/3196387331) 

### Migration with scripts created by your team with our support

If for some reason our script does not work for your use case you can re-create it using the following guide 

[https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/3196387331](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/3196387331)  

and API-to-API migration approach. Both Apps have REST API available.

***Data Center App:***

![image](media://c7bf97c6-db34-42e4-8b7d-adcbaeca74d2)

![image](media://915ba64b-a100-46a8-8aea-31e2369dd931)

> ℹ️ More details about Rest API for Datacenter App could be found here: [https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347)

***Cloud App:***

![image](media://b1e4977f-754d-4cbc-a237-a9ad95bbf7d5)

![image](media://1e5478a6-6bc8-40a5-9ee1-f32efd17ab94)

> ℹ️ More details about Rest API for Cloud App could be found here: [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2445246483](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2445246483)

***Will API cover all our migration needs?***

When it comes to APIs we eat our own dog food and use the same API to build frontend of our Apps. So for sure you can use both to retrieve the information you want to migrate and create it with Cloud App.

### Migration with support of Solution Partner

We have couple of Solution Partners that completed migrations recently for a number of our Enterprise Clients. They have some pre-created scripts as well so it should be way easier. Happy to make introductions to elaborate on details. We are also happy to collaborate with your existing Solution Partner to supervise you/them on migration path.

### Annex: Migration of Gadgets

#### Automated migration of Gadgets is not supported

As of now (Nov 17th, 2023) Jira Server/Datacenter to Cloud Migration tool does not support Jira Dashboards and Third Party Gadgets (Partner Gadgets) migration described in this feature request [https://jira.atlassian.com/browse/MIG-164](https://jira.atlassian.com/browse/MIG-164). That’s why we have equipped you with the following tips to help you with the manual migration of gadget configurations.

#### Assistance with manual migration of Gadgets

Once you migrated your Jira data from Server/Datacenter to Cloud, you need to manually recreate gadgets and their configurations. First, however, you need to know what gadgets were added to which dashboards.

You can fetch that information using SQL queries run in your Jira database.

> ℹ️ SQL snippets have been tested in Postgres and MySQL databases but should work in all other Jira-supported databases either as is or with minimal modifications.

##### List of Dashboards where Release Gadgets are used

**Postgres**

```sql
SELECT jira.baseurl || '/secure/Dashboard.jspa?selectPageId=' || pp.id as "dashboard_url",
       pp.pagename as "dashboard_name",
       pp.username as "dashboard_owner",
       count(pc.id) as "gadget_count"
FROM portletconfiguration pc,
     portalpage pp,
     (select propertyvalue "baseurl"
      from propertyentry PE join propertystring PS on PE.id=PS.id
      where PE.property_key = 'jira.baseurl') "jira"
WHERE pc.portalpage = pp.id
  AND pc.gadget_xml LIKE '%release-management%'
GROUP BY pp.id, jira.baseurl
ORDER BY "gadget_count" DESC;
```

**MySQL**

```sql
SELECT concat(jira.baseurl, '/secure/Dashboard.jspa?selectPageId=', pp.id) as "dashboard_url",
       pp.pagename as "dashboard_name",
       pp.username as "dashboard_owner",
       count(pc.id) as "gadget_count"
FROM portletconfiguration pc,
     portalpage pp,
     (select propertyvalue "baseurl"
      from propertyentry PE join propertystring PS on PE.id=PS.id
      where PE.property_key = 'jira.baseurl') as jira
WHERE pc.portalpage = pp.id
  AND pc.gadget_xml LIKE '%release-management%'
GROUP BY pp.id, jira.baseurl
ORDER BY "gadget_count" DESC;
```

**Result column / value details**

| **Column** | **Value** |
| --- | --- |
| dashboard_url | dashboard url that can be used for quick access to dashboard in the browser |
| dashboard_name | dashboard name |
| dashboard_owner | dashboard owner (Jira user name) |
| gadget_count | number of gadgets on the dashboard |

##### List of Release Gadgets that are used across all Dashboards

**Postgres**

```sql
SELECT substring(pc.gadget_xml, 'gadget/gadgets/(.*).xml') as "gadget_type",
       count(pc.gadget_xml) as "gadget_count"
FROM portletconfiguration pc,
      portalpage pp
WHERE pc.portalpage = pp.id
  AND pc.gadget_xml LIKE '%release-management%'
GROUP BY pc.gadget_xml;
```

**MySQL**

```sql
SELECT trim(trailing '.xml' from substr(pc.gadget_xml, length(substring_index(pc.gadget_xml, '/', 6))+2)) as "gadget_type",
       count(pc.gadget_xml) as "gadget_count"
FROM portletconfiguration pc,
     portalpage pp
WHERE pc.portalpage = pp.id
  AND pc.gadget_xml LIKE '%release-management%'
GROUP BY pc.gadget_xml;
```

**Result column / value details**

| **Column** | **Value** |
| --- | --- |
| gadget_type | Type of gadget:<br>- `progress-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Progress-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Progress-Gadget))
- `universal-progress-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Universal-Progress-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Universal-Progress-Gadget))
- `release-status-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Release-Status-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Release-Status-Gadget))
- `scope-change-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Scope-Change-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Scope-Change-Gadget))<br>- `burnup-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Burnup-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Burnup-Gadget))
- `trends-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Trends-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Trends-Gadget))
- `release-calendar-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Release-Calendar-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Release-Calendar-Gadget))<br>- `milestone-report-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Milestones-Report-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Milestones-Report-Gadget))
- `release-notes-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Release-Notes-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Release-Notes-Gadget))
- `environment-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Environments-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Environments-Gadget))
- `timeline-gadget` ([https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Roadmap-Gadget](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350/Gadgets+for+Dashboards+and+Confluence#Roadmap-Gadget)) |
| gadget_count | number of gadgets |

Any assistance you might need on the way please contact our [support team](https://releasemanagement.atlassian.net/servicedesk/customer/portal/11).

## Functionality parity

### Core functionality

| **Data Center App** | **Cloud App** |
| --- | --- |
| [Release Boards](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081365) | [Release Boards](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92078287) |
| ["Packages"](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081376) | [“Packages“](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/193953846) |
| Could be done via ["Packages"](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081376) with [Versions Sync](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081376/Use+packages+on+board#Synchronizing-versions-in-the-package) turned on | [Cross-Project](https://help.releasemanagement.app/space/RMC/92143812/FAQ+&+Troubleshooting+the+App#Can%E2%80%99t-see-%E2%80%9CRelease-Management%E2%80%9C-in-Apps-section) versions |
| [Virtual Versions](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081359/Use+versions+on+board#Virtualversion) (Epics and JQL based) | [Virtual Versions](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92111031/Managing+Versions+on+Release+Board#Virtual-version) (Epics, <span style="color: #006644">**Sprints**</span> and JQL based) |
| [Kanban-like](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081359), [Roadmap](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081373), [Calendar](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1294041133) and [List](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/2909962241) views | [Kanban-like](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92111031), [Roadmap](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/527204353), [Calendar ](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/1313275908)and [List](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2491646279) views |
| [Release Notes](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081356) | [Release Notes](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/348389377) |
| [Environments](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1605636) | [Environments](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/415956993) |
| [Track source code changes](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/18219115) | [Track source code changes](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/18219115) (plus <span style="color: #006644">**Builds and Deployments**</span>) |
| [Reports ](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081369)and [Gadgets](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081350) | [Insights ](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/478314497)and [Gadgets](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/458522625) |
| [Custom Properties](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/2459172921) | [Custom Properties](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2464579589) (plus <span style="color: #006644">**User Type, Filters by Properties, Properties in Hooks, Release Notes**</span>) |
| [“Release Management“ panel for Jira Issues](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/2457075787) | [“Release Management“ panel for Jira Issues](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2444656739) |
| [Web Hooks](#) on status change only | Full scale [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2776137753](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2776137753) |
| [Rest APIs](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081347) | [Rest APIs](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2445246483) (with [Personal API Access Tokens](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3168108545) available) |

### Data Center only

| **Data Center App** | **Cloud App** |
| --- | --- |
| [Custom JQL functions](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1703945) | 3rd party JQL functions are not supported by Jira Cloud Platform. No workarounds available. |
| [Milestones Report](https://releasemanagement.atlassian.net/wiki/spaces/RM4J/pages/1081369/Reports+Insights#ReleaseMilestonesReports) | no plans so far |
| Export Gadgets to Confluence | 3rd party Gadgets are not supported by Jira Cloud  Platform. There’s a workaround via [Wallboards](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/458522625/Dashboard+Gadgets#%F0%9F%A4%A9-Exporting-Gadgets-to-Confluence) functionality. |
| Assignee & Watchers (plus notifications via email upon changes made to versions/releases) | Could be partially covered with [Custom Properties](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2464579589) of User Type (no notification is enabled out of the box, [automation](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2776137753) should be used instead) |
| Statistics by Issue Count, Story Points and Ideal Hours | Statistics by Issue Count only as common denominator |

### Cloud only

| **Data Center App** | **Cloud App** |
| --- | --- |
| No plans so far | [Package Templates](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/1493008448) |
| No plans so far | [Non-working Days (Blackout Periods)](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92078312/Configure+Release+Board+Settings#Blackout-Periods-(Non-working-Days)) |
| Swimlanes (Packages for Board view and Packages, Projects for Roadmap view) | [Custom Swimlanes](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/527204353/Release+Roadmap+View#Swimlanes) (Projects, Packages, Tag & Types across Board and Roadmap views) |
| Predefined color schema | [Custom color codding schemas](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/92078312/Configure+Release+Board+Settings#%F0%9F%86%95-Color-coding-for-releases) |
| No plans so far | Epic start/due dates sync |
| No plans so far | Amend [Environment ](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/415956993)Types and custom Environment swimlanes |
| Not supported by the platform / No plans so far | [Compass Integration](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2506129435) and cross-project [Component Management](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2599616526) |
| Not supported by the platform | [ROVO AI](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3339288577) Agent |
| No plans so far | [Escalated permissions](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2863464452/Permission+Management+for+Jira+Release+Boards#Permissions-for-Non-Admins) (permissions for Non-Admins) |
| No plans so far | **DORA**: [Release Frequency](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3009118209/Advanced+Features#List-of-Advanced-Features) Report & Gadget |
| No plans so far | Collapse header and gain more space |
| No plans so far | Multi select on the Board view and Build operations |
| No plans so far | Hide items older than ... |
| No plans so far | Update versions status upon package move |

We suggest to kick off a trial with Cloud solution before you decide to migrate to check all the features you use in Server/Datacenter versions. Any assistance you might need on the way please contact our [support team](https://releasemanagement.atlassian.net/servicedesk/customer/portal/11).

> Macro (include)