How to migrate from Jira Server to Cloud with CMJ

It’s happening! As of February 15, 2024, the support for the Atlassian Server products is coming to an end. Atlassian will no longer sell Server licenses, and they’ll end support for Server products. Meaning that a Jira server-to-cloud migration is essential.

Transferring your data might seem risky and complicated. But there’s plenty of help available. You can find a partner to support you with expert help, online guides that provide step-by-step instructions, and apps that streamline the migration process.

In this article, you’ll learn how to migrate a Jira instance from Server to Cloud using Configuration Manager for Jira (CMJ). With CMJ, you can choose projects and initiate and track migration processes. 

What are the benefits of using Configuration Manager for Jira (CMJ) to migrate Jira Server to Cloud?

No matter how big or complex your migration might be, Configuration Manager for Jira (CMJ) can handle it. Using CMJ, you can:

• Move projects all at once or in phases
  Some teams at your company may be ready to migrate now, while others need more time to prepare. With CMJ, you can select projects that are ready to migrate now, and then come back to the others later.
• See the impact of proposed changes before you make them
  Once you select projects you want to migrate, the app analyzes your proposed migration plan and provides a tally of the configuration changes by type.
• Easily resolve errors or rename configuration elements
  CMJ’s analysis process identifies and explains any errors that might arise from your proposed migration. Use built-in tips to fix these problems before migrating. And you can rename project names/keys and workflows, and customize user mapping with a CSV upload — all from one screen!
• Perform smart migrations with deep configuration support
  CMJ is optimized to intelligently evaluate platform data and only migrate what’s different. The app supports large data sets and a vast range of configuration settings, like notification schemes, deeper workflow support, and more. 

Before you start your migration from Jira Server to Cloud, you’ll want to have your proverbial ducks in a row. We’ve prepared a handy checklist for you.

How to migrate Jira projects from Server to Cloud

Below, you’ll find a brief instruction manual for migrating your Jira projects from Server to Cloud.

Before you start your migration, install a free companion app on the server: the Configuration Manager Cloud Migration Tool. You’ll need an active license of Configuration Manager for Jira (CMJ) on your Cloud instance. You’ll also need site admin or org admin permissions in order to establish a connection between the Cloud Migration Tool and CMJ.

Once that’s ready, you can log in to your Jira Server or Data Center and open the Cloud Migration Tool's Manage Migrations page. (You can find this by clicking "Move to Jira Cloud" under Configuration Manager.)

Then, you create a migration with the “New Migration” button. Once connected, you can name your migration and connect to your Jira Cloud site.

Next, select the projects you want to migrate using the “Add Projects” button to the migration link. Click the “Add Boards” button to include boards that aren't associated with the selected projects to the migration scope.

Once you’ve added your projects and boards, move to the Analyze Changes phase and review the report of any changes introduced to the Cloud.

Once you’ve verified and checked any warnings, errors, or conflicts between the server and cloud configurations detected by the analysis, you can recheck it by clicking the “Rerun Analysis” button. Then, when you’re ready, run the migration.

PRO TIP: You can use Power Admin to clean up your source instance and CMJ on server to consolidate multiple server instances before migrating to the Cloud.

• Power admin: Identify duplicate configurations and merge them together; search the configurations by name or type, and identify configurations that aren’t in any projects and can, therefore, be removed easily (See documentation.)
• CMJ: Move entire projects from one instance to another. This helps you consolidate multiple instances at your organization, and streamlines purchasing and administration of Jira when moving to DC or Cloud ( See documentation)

Once your migration is complete, you can review a full report of migrated projects and configurations. On the final page of the migration, click the “Access Report” button to see the report and navigate to your Jira Cloud site to browse your projects, issues, and workflows.

When you’re ready, invite your teams to Jira Cloud.

An alternative: Jira Cloud Migration Assistant (JCMA)

If you’re looking for a free alternative, you might check out Atlassian’s native Cloud migration solution for Jira: Jira Cloud Migration Assistant (JCMA). JCMA works best for teams that are on a super tight timeline and are willing to skip CMJ’s thorough analysis. JCMA does enable you to do some cleanup and optimization of your instance before migrating, but you’ll need more careful planning before undertaking your migration using JCMA.

JCMA vs. CMJ

PRO TIP: For some migrations, JCMA and CMJ work even better together. If you could use some help figuring out the right approach for your migration, get some advice from Appfire and our network of trusted partners.

Migrate from Jira Server to Cloud with Appfire

Some migrations are complex, sure. But that doesn’t mean they can’t also be efficient and stress-free! Appfire is here to support you throughout the migration process. If you’re looking for expert advice on migration from Jira to Cloud, help yourself to a copy of our Ultimate Guide to Jira Migrations.

Wishing you a smooth migration. May your data never be lost, and your configurations remain unbroken!