> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/power-tools/manual-extractions.md).

# Manually run Extractions on your Cloud Environments

{% hint style="info" %}
If you are running Deploy 4+, we recommend you run extractions from the Deploy Dashboard instead of KUDU. For more information, see the [Deploy Dashboard](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/deployment/deploy-dashboard.md) article.
{% endhint %}

When deploying from one environment to another, the files from the Git repository are merged into the files used on the site. The Deploy engine then runs an extraction. This means that the files on the disk will be deserialized into the database in the Cloud environment.

Run an extraction following these steps:

1. Access Kudu.
2. Navigate to **CMD** under the **Debug console** menu.
3. In the file structure, navigate to `site/wwwroot/umbraco/Deploy`.

{% hint style="info" %}
When using Umbraco 7 or 8, you need to navigate to `site/wwwroot/data` folder.
{% endhint %}

4. The `/Deploy` folder contains:
   * `Revision` folder containing all your project's UDA files.
   * `deploy-marker` indicating the state of the latest extraction (`deploy-complete` or `deploy-failed`).
   * `deploy.log` containing logs from the latest extraction.
5. While in this folder, type the following command in the CMD console: `echo > deploy`. This will initiate extraction of the environment.
6. While the extraction is running, the *deploy-marker* will change its name to `deploy-progress`.
7. The extraction will end in one of two possible outcomes:
   1. `deploy-complete`: The extraction succeeded and your environment is in good shape.
   2. `deploy-failed`: The extraction failed - open the file, to see the error message. The same error message will be shown on your environment in the Umbraco Cloud Portal.

![Run manual extraction](https://3739769070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPzKn70Piyd2fd5UkYZGf%2Fuploads%2Fgit-blob-439755568e57397d58666ef5cfb2d0b350737ffa%2Fmanual-extraction-v9.gif?alt=media)

{% hint style="info" %}
Sometimes, you might encounter a deploy-marker called `deploy`. This usually means that extraction cannot run and you need to restart your environment for the extraction to run.
{% endhint %}

Sometimes, you might also need to run this extraction locally. This can be done using Command Prompt (CMD) to navigate to the `/umbraco/data` folder in your local project.

Find general information about Kudu and how to access the tool in the [Power tools](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/power-tools.md) article.


---

# 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.umbraco.com/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/power-tools/manual-extractions.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.