> For the complete documentation index, see [llms.txt](https://fulstech.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fulstech.gitbook.io/docs/custom-fields/jeditor-compatible-custom-field-for-jira-cloud/jira-cloud/migrate-to-jira-cloud.md).

# Migrate to Jira Cloud

{% hint style="info" %}
JEditor custom fields only Jira Data Center or Jira Server must be created by the [JEditor - Rich Text Editor For Jira](https://marketplace.atlassian.com/apps/1210768/jeditor-rich-text-editor-for-jira?tab=overview) plugin.
{% endhint %}

According to [this Atlassian's article](https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/#Adding-additional-entities-using-CSV-import), custom fields created by add-ons are not migrated by default.

However, the migration is still possible by the following steps:

## **Migrate the custom fields' data**

After migrate all data from Jira Data Center or Jira Server to Jira Cloud using Jira Cloud Migration Assistant, follow the instructions in [this Atlassian's article](https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/#Adding-additional-entities-using-CSV-import) to migrate JEditor fields to the Jira Cloud instance. Since Jira Cloud does not allow add-ons to add new custom field types, the Jira Cloud instance's custom fields to receive JEditor content must be of the type "Text Field (multi-line)".

## Install the Jira Cloud app

Please see the instructions [here](https://fulstech.gitbook.io/docs/custom-fields/jeditor-compatible-custom-field-for-jira-cloud/jira-cloud/overview).

## Configure the Jira Cloud app to render the new custom fields as JEditor

Please see the instructions [here](https://fulstech.gitbook.io/docs/custom-fields/jeditor-compatible-custom-field-for-jira-cloud/jira-cloud/create-a-markdown-enabled-custom-field).


---

# 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://fulstech.gitbook.io/docs/custom-fields/jeditor-compatible-custom-field-for-jira-cloud/jira-cloud/migrate-to-jira-cloud.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.