> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/server-to-cloud-migration/server-to-cloud-automatic-migration-tool/doing-the-migration.md).
# Doing the migration
Email This Issue uses Atlassian’s **Jira Cloud Migration Assistant** for the migration. For information on how to use this tool, please refer to the [Atlassian Cloud migration guide](https://www.atlassian.com/migration/plan/cloud-guide#introduction).
#### 1. In the *Assess your apps* phase select the *Needed in cloud* option for Email This Issue.
Assess your apps phase
#### 2. In the *Prepare your app* phase - *Install your apps* step make sure Email This Issue is installed on your Cloud site:
#### 3. Wait for the migration to complete
There are three stages of the migration progress:
* **0% - 49%** The migration has started and is in progress on the On-prem side or it is being transformed. This step might take from a couple of seconds to even a couple of hours depending on the amount of emails being moved from the On-Prem to the Cloud.
* **50% - 99%** The migration is in progress and data is being imported into the Cloud instance
* **100%** - The migration is finished. The result of the migration could be either **Success** or **Failed**.
Apps page
## Troubleshooting
During the migration, it might be the case that you see the following message:
{% code overflow="wrap" %}
```
Import finished, however there was an error during the import of manual email permissions. Please review 'Send Issues in Email' permissions in your Permissions Schemes.
```
{% endcode %}
This means that your configuration and operational data imports are finished successfully, but there was a problem when importing the permissions to send emails manually.
{% hint style="warning" %}
If you are using your Cloud instance with a free plan, the import of the permissions will always fail, because free Jira plans don't grant access to the permission schemes.
{% endhint %}
You should check it in the Jira Permission Schemes that all manual email permissions that were created prior to the migration are removed and you should add every permission that was configured in your On-prem installation to every active Permission Scheme in your Cloud instance.
On the On-prem side, you can find these settings under the P**ermissions and Condition for Sending Emails Manually** section of the **General Configuration** settings.
If you need help on how to configure permissions on your Cloud instance, please refer to our [Permissions](/email-this-issue/administration/email-this-issue-for-jira-cloud-permissions.md) documentation.
In case of any other error, please [contact our support team](https://metainf.atlassian.net/servicedesk/customer/portal/1) with the following information:
* The **transfer ID** of the migration (shown in the error message)
* The target Jira Cloud URL
* The date and time of the migration (including the timezone)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.meta-inf.hu/email-this-issue/server-to-cloud-migration/server-to-cloud-automatic-migration-tool/doing-the-migration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.