Migrating your instance of Jira Software, Confluence, or another Atlassian product? We’ll guide you through the process.

Atlassian products migration services

If you’re using Jira, Confluence, or another Atlassian tool, you might eventually get to the point when you want to change the server or cloud version of a product or need to actually move your data from one instance to another, or from third-party tools like Service Now and HP to the Atlassian environment. 


Why would you need to do that?

Atlassian encourages using various data migration solutions within its ecosystem. And as Atlassian Solution Partner, Rozdoum is no stranger to providing migration services. We realized it was a common issue when our customers started asking for assistance in data migration. One of the early cases was integrating several Jira instances into a single one. It became necessary after several teams in the company had merged into one large department with their own Jiras in place. Data migrations are also common in the case of mergers and acquisitions, as well as switching from one Jira instance to another.

So far, we’ve worked on various migrations inside the Atlassian environment. We’ve helped teams to move from server products to cloud ones and vice versa, merge several instances into one, migrate between two Atlassian products, or even different products like VersionOne and HP ALM to be more specific.

Diagram of the migration processes:

Assessment and preparation for the migration

Investigating ways of third-party data migration(data of add-ons)

Preparing a UAT planUser acceptance testing

Performing test migration and testing the result

Performing production migration


If you have one of the cloud products, you might need

There are a few options within the same cloud migration service, and they consist of pretty similar steps. During migration, we encourage customers to participate from time to time as it sometimes helps to better optimize processes on the go.
Cloud migration steps are as follows:

  1. Assessment and preparation for the migration
    • analyzing both instance and project setup to detect conflicts
    • suggesting solutions and discussing them with the customer
  2. Investigating ways of third-party data migration (data of add-ons)
  3. Preparing a UAT plan
  4. Performing test migration and testing the results
  5. Performing production migration

Among the most effective approaches to cloud migration are cloud to cloud, cloud to server, and cloud to data center. To better understand which kind of migration you might need, here are specifics for each case.

The three approaches to merge multiple instances of Jira cloud


In case you need to combine data from several Atlassian cloud instances, cloud merge is a service for you. No matter what your working processes were before, how different those instances are, or which changes you want to implement, we can help you define a new structure and workflow for your team before the merge. 

If you decided to take over control of Atlassian products, please make sure you read about Atlassian’s plans for shutting down the server products’ support by February 2024. However, in case you have to follow specific security requirements set by financial, medical, and other industries, you might need to move your cloud instance data to the server. Besides the specified steps, it is essential to see whether all cloud plugins have server versions and if they don’t, find replacements. In case there are no ready-made plugins for the server product you are planning to use, Rozdoum can take care of custom plugin development too. 

Migrating from one Atlassian cloud product to another is not a popular case. However, if you’re not in control of a cloud instance you use or divide your teams into several independent parts, you might need to change your Atlassian cloud instance and perform database migrations.

If you’re growing fast or have recently become a part of an enterprise, Data Center by Atlassian is a good solution. Data Center ensures security and compliance of the company’s data, addresses scalability issues, and allows for advanced data control. It combines several products and provides an easier way to manage the whole infrastructure. We can help you define which products to use, move all the data from your current instances, or introduce you to new products that you might have decided to use in DC.

If you have server products, you might need

Servers migration of Atlassian products was one of the first services we’ve established. What does it take?

  • checking if all product versions are up to date
  • following all the steps described in the cloud-to-cloud migration section, but using the server version of products you have.

However, with the server products, the list of cases for data migration services is a bit wider.

Here, the case might be similar to that of cloud merge. The only difference is that your data is physically located on different servers. We will still need to set up a new instance before backing up the data and importing it from those instances that are being merged.

If you haven’t purchased new Atlassian product versions for a while and need to upgrade the older version, you might face a few challenges when making changes. Our team can help you define the differences, check plugin compatibility with the latest product version you have, and execute data migration as well.

Upgrading Jira 6 to 8 is not directly possible. You need to do iterations step by step. The upgrade path will look like this: Jira and Confluence Pre-upgrade Planning Template

There are cases when you need to migrate or upgrade Atlassian products on a different server. The most common reason for this is the growing issues with your current server. It’s essential to set up a new instance, back up the existing database and home directory, move data to the newly installed instance and re-apply custom modifications. To handle server migration accurately, you might need external help.

With Atlassian planning to support those who’d like to switch to cloud versions, this might be the most popular service for upcoming years. Considering the interface differences and plugin selection, server-to-cloud migration requires more time and effort to prepare for. For example, the migration from Server to Cloud of the following Atlassian tools: Jira Software, Jira Service Management, Confluence can be accompanied by migration of a large number of Apps as Adaptavist Script Runner for JIRA, Checklist, Advanced Roadmaps for Jira  (Advanced Roadmaps plans, Advanced Roadmaps Team Management), Jira Misc Custom Fields, Jira User Export, Nextup JIRA Integration+, ProForma: Forms and Fields for JIRA, Insight, Insight Discovery, Insight SCCM Integration, JIRA Custom Fields,  JIRA Misc Workflow Extensions and much more. 

Here is the case study of the Server to Cloud Migration of Marketplace Apps: Case Study_ Server to Cloud Migration of Marketplace Apps.

The apps in the lists have necessary references to migrate apps from Server to Cloud: how-tos, migration guides, documentation links.

Rozdoum can assist you in this or guide you through the process.

Why Rozdoum?

When choosing a team that is able to handle data merges, it’s important to decide on those who will manage your tasks as their own.

After a few years of supporting our multiple servers, we had to migrate some projects to the cloud. Rozdoum team created custom apps for fast and automated migration and set up workflows within our new Cloud Jira instances. – Barry Cook.

Case studies

Several examples of successful migration should give you additional insight into our service.


Cloud-to-cloud migration:

2 cases with similar issues

View Case

Our customer requested a cloud-to-cloud migration due to the merger and acquisition of 2 educational platforms. Both teams had used Jira Cloud before the merger.

There were challenges with settings migration and the type of projects used. Since migration included next-gen projects, we couldn’t use CSV import. It didn’t work well with the projects of that type, because not all fields were migrated. So if you decide to merge cloud instances into a single server one, next-gen projects won’t exist there.

Another migration case that resulted from M&A had the same issues with next-gen projects. However, with an intermediate migration to Server Jira and then to Cloud Jira, we’ve resolved the task using custom tools for migration automation.

Server-to-server migration

To perform this migration we used the Project Configurator

View Case

To perform this migration we used the Project Configurator app on both Server Jira instances. After setup, we exported all projects with the necessary configurations applied and then imported them to the target server instance. We made a full backup of the client’s target instance’s database including attachments. In order to migrate smoothly and avoid users blocking the process, we moved data out of the client's office hours. It helped us check and validate all issues, detect conflicts, and test the performance of the target instance.

HP ALM to Jira Migration small

HP ALM to Jira migration

View Case

Recently, we’ve helped to migrate customer’s data from HP ALM to Jira. Besides data migration, we’ve also moved test management data to a Jira add-on.

VersionOne to Jira Merge small

VersionOne to Jira migration

View Case

This case required us to move data from VersionOne to Jira and Git. With a number of scripts created, most of the data migration was handled automatically.

So if you’re going to face instance migration or merge, which case is yours? Just choose it in our form below and get a free 1-hour consultation on the best way to handle it. 


If you’re currently running Jira, Confluence, and Bitbucket in server or Data Center and want to move to the cloud version, other instances, or upgrade, leave your details and we will guide you through the process.