> 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-canned-responses.md).

# Migrating Canned Responses

This section provides information on how to migrate canned responses from Server to Cloud.

Note: Settings configured under **Canned Responses** on Server can be configured under **Responses** on Cloud.

1. On the Server interface, display the canned response that you want to migrate as follows:
   1. Select **Canned Responses** under the **OUTGOING EMAILS** section of the sidebar.
   2. Click the three dots next to the canned response you want to migrate and select **Edit**.

2. In a separate browser tab, log in to the Cloud interface and migrate the basic response settings as follows:
   1. Select **Responses** under the **ADVANCED CONFIGURATION** menu item of the **Outgoing Mails** configuration tab and click **Add**.

   2. Copy and paste the content from the **Edit Response** panel on Server to the **Add Canned Response** panel on Cloud. As shown in the image below, make sure to copy and paste the content of the following fields:
      * **Name**
      * **Description**
      * **Category**

3. Migrate the response text to the HTML template as follows:
   1. Click **Next** on the **Add Canned Response** panel.

   2. Copy and paste the response from the **Edit Response** panel on Server to the **HTML Template** section of the **Add Canned Response** panel on Cloud as shown in the image below. Note that while on Server only text format is available, on Cloud it is possible to add text in HTML format.

   3. Click **Next** on the **Add Canned Response** panel.

4. Add the response text to the text template as well by copying and pasting the response from the **Edit Response** panel on Server to the **Text Template** section of the **Add Canned Response** panel on Cloud as shown in the image below:

5. Click **Save** in the **Add Canned Response** panel of the Cloud interface.

6. Repeat this procedure for all your canned responses.

Your canned responses are migrated from Server to Cloud.

For more information, see:

Server documentation: [Canned Responses](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/outgoing-emails/email-templates/canned-responses.md)

Cloud documentation: [Default Messages (Canned Responses)](https://docs.meta-inf.hu/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-default-messages-canned-responses)


---

# 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-canned-responses.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.