> 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-outgoing-settings/migrating-outgoing-mail-connections.md).

# Migrating Outgoing Mail Connections

This section provides information on how to migrate outgoing mail connections from Server to Cloud.

Note: Settings configured under **Outgoing Mail Connections** on Server can be configured under **Outgoing Mail Connections** on Cloud.

Note: 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 on migrating OAuth2 credentials, 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 the Server interface, display the SMTP connections that you want to migrate as follows:
   1. Select **Outgoing Mail Connections** under the **OUTGOING EMAILS ADMINISTRATION** section of the sidebar.
   2. Click the three dots next to the Outgoing connection you want to migrate, and select **Edit**

2. In a separate browser tab, log in to the Cloud interface and migrate SMTP connections as follows:

   1. Select **Outgoing Mail Connections** under the **OUTGOING MAILS** menu item of the **Administration** configuration tab, and click **Add**.

3. Copy and paste the content from the **Outgoing Mail Connection** panel on Server to the **Edit Outgoing Mail Connection** panel on Cloud as follows:
   1. As shown in the image below, make sure to copy and paste the content of the following fields:
      * **Name → Name**
      * **Description → Description**
      * **From Address → From Email Address**
      * **Prefix → Email Prefix**
      * **Connect Mode → Service provider**
      * **Encryption → Encryption**
      * **Username → Username**
      * **Password → Password**

   2. As shown in the image below, make sure to copy and paste the content of the following fields as well:
      * **Host → Host**
      * **Port → SMTP Port**
      * **Debug → Debug**

   3. In case of an OAuth2 setting, make sure to copy and paste the content of the following fields.
      * **Connect mode → Service Provider**
      * **OAuth2 Credentials → OAuth2 Credentials**

4. On the Cloud interface, click **Save**.

5. Repeat this procedure for all your connections.

Result: Your Outgoing Mail Connection settings are migrated from Server to Cloud.

For more information, see:

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

Cloud documentation: [SMTP Servers](https://docs.meta-inf.hu/email-this-issue/administration/email-this-issue-for-jira-cloud-smtp-servers)


---

# 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-outgoing-settings/migrating-outgoing-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.