> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/plan-operating-system-upgrade-paths.md).

# Plan operating system upgrade paths

Plan Command Centre upgrades that require intermediate operating system versions.

Older Command Centre versions do not run on modern operating systems. A big version jump therefore has to step through intermediate operating systems.

### Worked example: 5.21 on Windows XP to 8.30 on Windows 10 Pro

1. 5.21 on Windows XP to **6.10**. Remove the Commanders first.
2. 6.10 to **7.20** on a newer operating system. Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8 Pro, Windows 8.1 Pro, Windows Server 2012, and Windows Server 2012 R2 are all options, so use what is available.
3. Import the databases and upgrade to **7.70**. **At 7.70 there is no support for Windows 2008 Server**, so it would not be a good choice in the previous step. SQL will likely need a Service Pack or a version upgrade at this step.
4. 7.70 to **8.10**. Deconfigure the Legacy controllers here.
5. 8.10 to the new Windows 10 server, which is already running **8.30**. Migrate the databases and attach or restore them.
6. Connect to the controllers and upgrade them once they are online.


---

# 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://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/plan-operating-system-upgrade-paths.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.