> 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/migrate-from-rms-to-rmh/migration-hq-to-cm.md).

# Migrate from Headquarters to Central Manager

This topic identifies one method for migrating stores from RMS Headquarters to RMH Central Manager. Contact your partner for more information.

{% hint style="info" %}
Migration from Microsoft Dynamics' Retail Management System Headquarters (RMS HQ) to Retail Management Hero Store Manager and POS is only possible if the store's version of RMS HQ is 2.0.2000 (Cumulative Update 5) or newer.
{% endhint %}

## **Prepare for migration to Central Manager**

* Settle all credit or debit card (ECD) transactions.
* Run Z reports for every register to close out the registers.
* Complete all received purchase orders.
* Synchronize RMS HQ and all store databases using Worksheet 401.
* Stop all RMS HQ services (the server and all clients). The services are called HQ Server and HQ Client.
* Back up the RMS HQ database.
* Install Store Manager and POS.
* Install Central Manager, Central Server, and Central Clients.
* Activate the Store Manager and Central Manager licenses.

## **Connect to the RMS HQ database**

1. Start **Central Administrator**. The shortcut should be available on your desktop.
2. Click **Configuration**.
3. In the **Database** field, type the name of the **RMS HQ** database.
4. Click **Test Database Connection**.
5. Click **OK**.
6. Click **Save And Close**.
7. Click **Connect**.
8. Enter the **User Name** and **Password** for the **RMS HQ** database and click **Connect**.
9. Click **Force Install Tables** to update the database schema to work with RMH.
10. Click **Yes**.

## **Configure Central Server**

Refer to [**Install and configure Flash Central Server**](/installation/install-central-manager-multi-store/installation-central-server.md) for more information.

## **Prepare the RMS HQ database and confirm that passwords were deleted**

1. In **Central Server Assistant**, click **RMHC Database**.
2. Click **Prepare Database**.

{% hint style="warning" %}
This modifies the database schema so it is compatible with Central Manager. After you click Prepare Database, the database will no longer be backwards compatible to RMS HQ. This function will preserve usernames in the RMS HQ database but will delete passwords.
{% endhint %}

3. In **Central Administrator**, click **Query**.
4. Click **New Query**.
5. On the **SQL** tab enter: `SELECT \* FROM HQUsers`
6. Click **Run**.

If passwords are still showing in the password column, or the passwords appear encrypted:

1. Click **New Query**.
2. On the **SQL** tab enter: `UPDATE HQUser SET Password=’’` where the `’’` is two single apostrophes.
3. Click **Run**.

## **Configure store groups in Central Manager**

1. In **Central Manager**, click **Setup**.
2. Expand **Store**.
3. Click **Store Groups**.
4. Click **New**.
5. In the **Code** field, type a unique code for the store group, e.g., SG1.
6. In the **Description** field, type a description of the store group.
7. Select one of the following:

* All Stores
* Available Stores

8. Click **Save And Close**.

## **Assign records to store groups in Central Manager**

1. In **Central Manager**, click **Wizards**.
2. Click **Store Group Wizard**.
3. Select the store group(s).
4. Click **Next**.
5. Select the entity (**Item**, **Item Tax**, **Tax**, **Supplier**) containing the records that you want to assign to the store group.

{% hint style="info" %}
Select **Include dependencies** if you want to assign the records for all entities at once, instead of running the wizard four times to assign the records one entity at a time.
{% endhint %}

6. Click **Next**.
7. The option you selected determines the next steps:

* **Item:** Select the departments, categories, or suppliers, or use the Item Filter to select specific records to assign to the store groups.
* **Item Tax, Tax, or Supplier:** Use the Item Filter to select specific records to assign to the store groups.

8. Click **Next**.
9. Click **Finish**.

{% hint style="info" %}
Starting with release 3.11.14, the **Store Group Wizard** will continue to create records for items in the GlobalCatalog table of the Central Manager database, but it will no longer create any jobs to synchronize items to stores. You should use **Worksheet 261: Download Items** to synchronize items (and their properties) to stores instead of the Store Group Wizard.
{% endhint %}

## **Migrate stores to Store Manager and POS**

Migrate each store from Retail Management System Store Operations (RMS SO) to Retail Management Hero Store Manager and POS. Refer to [**Migrate from Store Operations to Store Manager**](/installation/migrate-from-rms-to-rmh/migration-so-to-sm.md) for more information.

## **Configure Store Manager to operate with Central Manager**

For each store:

1. In **Store Manager**, click **File** | **Configuration**.
2. Go to the **Multi-Store** tab.
3. Verify the **Store ID**.
4. Click **Test** to verify and test the **Central Server Assistant URL** and port.
5. Click **Save And Close**.

## **Configure the Central Clients**

Refer to [**Install and configure Flash Central Client**](/installation/install-central-manager-multi-store/installation-central-client.md) for more information.


---

# 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/migrate-from-rms-to-rmh/migration-hq-to-cm.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.