> 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-templates.md).

# Migrating Templates

This section provides information on how to migrate email templates from Server to Cloud.

1. On the Server interface, display the email template you want to migrate as follows:
   1. Select **Email Templates** under the **OUTGOING EMAILS** section of the sidebar.
   2. Click the three dots next to the template you want to migrate and select **Edit**. Note that in case of migrating HTML templates, we suggest that you open the HTML source of the Server template by choosing **Edit in HTML**, then copying and pasting the HTML code to the **Raw HTML Editor** on Cloud.

2. In a separate browser tab, log in to the Cloud interface and migrate the basic template settings as follows:
   1. Select **Templates** under the **EMAIL CONTENT** menu item of the **Outgoing Mails** configuration tab.
   2. Click **Add** and select the **Empty** theme for your new template.
   3. Copy and paste the the content of the following fields from the **Edit Template** panel on Server to the **Add Template** panel on Cloud as shown in the image below:
      * **Name**
      * **Description**
      * **Category**
      * **Subject template**

3. Migrate the HTML body template as well as follows:
   1. Click **Next** on the **Add Template** panel.
   2. Click **Open raw HTML Editor** on the **Add Template** panel on Cloud.
   3. Copy and paste the content from the **HTML Body Template** field of the **Edit Template** panel on Server to the **Raw** **HTML Template** editor on Cloud as shown in the image below:

4. Click **Save** in the **Add Template** panel of the Cloud interface.

5. Repeat this procedure for all your email templates.

Your email templates are migrated from Server to Cloud.

Note: If you’re using advanced features on Server, such as the macros described in [Velocity Context in Email Rendering,](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/outgoing-emails/email-templates/velocity-context-in-email-templates.md) make sure to check the available macros on Cloud (see [Velocity Context for Templates](https://docs.meta-inf.hu/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-customizable-email-templates)).

For more information, see:

Server documentation: [Email Templates](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/outgoing-emails/email-templates.md)

Cloud documentation: [Customizable Email Templates](https://docs.meta-inf.hu/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-customizable-email-templates)


---

# 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-templates.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.