---
title: "Migration process"
canonical: "https://support.appfire.com/space/CMT/198020736/Migration%20process"
format: markdown
---
> Macro (aura-html)

## Migrations to Jira Cloud

You can migrate your projects and issues from Jira Server/Data Center instances to destination Jira Cloud sites by pairing the *Cloud Migration Tool* and *Configuration Manager for Jira Cloud* apps. 

> ℹ️ **What Jira configuration do we migrate?**
> ℹ️ 
> ℹ️ Check out the [Supported Configuration Elements](https://appfire.atlassian.net/wiki/spaces/CMT/pages/197856608) document for a complete list of the configuration element types that the Cloud Migration Tool can migrate.

![image](media://e61cc708-21e7-46fc-b402-1d7bf20e3d08)

## Create your first cloud connection

When you open the **Move to Jira Cloud** home page for the first time and don’t have any connections to Jira Cloud sites yet, you’ll be able to quickly create your first-ever connection.

The **Create cloud connection** option allows you to connect to a Jira Cloud site without leaving the *Manage migrations* page. Then, you can proceed to a migration creation without switching pages - a single place to kick-start your instance transfer. Check out the [Cloud Connections](https://appfire.atlassian.net/wiki/spaces/CMT/pages/197856330) document to learn more about creating cloud connections.

![image](media://3bf93c2d-b8c1-407b-8b0d-60d829ba3187)

## Migration reports

We’ve added three reports with summarized information on your past and current migrations on top of the **Manage migrations** page:

- The **Projects **report shows the number of migrated, not migrated, and in-progress project migrations.
- The **Issues **report shows the number of migrated, not migrated, and in-progress issue migrations.
- The **Last migration **report displays information about the last successful migration: the projects and issues migrated during the last migration and its duration.

## Create migrations

**To create migrations to Jira Cloud sites:**

1. Log in as a user with the **Jira System Administrators **[global permission](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/) to your Jira Server/Data Center instance.
2. Choose the **cog icon **at the top-right corner of the screen, then choose **Configuration Manager.**
3. Open the **Move to Jira Cloud** page from the left-side menu.
4. **Create**: Click on the **New Migration** button on the page to create a migration.   
The first thing you’ll see is the *Connect* step of the migration wizard:
5. **Connect**: Name your migration and choose a Jira Cloud connection if you already have previously created one. Otherwise, click the **New connection** or **+** button to create a new one.   
[Learn more](https://appfire.atlassian.net/wiki/spaces/CMT/pages/197856330) about creating cloud connections and the Atlassian credentials you need to provide.
6. After you have named your migration and created/chosen a connection, click the **Select **button to move to the next migration phase.
7. **Select projects**: On the **Select **step of the wizard, click **Add projects to the migration** and select projects from the current Jira instance.
8. **Select boards ***(optional)*: You can also click the **Add boards **button next to the *Boards *section. This option will allow you to select boards outside (unrelated to) the selected projects and add them to the migration.
9. **Analyze**: Click **Analyze **to move to the next phase of the migration.
10. In the **Analyze **phase, review what will be added to and modified on the cloud - projects, configuration elements, and users. You'll be informed about problems or conflicts between the source and destination projects, configuration elements, and users. The analysis will show an error message with detailed information about the detected problem. [Learn more about the analysis process.](https://appfire.atlassian.net/wiki/spaces/CMT/pages/197856449)
11. If you have configuration errors or conflicts, you need to review and resolve them first. Then rerun the analysis.
12. **Migrate**: After resolving all errors and rerunning the analysis, click the **Migrate **button to run the migration.
13. Review the result of the migration. Click the **Access Report **button to review what exactly has been migrated.   
You can also check if any warnings and errors have been encountered during the migration of issues and issue links. [Learn more about the report](https://appfire.atlassian.net/wiki/spaces/CMT/pages/197824716).