> For the complete documentation index, see [llms.txt](https://boost.filecoin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boost.filecoin.io/v1/upgrade-from-lotus-to-boost.md).

# Migrate from Lotus to Boost

This section describes how to upgrade your lotus-miner markets service to boostd, as well as how to roll-back if you are not happy with boostd

A storage provider can run the lotus as a monolith process where everything is handled by a single `lotus-miner` process or separate the mining and market subsystems on different machines.

Boost supports migration from both monolith and a split-market miner. You can follow the below guides to migrate to boost.

{% content-ref url="/pages/VSf4rLOJPjZZ5PFP2s02" %}
[Migrate a monolith lotus-miner to Boost](/v1/upgrade-from-lotus-to-boost/migrate-a-monolith-lotus-miner-to-boost.md)
{% endcontent-ref %}

{% content-ref url="/pages/i58PiI49lAXD7PaoBmve" %}
[Migrate a Lotus markets service process to Boost](/v1/upgrade-from-lotus-to-boost/migrate-a-lotus-markets-service-process-to-boost.md)
{% endcontent-ref %}

### **Rollback**

{% hint style="danger" %}
Please note that Boost uses a SQLite database for the deal metadata and logs. Once Boost has been enabled, the new deals cannot be rolled back to the Lotus markets. If you decide to roll back after making Boost deals, you will lose all the metadata for the deal made with Boost. However, this will have no impact on the sealed data itself.
{% endhint %}

{% content-ref url="/pages/YKPnNk4KY9xkFdrmLCGf" %}
[Roll back to Lotus markets service process](/v1/upgrade-from-lotus-to-boost/roll-back-to-legacy-markets.md)
{% endcontent-ref %}

<br>


---

# 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://boost.filecoin.io/v1/upgrade-from-lotus-to-boost.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.