> 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/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud/server-migration.md).

# Server Migration

The TLS Client Certificate used to authenticate a Command Centre server against the Cloud is unique per server. It is stored in Command Centre's database.

If you move your Command Centre installation to a new server – typically by restoring a Command Centre backup onto a new machine – both the old and new servers will have a copy of the certificate and the cloud will treat them as a single instance. If the old server remains online this may lead to failure to issue Mobile Credentials or other connectivity problems.

If you wish to move your Command Centre installation from one server to another, and the old server is still online and connected to the internet, you must perform the **Disable Communication** override on the Cloud Item on the old server to prevent it from interfering with the new server.

You should not delete the Cloud Item from the old server. Simply disable communications and ideally power off the old server after migration.


---

# 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/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud/server-migration.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.
