> 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/upgrade-command-centre-server.md).

# Upgrade Command Centre Server

Upgrade Command Centre safely through version steps, with backups, customizations, and remote SQL.

{% hint style="info" %}
**Prerequisites:** Read [Installation - Hardware Restrictions](broken://pages/URbBlUhr3FTmx0CXVuK3) first if the site is coming from a much older version.
{% endhint %}

An upgrade is a loop of small version steps. Each step follows the same sequence.

### The upgrade loop

1. Process as many alarms as possible.
2. Apply all Windows updates and restart to apply them.
3. Verify the recovery code is valid. See [Databases - Detaching and Reattaching](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/cc-software/configure/databases-an-overview-of-command-centr/databases-detaching-and-reattaching.md).
4. **Backup.**
5. Upgrade SQL if necessary.
6. Run Command Centre and confirm all is OK.
7. **Backup.**
8. Upgrade Command Centre.
9. Run Command Centre and confirm all is OK.
10. If more steps remain, go to 4.
11. **Backup.**

If event history matters, detach both databases (**CCFTCentral** and **CCFTEvent**) and copy them to a safe location after each successful step. Use a portable drive or a network drive if the server is old. If history does not matter, a backup is enough to migrate between servers.

{% hint style="warning" %}
**Warnings**

* Never move a database to a server running a **higher** version than the database's origin.
* When moving databases or backups to a new server, the new server must be at the **same version** as the original.
  {% endhint %}

### Customizations

Customisations must be installed before services will start on a server whose database has them configured.

To migrate a system that uses them:

1. Remove the customisations from the old server.
2. Copy the databases to the new server.
3. Install the same Command Centre version on the new server.
4. Detach the new install's blank databases.
5. Copy the old databases into the data directory and attach them.
6. Install the customisations and start the services.

Before upgrading further, remove the customisations again. Always confirm the target version has the customisation available for it.

### Remote SQL

When the database is on a separate server, the Windows account performing the upgrade must have **DB Admin** rights on the SQL databases and **local administrator** rights on the Command Centre server. The same rights are required when adding or removing customisations.


---

# 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/upgrade-command-centre-server.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.