> 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-incoming-settings/migrating-incoming-mail-queue-settings.md).

# Migrating Incoming Mail Queue Settings

**Incoming Mail Queue** configuration cannot be migrated from Server to Cloud. On Server, there is a special feature called **purge strategy** (for details, see: [Incoming Mail Queue](/email-this-issue/email-this-issue-for-jira-server-data-center/documentation/administration/incoming-mail-queue.md)) but there is no corresponding feature on Cloud. Apart from this, the **Incoming Mail Queue** feature works the same way on Cloud as on Server.

The following figure shows the purge configuration options on Server:

![](/files/4IgyFYRQQhnmMHEmPrO2)

Note that as of now, migrating existing queue entries from Server to Cloud is not possible. An automated migration tool will be available later this year for this purpose.


---

# 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-incoming-settings/migrating-incoming-mail-queue-settings.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.