> 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/preparing-for-the-migration.md).
# Preparing for the migration
There are two parts of preparing for the migration:
1. [On-prem prepare steps](#on-premise-prepare-steps)
2. [Cloud-side preparation](#cloud-side-preparation)
It is essential that you follow the process carefully and not miss any of the steps. If at any time you run into problems, reach out to our [support team](https://metainf.atlassian.net/servicedesk/customer/portal/1) and send us as much information as possible, including screenshots and an explanation of what happened.
## On-premise prepare steps
#### 1. Download and install the latest version of Email This Issue.
{% hint style="info" %}
Please note the current application versions and related compatible Jira versions, supporting migration:
Email This Issue 9.24.2 + Jira 9.x
Email This Issue 10.0.6 + Jira 10.x
Email This Issue 10.2.1 + Jira 11.3
Email This Issue 10.4.0 + Jira 11.3 - 11.3.7
To ensure that the migration can be completed successfully, please make sure that your app version is listed above and your Jira version is in line with your current app version
{% endhint %}
#### 2. Remove any configuration that you don’t want to migrate to the cloud.
#### 3. Disable every Incoming Mail Connection.
{% hint style="warning" %}
After you start the migration, all new incoming emails (both created with Jira and/or with Email This Issue that you would process with Email This Issue on the On-prem version) and their processed data will not be migrated to the Cloud as the process is already running.
{% endhint %}
If you have Incoming Mail Connection created with Jira it should be disabled as well.
#### 4. Clean up your Incoming Mail Queue
Check if there are any important emails in the **Filtered out** or **Failed** incoming mail queues. If you need those emails, make sure to requeue them before the migration.
After this, wait for the **New** and **Being processed** queues to become empty. These steps assure that these emails will be migrated as well.
#### 5. Prepare incoming mail accounts
All emails that you do not want to be processed later in Cloud should be moved out or removed from the mail account folder that is used by Email This Issue for incoming emails. By default, this folder is called “INBOX”. To check if your Incoming Mail Connections are using custom folder settings you should look for the **Folder** option:
{% hint style="warning" %}
After the migration when incoming mail connections are enabled in the Cloud, all emails will be downloaded from the mail accounts regardless of being read or unread. If the mail account folders used by the connections are not cleared, it may lead to duplicate issues and comments.
{% endhint %}
#### 6. Set email audit log migration period
Optionally, you can set the time frame from when the audit log items should be migrated. The default time frame is to migrate from the last 1 month.
1. Navigate to the **Email Log** in the Email This Issue administration settings
2. Click on **Migration** then select the time frame that fits your needs from the **Migrate from the last** select list.\
3. Click on **Save settings**
## Cloud-side preparation
{% hint style="warning" %}
The migration tool will delete all existing data from Email This Issue Cloud by the end of the migration.
All these preparations are required to avoid data loss or duplication on the Cloud side of Email This Issue.
{% endhint %}
#### 1. Make sure Email This Issue is installed and has a valid license on your target Cloud instance.
#### 2. Disable every Incoming Email Connection
{% hint style="warning" %}
New emails will not be downloaded while this migration is in progress. Otherwise, these emails could be lost.
{% endhint %}
Disabling incoming mail connections in the Cloud version
#### 3. Clean up your Incoming Mail Queue
Check if there are any important emails in the **Skipped** or **Error** incoming mail queues. If you need those emails, make sure to requeue them before the migration.
After this, wait for the **Active** and **Processing** queues to become empty. These steps assure that these emails will be migrated as well.
Incoming mail queue before cleanup
#### 4. Prepare incoming mail accounts
All emails that you do not want to be processed in Cloud should be moved out or removed from the mail account folder that is used by Email This Issue for incoming emails. By default, this folder is called “INBOX”. To check if your Incoming Mail Connections are using custom folder settings you should look for the **Folder** option:
#### **5.** Enable data migration to your Cloud instance in Email This Issue
{% hint style="info" %}
This process can take a few minutes to complete, and there is no confirmation of its success.
{% endhint %}
To enable data migration, navigate to Email This Issue **Administration** - **Migration Options**:
Enabling data migration setting in Cloud
---
# 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/preparing-for-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.