> For the complete documentation index, see [llms.txt](https://docs.bullmq.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bullmq.io/guide/migration-to-newer-versions/bull-to-bullmq.md).

# Bull to BullMQ

Bull and BullMQ have diverged too much now to actually give any guarantee of backwards compatibility.

So the safest would be to use new queues for BullMQ and deprecate the old ones.

New queues in this context mean using different queue names or passing a custom prefix option. You can have a period where bull and bullmq workers are running in parallel until all the jobs from the old queues are completed. Take into account that producers should add jobs in bullmq queues in this period. When all queues from bull are drained, you can deprecate them.

You can use a dashboard tool such as <https://taskforce.sh> for monitoring this process and make sure the old queues are completely empty before removing them.

## Read more:

* 💡 [Worker Prefix Option Reference](https://api.docs.bullmq.io/interfaces/v5.WorkerOptions.html#prefix)
* 💡 [Queue Prefix Option Reference](https://api.docs.bullmq.io/interfaces/v5.QueueOptions.html#prefix)


---

# 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.bullmq.io/guide/migration-to-newer-versions/bull-to-bullmq.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.