---
title: "Detailed reports of successful migrations"
canonical: "https://support.appfire.com/space/CMT/197824716/Detailed%20reports%20of%20successful%20migrations"
format: markdown
---
> Macro (aura-html)

## Review a report on a successful migration

Having complete information about which configurations have been [migrated to the cloud](https://appfire.atlassian.net/wiki/spaces/CMT/pages/197922405) is essential to any Jira administrator. 

When a migration finishes successfully, Cloud Migration Tool offers a report listing all the migrated configuration elements and any encountered warnings and errors. You’ll find it under** Migration report **on the final **Migration complete** page.

**To view the report of a successful migration:**

1. [Start a migration](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=cmt&title=Migrations&linkCreation=true&fromPageId=197824716) from a Jira Server/Data Center instance to a Jira Cloud site.
2. After the migration finishes, click **Migration report >** **Access report** on the last **Migration complete** step.
3. The [Cloud Migration Tool](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=cmt&title=Concept&linkCreation=true&fromPageId=197824716) will show you a **report **of the configuration uploaded to the cloud. The report allows you also to review any warnings and errors encountered during the migration of issues and issue links.

### Report about migrated app data

The **Migration report** will also include information about any migrated app data. If an app has integration with our [Service Provider Interface (SPI)](https://appfire.atlassian.net/wiki/spaces/AppIn/pages/197858713) for [server-to-cloud app data](https://appfire.atlassian.net/wiki/spaces/AppIn/pages/198378055) migrations, it will be migrated to the cloud. Inside the **Migration report, **there’ll be a section called **App Migrations** listing the migrated data for each app.

The **App Migrations **report always lists the app name, migrated configuration, and a summary of the migration. The report optionally may also include any errors and warnings encountered during the migration and/or a link to a custom report generated by the app. However, this optional information depends on the vendor's reporting choice set in the integration of the app with the [SPI](https://appfire.atlassian.net/wiki/spaces/AppIn/pages/197858713).

See how the report might look if a single app workflow has been migrated:

| **Jira Misc Workflow Extensions (JMWE) migration** |
| --- |
| Workflow | THE_NAME_OF_THE_WORKFLOW |
| Summary | <span style="color: #6554c0">Operation with ID 1324324546HGKH767 finished with problems. </span>  
<span style="color: #6554c0">Check the reported errors and warnings below.</span> |
| App migration report | <span style="color: #0747a6">View report (link to the report)</span> |
| Migration errors | Error 01: We didn’t update the workflow |
| Migration warnings | Warning 01: No transition with id 55 found<br>Warning 02: User with id 1212123-123123123-123123123-12312123 doesn’t exist on the system |

> ℹ️ Remember that the **App migration report**, **Migration errors **and **Migration warnings **fields are optional. They depend entirely on the information provided by the app throughout the migration.