> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/licensing/licensing-mlm-to-ls.md).

# Convert from MLM licensing to RMH Hub licensing

This topic describes how to configure the licensed RMH apps to use license keys obtained through the RMH Hub.

{% hint style="info" %}
The customer must be using a version of RMH that supports RMH Hub app licensing (e.g., 3.51+). The customer's store database(s) must currently be licensed in MLM, and the customer must have not for resale (NFR) or production app license keys generated by the RMH Hub.
{% endhint %}

1. Start **Store Manager** on all computers and log in.
2. Start **POS** on all computers and log in.
3. On all computers running Store Manager, convert the app licensing for Store Manager to the RMH Hub:
   1. Click **File** | **Switch to LS Licensing**. Click **Yes** to confirm.
   2. In the **License Key** field, paste the app license key from the RMH Hub.
   3. Click **Activate**.
   4. Click **OK** to confirm. Store Manager automatically closes.
4. On all computers running Store Manager, confirm that Store Manager is successfully licensed through the RMH Hub:
   1. Start **Store Manager** and log in.
   2. Click **File**. It should say **Licensed in LS Mode**.
5. On all computers running POS, convert the app licensing for POS to the RMH Hub:
   1. Tap **Operations** | **About** | **Switch to LS Licensing**. Tap **Yes** to confirm.
   2. In the **License Key** field, paste the app license key from the RMH Hub.
   3. Tap **Activate**.
   4. Tap **OK** to confirm. POS automatically closes.
6. On all computers running POS, confirm that POS is successfully licensed through the RMH Hub:
   1. Start **POS** and log in.
   2. Tap **Operations** | **About**. It should say **Licensed in LS Mode**.


---

# 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.rmhpos.com/installation/licensing/licensing-mlm-to-ls.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.