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

# Migrating Contexts

This section provides information on how to migrate some of your context settings from Server to Cloud.

Note: **Contexts** do not exist on Cloud, but some of their features from Server can still be set up in **Advanced Email Configuration** on Cloud.

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

2. In a separate browser tab, log in to the Cloud interface and migrate the scope-related settings as follows:
   1. Select **Advanced Email Configuration** under the **ADVANCED CONFIGURATION** menu item of the **Outgoing Mails** configuration tab, and click **Add**.
   2. Copy and paste the content from the **Edit Context** panel on Server to the **Add New Advanced Email Configuration** panel on Cloud. As shown in the image below, make sure to enable the **Email Triggers** you want to apply, and to copy and paste the content of the following fields:
      * **Project**
      * **Issue Type**
      * **JQL Filter**
      * **Order**

3. Migrate email settings as follows:
   1. Click **Next** on the **Add New Advanced Email Configuration** panel of the Cloud interface.

   2. As shown in the image below, make sure to copy and paste the content of the following fields from Server to Cloud:

      * **Field for External Watchers → Store Non-Jira recipients**
      * **Sender Name Pattern → From Name Pattern**
      * **From Address Pattern → From Email Address Pattern**

   3. Scroll down in the **Add New Advanced Email Configuration** panel and migrate the content of the following fields as well:
      * **Reply-to Address Pattern → Reply-To Email Address Pattern**

      * **Bcc Address → BCC address**

      * **Reply Template → Reply/Forward template**

4. Click **Save** in the **Add New Advanced Email Configuration** panel of the Cloud interface.

5. Repeat this procedure for all your contexts.

Result: Some of your context settings are migrated from Server to Cloud.

The following sections of this Manual Migration Guide also explain the migration of some context-related settings:

[Migrating Manual Email Defaults](/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-manual-email-defaults.md)

[Migrating Notifications](/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-notifications.md)

For more information, see:

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

Cloud documentation: [Advanced Email Configuration](https://docs.meta-inf.hu/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-advanced-email-configuration)


---

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