# Migrating Post Functions

This section provides information on how to migrate post functions from Server to Cloud.

1. On the Server interface do as follows:
   1. Select **Issues** in the **Administration** menu, then go to **Workflows** under the **WORKFLOWS** section of the sidebar.
   2. Choose the Workflow that has Email This Issue Post Functions to migrate, and click **View** under the **Actions** column.
   3. Switch to **Text** view to display the **Transitions (id)** column.

2. In a separate browser tab, log in to the Cloud interface and do as follows:
   1. Select **Issues** in the **Settings** menu, then go to **Workflows** under the **WORKFLOWS** section of the sidebar.
   2. Choose the Workflow that you will migrate the Post Functions to, and click **View** under the **Actions** column.
   3. Switch to **Text** view to display the **Transitions (id)** column.

3. Find the transition of the Post Functions you want to migrate based on the **Transitions(id)** column both on Server and Cloud.

4. Click the transition ID under the **Transitions(id)** column both on Server and Cloud.

5. Do as shown in the image below:
   1. Switch to the **Post Functions** tab of the selected transition both on Server and Cloud.
   2. On the Server interface, hover your mouse over the post function that you want to migrate and select the edit icon to see the details of the post functions. Note that all Post Functions created with the Email This Issue Post Function Plugin are marked with the **Sends issue in email with the following parameters** label as shown in the example below.
   3. On the Cloud interface, click **Add post function**.

6. On the Cloud interface, select **Send Customizable Emails** in the **Add Post Function To Transition** panel.

7. Copy and paste the content from the **Email Recipients and Content** panel on Server to the **Add Parameters To Function** panel on Cloud.
   1. As shown in the image below, make sure to copy and paste the contents of the following fields:
      * **JQL Filter → JQL Filter**
      * **Recipients (To)** → **Recipient(s) To**
      * **Copy recipients (Cc)** → **Recipient(s) Cc**

   2. As shown in the image below, scroll down and make sure to copy and paste the contents of the following fields as well:
      * **Subject** → **Subject**
      * **Body** → **Message**
      * **Add attachments to email** → **Attachments**
      * **Templates** → **Template**

   3. As shown in the image below, make sure to copy and paste the content of the following field as well:
      1. **HTML Email** under **Email Settings** → **Email Format**

8. On the Cloud interface click **Add**.

9. Move the new Post Function down to the last position in the list of Post Functions.

10. Repeat this procedure for all your Email This Issue Post Functions within all the affected workflows and transitions.

Your post function settings have been migrated. Don’t forget to publish your updated workflows when you are finished with all your transition updates.

For more information, see:

Server documentation: [Workflow post-function](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/outgoing-emails/workflow-post-functions.md)

Cloud documentation: [Workflow Post Function](https://docs.meta-inf.hu/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-workflow-post-function)


---

# Agent Instructions: 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:

```
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-post-functions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.