> 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/upgrade-rmh/upgrading-cm.md). # Upgrade Classic Central to Flash Central Use this checklist as a guideline if you are upgrading Classic Central Manager to Flash Central Manager. Refer to the specific installation procedures for detailed installation steps.
Step 1Review the system requirements and perform any required upgrades. All computers must meet or exceed the minimum system requirements.
Step 2Perform Windows updates on all computers. Ensure all computers are updated with the latest service packs and hot fixes.
Step 3Download the latest RMH release package and extract all files. Review the release notes and readme for the release package. Determine if there are any known issues that could potentially impact the store's business operations.
Step 4Back up the Central and store databases.
Step 5Back up all custom files (labels, receipt templates, pictures, reports, active reports).
Step 6Exit all RMH apps on the computer.
Step 7Uninstall all RMH apps on the computer. This includes Central Manager, Central Server, Central Client, Store Manager, POS, and Loyalty.
Step 8Confirm that RMH services have been removed from the computer. These include the RMH Worksheet Processor, RMH Central Server, and RMH Central Client services.
Step 9Delete the C:\Program Files (x86)\Retail Hero folder from the computer.
Step 10Delete the C:\ProgramData\RetailHero folder from the computer. Note: The C:\ProgramData folder may be hidden. To show the folder, in File Explorer, click View \\
Step 11Install the .NET Framework or .NET SDK on any computer that will run an RMH app. .NET must be installed on any computer that will run an RMH app. The system requirements identify which version of .NET is required for the apps.
Step 12Restart the computer.
Step 13Install Flash Central Manager.
Step 14Connect to the Central database and force install tables.
Step 15Obtain a Flash Central license and activate it.
Step 16Install and configure Flash Central Server.
Step 17Install and configure the Flash Bridge on the Central Manager computer.
Step 18Install Store Manager. Follow the detailed installation instructions for the Store Manager app.
Step 19Install and configure Flash Central Client.
Step 20Install and configure the Flash Bridge on the Store Manager computer.
Step 21Configure Store Manager to operate with Central Manager.
Step 22Restore all custom files (labels, receipt templates, pictures, reports, active reports).
Step 23(Optional) Install and configure the Flash Backward Compatibility Extension. If you have any non-Flash stores, install the Flash Backward Compatibility Extension on the same computer where both the Flash and non-Flash RMH Central Server apps are installed.
Step 24Install POS.
Step 25Install and configure the Flash Bridge on the POS computer.
Step 26(Optional) Install Loyalty.
--- # 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.rmhpos.com/installation/upgrade-rmh/upgrading-cm.md?ask=&goal= ``` `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.