> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/migrating-from-the-alpha-version.md).

# Migrating from the alpha version

Steps to migrate a GHE.com Cloud organization imported during the alpha version of the import feature.

If you have imported your GHE.com organization during the alpha version of this import feature, you have to perform the following steps:

1. Go to GHE.com and edit your GHE application as follows to enable webhooks:
   1. In the **Webhook** section, select **Active** and fill in the webhook fields mentioned in [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md#step-1).
   2. In **Subscribe to events** select the following event types: **Pull request**, **Push**, **Repository**. The owners of organizations on which the app is installed will be notified that the app is requesting updated permissions. Organization owners must manually approve the updated permissions otherwise the app will still retain its current permissions.
2. In SonarQube Cloud, add the following to your SonarQube Cloud organization binding (see [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md#updating-the-ghe-app-details)):
   1. The webhook secret.
   2. Your enterprise name. (It's the name you see in your Web URL: <https://enterprise-name.ghe.com>)

## Related pages

* [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/migrating-from-the-alpha-version.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.