> 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-other-settings.md).

# Migrating Other Settings

This chapter provides information on how to migrate other settings that are not specific to outgoing or incoming emails from Server to Cloud. See the following sections for migrating certain features.

The following table also shows the level of difficulty of each feature’s migration from Server to Cloud and how much time it takes to move configurations from Server to Cloud.

Note: These estimates may vary and depend on the number of settings you need to migrate.

|                                                                                            |                                  |                    |
| ------------------------------------------------------------------------------------------ | -------------------------------- | ------------------ |
| **Procedure**                                                                              | **Migration process difficulty** | **Time demand**    |
| ​​[Migrating OAuth2 Credentials](broken://pages/bpAos7cjAvNSfnaPpe83)                      | EASY​                            | FAST​              |
| [Migrating global default email settings](broken://pages/nrCZWokjAcUuG8gFOQR5)             | MEDIUM​                          | <p>MEDIUM​<br></p> |
| ​​[Migrating permissions for sending emails manually](broken://pages/6p9HbbaWhD6qGzcuWt4k) | MEDIUM​                          | MEDIUM​            |
| [Migrating recipient restrictions](broken://pages/RNmklQIcFKsxghV3Gaop)                    | MEDIUM​                          | MEDIUM​            |

<br>


---

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