> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/rules/rule-flow/rule-flow-convertor.md).

# Rule Flow Convertor

The **Rule Flow Converter** allows you to **convert an existing Rule Flow into a Decision Flow**, making it easy to take advantage of all the advanced features of Decision Flow.

Decision Flow offers **greater flexibility, more node types, and powerful decision logic**, enabling scenarios that go beyond the capabilities of Rule Flow. By converting your Rule Flows, you can continue using your existing logic while unlocking these enhanced possibilities.

Learn more about [Decision Flow](/doc/rules/flow/decision-flow.md)

### How it Works

When you run the conversion:

* A new **Decision Flow** rule is created.
* The new rule inherits the same **input/output model, name, version, description, status, and audit log settings** as the original Rule Flow.
* If the Rule Flow contains any rules without defined aliases, the converter will automatically generate them.

### Where to Find It

The **Convert to Decision Flow** button is available directly in the **Rule Flow Designer**.

<div data-full-width="false"><figure><img src="/files/GamrMwu9e730USaHupDp" alt=""><figcaption></figcaption></figure></div>

### Availability

The **Convert to Decision Flow** option is visible only if the user has the necessary **permission to create rules**.

This option is **disabled** if:

* The user has reached their rule limits.
* Decision Flow is not enabled in the current plan.
* The Rule Flow contains warnings or errors.
* The Rule Flow has not been saved.
* The Rule Flow is locked.

### Conversion Mapping

During conversion, nodes are mapped as follows (Rule Flow -> Decision Flow):

* **Start** → **Start node**
* **Rule** → **Business Rule node**
* **End** → **Assign node**


---

# 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://docs.decisionrules.io/doc/rules/rule-flow/rule-flow-convertor.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.