> 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-deploy/17.latest/deployment-workflow/deployment-workflow.md). # Deployment A description of the proper workflow when working with Umbraco Deploy Umbraco Deploy uses a deployment model that relies on Git and Umbraco Deploy core technology to move your changes from one environment to another. Umbraco Deploy uses a classic "left to right" deployment model, meaning that changes are first made in the Development or local environment and then deployed to the production environment. {% hint style="info" %} If your project contains a Staging environment, deployments will be made from Development to Staging and then from Staging to Live. {% endhint %} ![Left to right model](https://3380034848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Febsxdo6rn5b86Y4JvrrZ%2Fuploads%2Fgit-blob-ffe8d03dd6cb6ff9fff12f6188df6031141673b4%2Fleft-to-right.png?alt=media) ## Deployment Approach Umbraco Deploy uses a two-part deployment approach. This approach keeps meta data (Document types, templates, and so on) separate from content (Content nodes and Media). The term *transfer* refers to content and media deployments. The term *deploy* refers to meta data deployments. In summary: 1. Meta data such as Document Types, Templates, Forms, Views and config files are stored in a repository and are **deployed** between environments. This can be achieved using a CI/CD deployment pipeline with something like GitHub Actions or Azure DevOps. 2. Content and Media items are **not** stored in the repository. These need to be **transferred** directly from the Umbraco backoffice using the *"Queue for Transfer"* option. Once a content editor has all the items needed for a transfer they will use the Deployment Dashboard in the Content section to transfer the items in the queue. ### Deploying meta data To transfer content and media, the source and target environments needs to have the same setup. They need to be in sync and have the same file structure. To achieve this you need to deploy your meta data changes to the target environment. * [Deploying from your local machine to your environments](/umbraco-deploy/17.latest/deployment-workflow/deploying-changes.md) ### Transfer Content and Media Moving your content and media between your environments is done through the Umbraco backoffice. You can transfer content from one environment to another, for example, from local to your development environment. You also have the option to restore content and media to your local or development environment from your production or staging environment. * [Transfer Content and Media](/umbraco-deploy/17.latest/deployment-workflow/content-transfer.md) * [Restore Content and/or Media](/umbraco-deploy/17.latest/deployment-workflow/restoring-content.md) {% hint style="info" %} Transferring and restoring content and media is the same whether you are working locally and transferring between two environments. {% endhint %} {% embed url="" %} Umbraco Deploy - Content transfer and deploy {% endembed %} ### Import and Export Another approach for transferring content and schema between environments is to use import and export. In one environment, you can export selected content, a tree, or the whole workspace to a .zip file. There are options to include related media files, schema and code files such as templates and stylesheets. That .zip file can then be uploaded into a new environment, where it will be validated and then processed to update Umbraco. As part of the import process, hooks are provided to allow for migrations of the imported artifacts (like data types) and property data. This should allow you to migrate your Umbraco data from one Umbraco major version to a newer one. It is recommended to use the content and media backoffice transfer options for day-to-day editorial activities. Import and export is intended more for larger transfer options, project upgrades, or one-off tasks when setting up new environments. Read more about the [import and export](/umbraco-deploy/17.latest/deployment-workflow/import-export.md) feature. ## Deploy Dashboard Umbraco Deploy includes a Deploy Dashboard in the Settings section of the Umbraco backoffice to make it easier to run operations like schema deployment from data files and extract schema to data files. When running the `extract schema to data files` operation, Umbraco Deploy will run an `echo > deploy-export` in the data folder of your project which is used to generate UDA files based on the schema in your database. Running the `schema deployment from data files` operation will initiate an extraction on the environment 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 deploy-failed file, to see the error message. {% hint style="info" %} When [`DiskMode`](/umbraco-deploy/17.latest/getting-started/deploy-settings.md#disk-mode) is set to `ReadOnly`, Deploy doesn't process marker files or write status files. The dashboard shows the outcome of the last operation instead, and extracting schema to data files returns an error. {% endhint %} It is also possible to see which version of Umbraco Deploy you are running, when the last operation was started and the status of the deployment operation.
Deploy Dashboard

Deploy Dashboard

{% embed url="" %} Umbraco Deploy - Content transfer and deploy {% endembed %} --- # 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-deploy/17.latest/deployment-workflow/deployment-workflow.md?ask=&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.