> 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/roll-back-to-legacy-markets.md).

# Roll back to Lotus markets service process

This section describes how to roll back to Lotus markets service process if you are not happy with boostd

{% hint style="warning" %}
Before you begin migration from Lotus markets service process to Boost, make sure you have a backup of your Lotus repository, by following the [Lotus documentation](https://lotus.filecoin.io/storage-providers/operate/backup-and-restore/).\
\
You can also do a full backup of the Lotus markets repository directory.
{% endhint %}

1. If you haven't made any legacy deals with Boost:
   1. Stop `boostd` 
   2. Run your `lotus-miner` `markets` service process as you previously did<br>
2. If you have made new legacy deals with Boost, and want to migrate them back:
   1. Stop `boostd`
   2. Copy the `dagstore` directory from `boost` repository to `markets` repository.
   3. Export Boost deals datastore keys/values:\
      `lotus-shed market export-datastore --repo <repo> --backup-dir <backup-dir>`\
      \
      `Wrote backup file to <backup-dir>/markets.datastore.backup`
   4. Import the exported deals datastore keys/values from `boost` to `lotus markets`:\
      `lotus-shed market import-datastore --repo <repo> --backup-path <backup-path>`\
      \
      `Completed importing from backup file <backup-path>`


---

# 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/roll-back-to-legacy-markets.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.