> 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-workflow/17.latest/upgrading/migrating-workflow.md).

# Migrate from Plumber to Workflow

Umbraco Workflow is backwards compatible with Plumber data. However, with a new default namespace constituting a major breaking change any existing customization or extension needs to be updated.

To migrate from an Umbraco installation with an existing Plumber installation to Umbraco Workflow, follow these steps:

{% tabs %}
{% tab title="Site running on SQL Server database" %}

1. Uninstall Plumber and remove the `/App_Plugins/Plumber` folder.
2. Upgrade your project to Umbraco 11.
3. Install Umbraco Workflow 11. See the [Installing Umbraco Workflow](/umbraco-workflow/17.latest/installation/installing-workflow.md) article.
4. Build the application.

{% hint style="info" %}
SQL is the preferred database provider for production websites.
{% endhint %}
{% endtab %}

{% tab title="Site running on SQLite database" %}

1. Uninstall Plumber and remove the `/App_Plugins/Plumber` folder.
2. Upgrade your project to Umbraco 11.
3. Make a copy of the `Value` column from the `WorkflowSettings` table.
4. Delete the `WorkflowSettings` table.
5. Update `WorkflowTaskInstance` table to allow null values in the GroupId column.
6. Install Umbraco Workflow 11. See the [Installing Umbraco Workflow](/umbraco-workflow/17.latest/installation/installing-workflow.md) article.
7. Build the application.
8. Update the `WorkflowSettings` table to restore the previous data to the `Value` column.
   {% endtab %}
   {% endtabs %}

{% hint style="info" %}
All your existing workflow data and settings are not affected and will be available on your upgraded site.
{% endhint %}


---

# 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-workflow/17.latest/upgrading/migrating-workflow.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.