> 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/email-this-issue-for-jira-server-data-center/server-to-cloud-migration/server-to-cloud-manual-migration-guide-for-email-this-issue/migrating-incoming-settings/migrating-incoming-mail-connections.md).

# Migrating Incoming Mail Connections

This section describes how to migrate incoming mail connections from Server to Cloud.

Note that if connections use OAuth2, client credentials need to be migrated first so that they are available when the connections are replicated on Cloud. For more information, see: [Migrating OAuth2 Credentials](/email-this-issue/email-this-issue-for-jira-server-data-center/server-to-cloud-migration/server-to-cloud-manual-migration-guide-for-email-this-issue/migrating-other-settings/migrating-oauth2-credentials.md).

1. On Server, do the following:
   1. Go to **Incoming Mail Connections** under **INCOMING EMAILS ADMINISTRATION** on the sidebar.
   2. Choose the account you want to migrate, click the three dots, and select **Edit**.

2. On Cloud, do the following:
   1. Go to the **Administration** configuration tab, then select **Incoming Mail Connections** under **INCOMING MAILS**.
   2. Click **Add**.

      ![](/files/AgOukYw62oV9fwT41pvr)

3. Copy and paste content from the **Edit Incoming Mail Connection** panel on Server to the **Add Incoming Mail Connection** panel on Cloud. Make sure to set the same values to the following fields on Cloud as on Server:
   * **Name → Name**
   * **Description → Description**
   * **Protocol → Service Provider**
   * **Encryption → Encryption**
   * **Host → Host**
   * **Username → Username**
   * **Password → Password**
   * **Port → Port**
   * **Timeout → Timeout**

4. Pay special attention to the **Protocol** field:
   * If it contains **IMAP** on Server, as in the example above, select **General IMAP4 service** in the **Service Provider** dropdown list on Cloud.
   * If it contains **POP3** on Server, select **General POP3 service** in the **Service Provider** dropdown list on Cloud.
   * If it contains **OAuth Credentials** on Server, as in the example below, select **GMail/GSuite with OAuth2** or **Microsoft365 with OAuth2** in the **Service Provider** dropdown list on Cloud, depending on the type of mail account that your are configuring.
     * If no OAuth2 Client settings are found, you must migrate your OAuth2 credentials from Server to Cloud, and restart the account setup procedure. For more information, see: [Migrating OAuth2 Credentials](/email-this-issue/email-this-issue-for-jira-server-data-center/server-to-cloud-migration/server-to-cloud-manual-migration-guide-for-email-this-issue/migrating-other-settings/migrating-oauth2-credentials.md).
     * If OAuth2 Client settings are already created on Cloud, configure the **OAuth2 Credentials** field on Cloud based on the value of the **OAuth Credentials** field on Server.

5. To validate all parameters, select **Test Connection**.

6. Save your settings.

Your mail accounts have been migrated. As a final validation step, send yourself a test email.

For more information, see:

[Migrating OAuth2 Credentials](/email-this-issue/email-this-issue-for-jira-server-data-center/server-to-cloud-migration/server-to-cloud-manual-migration-guide-for-email-this-issue/migrating-other-settings/migrating-oauth2-credentials.md)

Server documentation: [Incoming Mail Connections](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/administration/incoming-mail-connections.md)

Cloud documentation: [Incoming Mail Connections](https://docs.meta-inf.hu/email-this-issue/administration/email-this-issue-for-jira-cloud-incoming-mail-accounts)


---

# 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/email-this-issue-for-jira-server-data-center/server-to-cloud-migration/server-to-cloud-manual-migration-guide-for-email-this-issue/migrating-incoming-settings/migrating-incoming-mail-connections.md?ask=<question>&goal=<endgoal>
```

`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.